Three-destination mobile shell with one dominant photo action
Free-text Timmy chat with local fallback
Authenticated same-origin Hermes gateway with private server-side continuity
Bounded text-only ledger context; photos and credentials excluded
Checked-in non-diagnostic workspace policy and release-specific demo
Evidence
42/42 unit and security tests passed
journal, photo-first, and sleek/chat Playwright acceptance passed
npm audit: 0 vulnerabilities
release secret scan: clean
real filtered-environment two-turn Hermes continuity: passed
release demo decoded and visually inspected
Deployment boundary
Hermes remains disabled by default. Public exposure still requires authenticated TLS, a dedicated profile/workspace, and operator review of its host/tool authority.
Closes #47
Closes #48
## What changed
- Three-destination mobile shell with one dominant photo action
- Free-text Timmy chat with local fallback
- Authenticated same-origin Hermes gateway with private server-side continuity
- Bounded text-only ledger context; photos and credentials excluded
- Checked-in non-diagnostic workspace policy and release-specific demo
## Evidence
- 42/42 unit and security tests passed
- journal, photo-first, and sleek/chat Playwright acceptance passed
- npm audit: 0 vulnerabilities
- release secret scan: clean
- real filtered-environment two-turn Hermes continuity: passed
- release demo decoded and visually inspected
## Deployment boundary
Hermes remains disabled by default. Public exposure still requires authenticated TLS, a dedicated profile/workspace, and operator review of its host/tool authority.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #47
Closes #48
What changed
Evidence
Deployment boundary
Hermes remains disabled by default. Public exposure still requires authenticated TLS, a dedicated profile/workspace, and operator review of its host/tool authority.