# What Framework starter build status Plans and build updates are not live releases. Only recorded published source and verified deployments receive source/demo links. Reported checks are not independent verification. Updated: 2026-10-08T17:02:10.656Z ## Tempo — Live on Vura The tracker shows its running block and elapsed time, guards pending creation and invalidates late responses on reset. Keyboard editing remains stable; denied storage is explicitly session-only. - Reference: https://whatfw.com/templates/status/what-starter-tempo - Public source: https://github.com/CelsianJs/what-starter-tempo - Live demo: https://what-starter-tempo-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Continuous keyboard editing: Failed — The numeric/text update replaced the input DOM node and moved focus to the body. Keyed accessor rows are being verified to preserve continuous typing and persistence.; Final reviewed source and live refinement: Passed — Source bb8edc729bc875cbd3a114840d5b27871e4f529c is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; Continuous keyboard editing: Passed — Live continuous replacement typing retains the same connected, focused input DOM nodes; complete values and updated totals persist. The earlier remount/focus-loss failure is closed by keyed accessor rows.; October workflow and brand audit: Reported, not independently verified — Repairing duplicate pending timer starts, honest storage-failure feedback and running-block context. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; Early Function response diagnostic: Reported, not independently verified — One early validation request returned503. Fresh UI retries, the real reset-during-pending flow and three consecutive direct probes returned200. The isolated transient cause is not confirmed; this is not a perfect cold-start reliability claim.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Serverless demos should show request boundaries even when the data is synthetic.; Use keyed accessors for editable repeated state when objects are replaced immutably.; Reset is an asynchronous ownership boundary, not just a group of signal writes.; Keep style regressions in the delivery path alongside behavior checks. - Learning journal: Tempo is a hybrid time-tracking SaaS reference: the browser owns workspace state and two serverless endpoints validate entries and summarize reports. - Source paths: src/state.js, src/domain.js, src/app.jsx, src/api/bounded-json.js, src/styles.css - Example topics: Seed demo rows relative to now; Keep focused rows stable during immutable edits; Bound function input by bytes, not text length; Let only the current workspace accept an async report - Limitations: Workspace data is browser-local seed data, not a multi-user database.; Serverless functions validate and summarize posted data; they do not persist account records. ## Launchpad — Live on Vura Product-facing releases, transparent rate assumptions and distinct tour evidence make the startup reference substantive. Its static pages, islands and no-JS content passed new release checks. - Reference: https://whatfw.com/templates/status/what-starter-launchpad - Public source: https://github.com/CelsianJs/what-starter-launchpad - Live demo: https://what-starter-launchpad-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 98fa34bf19a56b022403f8e75102e0d7a9c7ef0b is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Deepening product-facing pricing, changelog and documentation with distinct worked tour scenarios. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Static route classes are part of the component contract when a client island mounts inside them.; Static-first does not mean state-free; persisted island state still needs input hygiene.; Product claims should come from visible authored evidence, not decorative metrics.; Distinguish decoration from a data encoding before removing a visual treatment. - Learning journal: Launchpad is a static startup marketing site with small What islands for pricing and product-tour interaction. - Source paths: src/server/render.mjs, src/client/main.jsx, scripts/check.mjs, src/shared/site.css - Example topics: Clamp persisted pricing inputs before making signals; Treat static route generation as a contract; Read tour evidence at the selected stage; Keep timeline fill driven by authored data - Limitations: The pricing calculator is an anonymous local estimate, not billing or entitlement logic.; All application pages are static HTML with client islands; there is no request-time backend in this starter. ## Fieldwork — Live on Vura Four distinct authored research dossiers present questions, methods, specimens and limits. The shared seeded instrument is described honestly, with a clearer mobile accession heading and adjacent navigation. - Reference: https://whatfw.com/templates/status/what-starter-fieldwork - Public source: https://github.com/CelsianJs/what-starter-fieldwork - Live demo: https://what-starter-fieldwork-fae244da.vura.app/ - Checks: Clean install and local workflows: Passed — Node22 clean npm ci, 3 unit tests, production build and browser smoke passed. The canvas test checks changed pixels, and every research record is opened directly. Full dependency audit reports zero vulnerabilities.; Vura release and public source: Passed — Public repository commit verified. HTTPS home, build guide and direct research route return200; unknown path returns404. Native browser renders the guide and source-linked lessons.; Visual quality review: Failed — The initial layout did not meet the presentation bar: oversized type and a cramped canvas need a dedicated design revision. Functional checks do not establish visual quality.; Revised design and harness verification: Passed — Independent visual review cleared real desktop and390px mobile captures. Fresh install,3 unit tests, build-first browser smoke, isolated repository-local harness and owned-process exit passed. The revised HTTPS home, guide, direct record and404 were checked on the new deployment.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source a4bd66527a71a0c495adbcb335ae5bc494041eff is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Deepening per-record research dossiers and clarifying the shared seeded instrument and mobile accession heading. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: When an effect must follow a signal over time, pass the accessor, not a sampled value.; Deployment success and design quality are different claims. The public journal should name both.; For public starter evidence, process exit is part of the proof, not bookkeeping after the proof.; Research-style presentation must distinguish authored specimens from empirical evidence. - Learning journal: Fieldwork is a client-rendered creative research archive with deterministic canvas art, filters and static aliases for every bundled research record. - Source paths: src/state/gallery.js, src/components/GenerativeCanvas.jsx, scripts/generate-static-aliases.mjs, tests/smoke.mjs, src/data/dossiers.js, src/components/ProjectCard.jsx, src/pages/ProjectDetailPage.jsx, src/styles.css - Example topics: Use signal accessors as effect dependencies; Generate route aliases from the content source; Let only the card footer stretch; Keep immutable route content out of mutable state - Limitations: Canvas art is deterministic browser drawing, not live AI inference.; The archive is client rendered; research detail content is not request-time SSR article HTML. ## Oscillator — Live on Vura Saved/custom pattern identity, guarded storage failure and numerical controls match the instrument state. The playable sequencer appears much earlier on mobile; audio ownership and guide containment pass. - Reference: https://whatfw.com/templates/status/what-starter-oscillator - Public source: https://github.com/CelsianJs/what-starter-oscillator - Live demo: https://what-starter-oscillator-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source a441f9fe97604ed90b2b04bf495bf19bc9cd2516 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Repairing denied-storage feedback and saved-pattern identity, with the sequencer earlier on mobile. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Reported, not independently verified — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. The desktop home hero measures 56px, exceeding the 48px heading target; this styling exception remains open.; Oscillator heading bound repaired and rechecked on production: Passed — The previously reported 56px desktop hero is closed by the released stylesheet repair. Fresh home, studio and build routes returned 200 at 1440 by 900 and 390 by 844 with the exact new deployment identifier. Home heading measures 48px on desktop and 32px on mobile; body text remains 16px and brand targets meet 44px. No horizontal page overflow, framework overlay, pageerror or console error occurred. Home-to-studio navigation responds with a visible 2px keyboard focus outline. The actual released desktop PNG is the replacement gallery preview. - Lessons: A visual alignment bug can be a data-structure bug in the markup, not only a CSS spacing bug.; Long-running browser resources need idempotent start and explicit cancellation, even in a demo.; Preset identity, current edits and persistence success are separate facts.; Reflow related controls and labels together instead of shrinking targets.; A local typography cap is not release evidence: remeasure the actual production hero after the source revision and deployment identifiers change. - Learning journal: Oscillator is a browser music studio that demonstrates global pattern state, Web Audio lifecycle cleanup and routeable studio/build pages. - Source paths: src/audio/engine.js, src/audio/engine.lifecycle.test.js, src/state/studio.js, src/state/studio.test.js, src/components/Sequencer.jsx, src/styles.css - Example topics: Coalesce async audio starts; Prove pending starts can be cancelled; Only show the playhead while playback is active; Derive preset identity from the current patch - Limitations: The studio runs entirely in the browser; it does not stream audio or save patterns to a server.; Audio support depends on the browser exposing AudioContext. ## Lens — Live on Vura Mobile metrics and charts arrive earlier, server reports show their filter snapshot, and cohorts retain a labeled scrollable table. The real bounded report API and all chart ranges passed hosted checks. - Reference: https://whatfw.com/templates/status/what-starter-lens - Public source: https://github.com/CelsianJs/what-starter-lens - Live demo: https://what-starter-lens-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source ca842dfb5f359246f709f3f7ac6c93804e64f86a is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Compacting mobile analytics hierarchy and clarifying report snapshots and cohort scrolling. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: A small metadata flag can keep chart components from flattening every metric into the same visual grammar.; Serverless examples should teach safe request handling next to happy-path charts.; Label response snapshots explicitly when controls can change independently. - Learning journal: Lens is a client analytics dashboard with a serverless report endpoint, synthetic event data and CSV export. - Source paths: src/state.js, src/api/report.js, src/api/bounded-json.js, src/data.js, src/styles.css - Example topics: Treat filters as the source of truth; Post only the filter contract to the function; Let chart meaning choose the orientation; Block duplicate report refreshes - Limitations: Events are synthetic fixtures, not customer telemetry.; The report endpoint computes a response from posted filters; it is not a warehouse query service. ## Harbor — Live on Vura Incident quick actions update visible controls and activity; restored saved views are validated and deduplicated. The industrial console is compact on mobile and remains a browser-local simulation. - Reference: https://whatfw.com/templates/status/what-starter-harbor - Public source: https://github.com/CelsianJs/what-starter-harbor - Live demo: https://what-starter-harbor-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, unit tests, production build, route smoke and desktop/mobile browser flows. The matching official Playwright image includes Chromium and WebKit; no tests were removed.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 3d66fdf519082e91ca9722b3dcbe08c1293c2720 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Repairing stale incident controls after saved quick actions and making saved filters distinguishable. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Dashboards feel sharper when each region owns a distinct decision, not the same number in a different box.; Local persistence should be a capability, not a prerequisite for routeable app behavior.; A signal update cannot refresh a record sampled once during component setup.; Use content-fit alignment where adjacent panels have different amounts of information. - Learning journal: Harbor is an operations console reference for filters, incident overrides, saved views, activity logs and routeable detail pages. - Source paths: src/state/ops.js, src/routes.js, src/pages/Build.jsx, src/pages/IncidentDetail.jsx, src/styles.css - Example topics: Layer local overrides over seed incidents; Compute deploy risk display once; Capture identity, not the changing incident; Use the shared stylesheet on application routes - Limitations: Harbor edits are local simulation state, not shared incident-management storage.; No real service monitors, deploy systems or alert feeds are connected. ## Gather — Live on Vura Ingredient checks persist across routes and reload, with remaining counts and clear controls independent of meal planning. The terracotta recipe and market notebook remains browser-local. - Reference: https://whatfw.com/templates/status/what-starter-gather - Public source: https://github.com/CelsianJs/what-starter-gather - Live demo: https://what-starter-gather-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 68972b5eb8e3ab375c99dd80ad25891b4ebe29f4 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Persisting ingredient checklist state across navigation, with remaining counts and clear controls. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Small native controls can teach state transitions more clearly than a hard-coded demo shortcut.; Persist user intent by stable item identity while deriving completion from the current list.; Enlarge the associated label hit area while preserving native control geometry. - Learning journal: Gather is a recipe and meal-planning starter with static recipe routes, client filters, scaled servings and a derived shopping list. - Source paths: src/state/planner.js, scripts/static-aliases.mjs, src/pages/Build.jsx, src/pages/RecipeDetail.jsx, src/styles.css - Example topics: Choose the target day explicitly; Derive grocery totals from the plan; Emit every recipe detail alias; Store market checks by ingredient identity - Limitations: Recipes and nutrition-like details are fixtures for interaction design, not a live recipe API.; Planner and shopping list state stays in the browser. ## Marginalia — Live on Vura Complete authored essays, useful sidenotes and related reading replace shallow article previews. Reading durations derive from actual text; local bookmarks and static no-JS reading work. - Reference: https://whatfw.com/templates/status/what-starter-marginalia - Public source: https://github.com/CelsianJs/what-starter-marginalia - Live demo: https://what-starter-marginalia-fae244da.vura.app/ - Checks: Delivery-owner progress report: Reported, not independently verified — Local implementation reported complete. Independent check results and public release evidence have not been recorded here yet.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 1e66315f13ac82b1b1c66ad4a9c35c3b1b451182 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Expanding substantive essays, related reading and useful sidenotes, with reading time derived from actual text. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: In static sites, client islands still need reactive branches for empty, saved and cleared states.; Editorial metadata should describe actual content rather than set a target the content must pretend to meet. - Learning journal: Marginalia is a static editorial site with client islands for search, bookmarks and reading progress. - Source paths: src/server/render.mjs, src/client/main.jsx, src/content/articles.mjs, src/shared/site.css - Example topics: Make static search an island; Fallback when localStorage is unavailable; Derive reading duration from the actual essay; Use the shared stylesheet on application routes - Limitations: Bookmarks are local reading-list state, not an account feature.; Search uses the bundled article index; there is no hosted search backend. ## Meridian — Live on Vura Guide context carries into the planner without silently replacing saved plans. Rich logistics, coherent fixed-slot movement and the current-state route map are verified on desktop and mobile. - Reference: https://whatfw.com/templates/status/what-starter-meridian - Public source: https://github.com/CelsianJs/what-starter-meridian - Live demo: https://what-starter-meridian-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source cb13cf0400765cda9583a415a07c729ed12e0c5a is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Carrying selected guide context into the planner and reconciling itinerary order, days and times. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: A small CSS alignment rule can make an island feel intentional instead of stretched by its sibling content.; Static script JSON needs the same rendering-boundary care as visible HTML.; Distinguish activity identity, schedule slots and real timestamps before implementing itinerary movement.; Verify rendered text dimensions as well as logical SVG geometry. - Learning journal: Meridian is a static travel-planning reference with build-time guide pages and a client-mounted itinerary planner island. - Source paths: src/server/render.mjs, src/client/main.jsx, scripts/build.mjs, scripts/smoke.mjs, src/content.mjs, src/styles.css - Example topics: Decode escaped script JSON before mounting; Group route state from one stop list; Move activities without moving the schedule clock; Fit planner controls to their content - Limitations: Trip data is fictional and local-only.; The planner is client-mounted over static fallback HTML; it is not SSR-preserving hydration. ## Cartograph — Live on Vura Basket snapshots reject stale quote replies, quantity replacement preserves focus and receipt reset clears the visible record immediately. Product and quote controls appear earlier without changing its outdoor identity. - Reference: https://whatfw.com/templates/status/what-starter-cartograph - Public source: https://github.com/CelsianJs/what-starter-cartograph - Live demo: https://what-starter-cartograph-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Continuous keyboard editing: Failed — Clearing the cart quantity removed its row before replacement typing could finish. A row-local draft and controlled commit path are being verified.; Final reviewed source and live refinement: Passed — Source 255865a0f563baa7dab8659c12ea63a773895d15 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; Continuous keyboard editing: Passed — Live blank-to12 quantity replacement keeps the same focused DOM input and cart row, updates the subtotal to$2,976 and persists on reload. Remove remains a separate explicit action.; October workflow and brand audit: Reported, not independently verified — Guarding server quotes against changed baskets and stale replies, with earlier product and quote controls. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: For replacement editing, canonical app state and transient DOM text can intentionally be different for a few keystrokes.; Use the same content source for UI, API validation and static hosting shape.; Async results need snapshot ownership, and resettable views must read current state reactively. - Learning journal: Cartograph is a hybrid commerce reference with static catalog routes, local cart state and a serverless field-stock quote endpoint. - Source paths: src/state/cart.js, src/api/quote.js, scripts/build-vura.mjs, test/cartograph.test.js, src/pages/Receipt.jsx, src/pages/Cart.jsx, src/styles.css - Example topics: Validate quantity text before committing it; Let the DOM hold a blank draft quantity; Validate quote requests on the function boundary; Read the receipt inside the reactive branch - Limitations: Stock and receipts are fixtures; no order, payment, fulfillment or durable inventory is created.; The serverless quote validates the posted cart but does not reserve stock across visitors. ## Form — Live on Vura Case studies now explain program, material and design rationale, and a selected study can seed an empty brief without overwriting edits. Drawings and the vermillion drafting identity remain intact. - Reference: https://whatfw.com/templates/status/what-starter-form - Public source: https://github.com/CelsianJs/what-starter-form - Live demo: https://what-starter-form-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 6a2bf99a4058c1ba138926226eb7ee12fffdb41d is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Deepening project materials, program and rationale and carrying a selected study into the brief. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: When the state model is already clean, a design repair can stay in layout and proof rather than code architecture.; Do not describe these islands as hydrated server markup; they are client-mounted interactive regions.; Contextual entry should seed empty work, not silently replace an existing draft. - Learning journal: Form is a static architecture-portfolio starter with project detail pages, a filter island and a local proposal-brief generator. - Source paths: src/server/render.mjs, src/client/main.jsx, scripts/build.mjs, scripts/smoke.mjs, src/content.mjs, src/styles.css - Example topics: Keep a local proposal preview computed; Verify accessible activation when pointer layout is dense; Resolve study context without overwriting saved edits; Use the shared stylesheet on application routes - Limitations: Proposal data is local-only and never submitted to a CRM or server.; The portfolio content is fictional and has no analytics or lead capture endpoint. ## Beacon — Live on Vura Speaker/session relationships, fuller abstracts, contextual agenda saves and a real folded calendar download are operational. Static details and saved-only agenda behavior passed. - Reference: https://whatfw.com/templates/status/what-starter-beacon - Public source: https://github.com/CelsianJs/what-starter-beacon - Live demo: https://what-starter-beacon-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 3099cbbd6a69e4aaa60379e352197f8b14ff1dcf is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Adding fuller session details, speaker relationships and actual calendar download alongside the preview. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Interactive islands may need a different accessible link structure than their no-JS fallback.; Starter pages should foreground the workflow object, not only the aesthetic.; Export proof should inspect the actual file and format, not just visible preview text. - Learning journal: Beacon is a static event site with session and speaker routes plus a local agenda island that exports VCALENDAR text. - Source paths: src/client/main.jsx, src/server/render.mjs, scripts/build.mjs, scripts/smoke.mjs, src/calendar.mjs, src/styles.css - Example topics: Escape VCALENDAR fields before export; Compute the calendar from saved sessions; Fold calendar lines by UTF-8 bytes; Use the shared stylesheet on application routes - Limitations: Sessions and speakers are fictional event fixtures.; Agenda state and ICS output are local-only; there is no ticketing, sync or external calendar API. ## Finch — Live on Vura Practice cards advance reactively with reset reveal state, progress and concrete continuation links. Touch controls, completed lesson navigation and local persistence passed. - Reference: https://whatfw.com/templates/status/what-starter-finch - Public source: https://github.com/CelsianJs/what-starter-finch - Live demo: https://what-starter-finch-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 4db4cf55704c251d628cec58afd7f76866d3784d is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Repairing card advancement through reactive reads and clarifying progress and lesson continuation. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Debounce background persistence, but synchronously save user actions that feel final.; Run-once setup owns stable resources; changing reads and concrete navigation targets belong at reactive boundaries. - Learning journal: Finch is an educational starter with lessons, quizzes, flashcards and locally persisted progress. - Source paths: src/state/progress.js, src/data/lessons.js, src/routes.js, src/pages/Practice.jsx, src/styles.css - Example topics: Persist progress without duplicating derived counts; Read the current practice card through accessors; Use the shared stylesheet on application routes - Limitations: Progress is local to the browser and is not a hosted student account.; Lesson content is a framework-learning fixture, not a certified curriculum. ## Tally — Live on Vura Invoice lines can be removed and recovered, dates and draft status are clear, and line/export calculations use the same safe operands. Focus, totals, receipt and responsive labels passed. - Reference: https://whatfw.com/templates/status/what-starter-tally - Public source: https://github.com/CelsianJs/what-starter-tally - Live demo: https://what-starter-tally-fae244da.vura.app/ - Checks: Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Continuous keyboard editing: Failed — The numeric/text update replaced the input DOM node and moved focus to the body. Keyed accessor rows are being verified to preserve continuous typing and persistence.; Final reviewed source and live refinement: Passed — Source 3dc5ea4fdad1afb13bb17a69ac958675ab95c586 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; Continuous keyboard editing: Passed — Live continuous replacement typing retains the same connected, focused input DOM nodes; complete values and updated totals persist. The earlier remount/focus-loss failure is closed by keyed accessor rows.; October workflow and brand audit: Reported, not independently verified — Adding reversible line removal and clearer invoice dates, draft state and mobile ledger context. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Editable tables should use identity-preserving loops before reaching for imperative refocus code.; Dense editor grids need both column math and responsive labeling, not one or the other.; Derived financial UI should guard calculations even when persistence is local-only.; Editor recovery and displayed math should follow the same canonical operands as exported totals. - Learning journal: Tally is a client invoice workspace with editable drafts, computed totals, direct receipt routes and local JSON export. - Source paths: src/state/workspace.js, src/data/invoices.js, scripts/static-aliases.mjs, test/invoices.test.js, src/pages/InvoiceDetail.jsx, src/styles.css - Example topics: Keep invoice totals derived; Preserve line identity while editing; Generate every direct invoice URL; Use the shared stylesheet on application routes - Limitations: Exports are local JSON only; no invoice is sent, paid or filed.; The starter does not claim tax, payment, compliance or accounting coverage. ## Drift — Live on Vura The List filter reacts immediately, edge moves are disabled and named, and lane orientation is clearer. The spatial planner preserves local state and its distinct lilac and peach identity. - Reference: https://whatfw.com/templates/status/what-starter-drift - Public source: https://github.com/CelsianJs/what-starter-drift - Live demo: https://what-starter-drift-fae244da.vura.app/ - Checks: Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source f4c68cb50c7e5d67597b73a7cd6f98bfc23551dc is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Repairing stale assignee filtering in List view and disabled edge moves, with clearer lane orientation. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: Shared route state is only useful if restoration cannot poison every route at startup.; Derived collections that change after mount belong in accessors, not setup snapshots.; Normalize measurement tolerances without reducing the authored target size. - Learning journal: Drift is a project-board starter showing shared state across board, list, detail and activity routes. - Source paths: src/state/board.js, src/routes.js, test/browser/drift.spec.js, src/pages/Board.jsx, src/styles.css - Example topics: One card source feeds board and list views; Read the filtered list after setup; Use the shared stylesheet on application routes - Limitations: Planner edits and export data are browser-local.; The board models workflow interactions, not team authorization or collaboration. ## Bloom — Live on Vura Dated manual watering updates reminders, undated legacy records stay honest, plot assignment displays correctly and observations have history. Botanical silhouettes and responsive code guides are verified. - Reference: https://whatfw.com/templates/status/what-starter-bloom - Public source: https://github.com/CelsianJs/what-starter-bloom - Live demo: https://what-starter-bloom-fae244da.vura.app/ - Checks: Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source 57cd10e9e295b9dda7b84217678d370ccf1e9960 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Repairing dated watering urgency and plot assignment display, and adding observations and botanical detail. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: When the UI offers one select per item, the state mutation should enforce that same uniqueness invariant.; Small starters should show recovery paths because agents will copy them into larger apps.; Preserve unknown dates as unknown; manual care reminders are not sensor measurements.; Contain literal code within its own scroller instead of changing source text to fit the page. - Learning journal: Bloom is a gardening planner starter with plant catalog routes, plot assignments, watering journal state and derived care queues. - Source paths: src/state/garden.js, src/routes.js, src/pages/Build.jsx, src/utils/care.js, src/styles.css - Example topics: Move one plant to one plot; Derive a care queue from source state; Use local calendar days for the next soil check; Use the shared stylesheet on application routes - Limitations: Plant and care data are fictional fixtures.; Garden state is browser-local and not a synchronized account. ## Signal — Live on Vura Both incident detail routes render, request loaders use real timestamps and the stylesheet is served correctly. Cached overview and private uncached snapshot behavior passed live proof. - Reference: https://whatfw.com/templates/status/what-starter-signal - Public source: https://github.com/CelsianJs/what-starter-signal - Live demo: https://what-starter-signal-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Live public asset and render proof: Failed — The page links styles.css, but public HTTPS returns404 for that CSS asset and the browser uses default unstyled text. The server-rendered timestamp displays unknown; local source diagnosis identified a loader API mismatch.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Live public asset and render proof: Passed — Public styles.css now returns200 text/css from the recorded deployment; the rendered body is styled. Overview ISO stamps repeat within30seconds, while snapshot stamps change with private/no-store. The prior unknown stamp is absent.; Final reviewed source and live refinement: Passed — Source 4b8d855c3479476ac2cfe4e7b392e5d2e8a0f761 is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Adding the missing detail route for the second active incident while preserving verified loader and cache behavior. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: For deployable metaframework features, explicit route metadata beats clever abstraction.; Server-rendered Vura pages should read request data through the framework loader hook, not guessed component props.; When static scanners require literal strings, boring one-line metadata can be the safest output contract.; Direct-route completeness is part of the content contract, even when a dashboard already lists the record. - Learning journal: Signal is a Vura server-rendered status page showing cached output, page config and a small serverless health route. - Source paths: src/pages/index.tsx, src/api/health.ts, src/pages/snapshot.tsx, src/pages/build.tsx, src/pages/incidents/webhook-retry-spike.tsx, src/site/styles.css - Example topics: Declare a cached server-rendered page; Keep serverless route metadata literal; Read the incident from its loader contract; Use the shared stylesheet on application routes - Limitations: Status data is fictional seed data.; The server-render proof demonstrates cache behavior; it is not an uptime monitor. ## Orbit — Live on Vura Changed booking drafts invalidate old holds and ignore late replies; service selection proceeds into booking and cancellation history survives reload. Keyboard/date controls and local calendar downloads work. - Reference: https://whatfw.com/templates/status/what-starter-orbit - Public source: https://github.com/CelsianJs/what-starter-orbit - Live demo: https://what-starter-orbit-fae244da.vura.app/ - Checks: Implementation-owner local checks: Reported, not independently verified — Build, targeted tests and browser journeys are reported passing. Independent code, design and clean-consumer verification are still required.; Independent visual quality review: Passed — Actual desktop and mobile screenshots were reviewed after domain-specific layout refinements. Final review cleared the presentation; functional hosting checks remain separate.; Public source and hosted release: Passed — Source, README and BUILD guide are published. The Vura deployment is ready; HTTPS home, build guide and genuine unknown404 were checked. Local clean-install and browser workflows are distinct from this hosted route proof.; Published source CI: Passed — GitHub CI passed at the recorded source commit: clean install, tests, production build and the configured Chromium browser or smoke workflows. Public README and BUILD files exactly match this checkout.; Post-refinement hosted route check: Passed — Fresh HTTPS checks returned200 for home and the in-app build guide, and404 for an unknown path. Source comparison confirms only README or CI configuration changed; the hosted application artifact is unchanged.; Independent live design audit underway: Reported, not independently verified — Fresh desktop, mobile and product-detail screenshots are captured. Claude Opus5.5 at medium effort is reviewing the rendered evidence and source; this is not a passed design verdict or a new release.; Opus-guided refinement source and release: Passed — Independent code/spec review cleared the accepted changes; this recorded source workflow passed, the production build completed and the existing Vura project reports ready production. Live screenshots and native workflow evidence are captured separately.; Final reviewed source and live refinement: Passed — Source a2a5fbafb9cd1d563b6e5c6715abb01e1a1c78dc is published and its workflow passed. The existing Vura project reports ready production at the recorded deployment. Fresh desktop/mobile/detail screenshots and native workflow proof confirm the accepted refinements; local and hosted checks remain separate evidence.; October workflow and brand audit: Reported, not independently verified — Invalidating obsolete booking holds after draft changes and making service selection and cancellation history consistent. Implementation and fresh release verification are pending; this is not a new deployment claim.; October final local product and code gates: Passed — Production builds, app regressions and desktop/mobile workflows pass. Independent reviewers cleared the frozen source after async ownership, stale views, storage recovery and guide-width repairs. Current demo/source links still identify the previous verified deployment.; October published source and hosted workflow release: Passed — Reviewed source merged after configured CI passed, then built and deployed through the public CLI. Fresh released desktop/mobile captures, actual assets and critical workflows passed; deployment and source identifiers match this record.; October shared typography release and fresh rendered route evidence: Passed — Ready production deployment and live response identifiers match the published source checkpoint. Fresh home, product and build routes returned 200 at 1440 by 900 and 390 by 844, with six actual viewport captures, 16px body text, no horizontal page overflow or runtime error overlay. Mobile primary navigation responds and keyboard focus is recorded. - Lessons: A dramatic display face still needs route-level clamps when the workflow starts below the headline.; A UI fallback can become a security or correctness bug when copied into a server boundary.; Generate download URLs at the interaction boundary rather than storing unsafe URLs in render state.; A validated response authorizes its submitted draft, not whichever controls happen to be visible later. - Learning journal: Orbit is a hybrid scheduling reference with local reservations, serverless availability validation and safe ICS download. - Source paths: src/state/booking.js, src/api/availability.js, src/data/studio.js, src/pages/Reservations.jsx, test/orbit.test.js, src/styles.css - Example topics: Validate local reservations strictly at the API boundary; Download ICS through a temporary Blob URL; Permit booking only from the verified draft; Use the shared stylesheet on application routes - Limitations: Reservations are private to the current browser unless a durable calendar backend is added.; The availability function validates local and demo holds, but it does not create shared locks across users.