Live by Significant Hobbies

Live helps a person name the life they want to live and walk toward it: what they still want to try, what persisted, what is worth doing next, and — each week — what they actually lived. It includes discovery, bucket lists, commitments, timelines, side quests, the weekly log, and personal history.

This is Live's canonical repository and issue tracker. Its Git history was preserved when it was extracted from Significant-Hobbies/significanthobbies. The retired Hub backend and PersonalSyncKit remain there. The former Journal product now lives inside Live as the weekly log at /journal; earlier AM/PM entries remain readable as archive.

Local development

pnpm install
pnpm dev
pnpm test
pnpm typecheck
pnpm build

The full Live app is canonical at https://significanthobbies.com. https://live.significanthobbies.com remains a full serving and sign-in alias for existing host-only sessions and browser-local guest records. The existing significanthobbies Worker and D1 remain Live's runtime and data authority. Only /hub, /health, /mcp, /v1/* and /landing/* retain the retired Hub backend through the existing service binding. Exactly /hub also delegates on the Live alias. Hub compatibility data stays backend-owned; the public homepage and discovery identity belong to Live.

Verification and retained work

On 2026-09-07, the public nine-choice quiz produced relevant Scholar hobby suggestions and small experiments. Sharing is scoped to that guest experience; authenticated saving, history, bucket-list planning and account persistence still require hands-on qualification.

The same-day production smoke failure was a JSON parsing defect in the checker: whitespace stripping and a greedy expression selected a nested app's name. The repaired check reads the top-level JSON name and rejects missing/null values. All five existing read-only smoke steps passed locally against the live hosts, including crawler routes, redirects, HEAD parity and the social image. This repair does not deploy application changes or qualify authenticated journeys.

The Hub login repair keeps private Hub intent through sign-in, cancellation, expiry and unavailable services without changing authentication identities or cookie domains. Local browser proof used actual Live-issued synthetic sessions and two-account summary isolation; receipts remain separate from hosted Google sign-in qualification. The intended private entry is https://live.significanthobbies.com/hub, while the public directory stays on the apex. No application deployment was performed for this repair.

Current signed-in acceptance gate

The 9 September provider failure is superseded by the 11 September owner verification: the existing Google OAuth client now authorizes the canonical callback while retaining its existing redirect entries. Native Chrome reached the authenticated Live Hub, and a synthetic bucket-list item was created, completed, reopened and persisted across reloads before being deleted; no pre-existing records changed. Source dc0ad9b5 is deployed at 100% traffic through deployment run 34599212391. Issue 14 remains open for two-account isolation and physical iPhone installation/launch plus cross-device use. The former GitHub Actions credential blocker is stale after the current successful deployment.

The 9 September security migration receipt records patched Next/Astro/Sharp dependencies, a preserved landing whitespace contract, 593 unit tests, full deployment-bundle compilation and 20 local guest/landing browser checks. Mobile landing evidence is from the local build. The operator's 9 September release receipt records source 207f11bff5e03207bbe0ffaf79fa446b4629ef72 deployed as Worker ecd54c8c-8df1-4c60-8f52-0942b3b89ced, deployment a10dc6ea-1707-4f3e-9021-4eb98cab8aa9, with its full source tag at 100% traffic. All six deployment gates and exact-source Quality, Browser CI and Docs passed. The actual 390px production landing returned 200 with readable heading spacing and no overflow. This is the dated release observation, not a fresh provider check; it does not resolve Google's registration requirement or qualify a real account.