8 Commits

Include renames

Author	SHA1	Message	Date
timmy	4cc5f4f7b1	feat: user-reported hard-stool follow-up with deterministic red-flag handoff (#67) ... Field finding #67: a hard/lumpy (Bristol 1-2) entry now asks a short follow-up before saving — difficult to pass, soreness, visible red blood, truly black/sticky/tarry versus dark brown, and dehydration. Every answer is user-reported and starts unanswered; nothing is inferred from the photo, and answering "dark brown" never silently escalates as black stool. A confirmed red-flag answer writes the same symptom flag manual logging already uses, so the existing deterministic escalation is the only escalation path. Mild reports get concise non-diagnostic self-care that states the photo cannot rule out bleeding, and it is withdrawn whenever a red flag is confirmed. - src/followup.js: pure follow-up contract (9 unit tests, tests/followup.test.js) - app.js + styles.css: follow-up block on the safety step for Type 1-2 entries only - tests/followup.acceptance.mjs: browser acceptance incl. that the AI suggestion surface still contains no symptom wording - CI + release builder gates: npm run test:followup, syntax checks, manifest gate - scripts/record_release_demo.mjs: records the real follow-up, mild guidance, and the black/tarry alert handoff with synthetic data	2026-10-09 08:10:43 +00:00
timmy	5aee7436f2	feat: make AI suggestions visibly provisional and correction-first (#13) ... Suggested, confirmed, and corrected AI states are now distinct in the log sheet, and correcting a suggested value clears the AI-confirmed state while keeping every user-entered field. Screen-reader copy states the AI confidence and who is in control. - src/suggestion.js: provenance state machine (pending/confirmed/corrected/manual) - app.js: renders provenance on the scan result and log steps, tracks corrections - tests/suggestion.test.js: unit coverage for the state machine and a11y copy - tests/provisional-suggestion.acceptance.mjs: browser acceptance + screenshots - record_release_demo.mjs: demo now reviews, confirms, and corrects the suggestion - CI, release builder, and release notes gate the new contract	2026-10-08 08:09:10 +00:00
timmy	dce668e72b	feat: guarantee manual fallback and in-session draft recovery (#12) ... Logging must never depend on AI availability, and an unsaved entry must not disappear when the user navigates away mid-log. - add src/vision-readiness.js so the photo flow consumes one readiness contract - when the worker is offline/disabled/unknown, offer no AI action and no analysis-consent prompt, and keep manual Bristol entry one action away - add src/draft.js and make the draft own the photo so a chosen photo and entered context survive a recoverable close or navigation, with a visible kept-draft summary and an explicit start over - drafts stay in session memory only: a photo awaiting consent is never persisted, and reload starts clean - service worker now refuses to cache image bodies in addition to analysis requests and no-store responses - tests: 2 new unit files, 3 service-worker privacy assertions (1 hold-out), 1 browser acceptance file, release-demo and CI/package assertions - release demo now visibly replays the vision-offline pass and the retained draft with synthetic data and an in-script assertion	2026-10-07 08:12:43 +00:00
timmy	463dff7f22	feat: harden mobile capture recovery (#11)	2026-08-26 08:07:30 +00:00
timmy	877b8a01f3	fix: make staging compatible with strict CSP	2026-08-21 15:01:05 +00:00
timmy	7e11154302	feat: add private subpage staging slice	2026-08-21 14:12:17 +00:00
timmy	a50afa6722	feat: simplify Timmy and add secure Hermes chat	2026-08-20 16:21:00 +00:00
timmy	58906f11d0	feat: ship photo-first Timmy prototype and sovereign vision spike	2026-08-19 01:54:29 +00:00