3 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	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