nesquena-hermes 43677b046d docs(rfcs): add anti-speculative-implementation conventions guidance ... When merging PR #2105 (Hermes Run Adapter RFC) the standing concern was that landing the RFC unconfirmed would invite the speculative-fragment implementation pattern we just had to put on hold with PR #2071 — well- written 651-LOC standalone scripts with no callers. Add a single bullet to the conventions block so the contract is explicit: an RFC is a design direction, not an invitation to PR fragments against it. Implementation slices need maintainer confirmation first. Applied during stage-341 build, not requested from @Michaelyklam — the guardrail belongs in the conventions doc itself rather than as a one-off ask on this PR.		2026-05-12 00:05:28 +00:00
..
images
pr-assets
pr-media	Clarify worktree session archive/delete semantics	2026-05-12 00:05:05 +00:00
rfcs	docs(rfcs): add anti-speculative-implementation conventions guidance	2026-05-12 00:05:28 +00:00
ui-ux
docker.md	security: harden production Docker image	2026-05-08 20:48:39 +00:00
EXTENSIONS.md
ISSUES.md
onboarding.md	docs: add first-run onboarding guide	2026-05-11 11:47:26 +08:00
supervisor.md	fix: harden persistent WebUI health checks	2026-05-04 15:30:37 -07:00
troubleshooting.md	docs(troubleshooting): bake the #1695 diagnostic flow into the error message + a new troubleshooting doc	2026-05-05 22:14:07 +00:00
wsl-autostart.md	docs: add WSL WebUI autostart helpers	2026-05-05 01:12:07 +00:00