Files
poli0981andClaude Opus 5 8be01829f7 docs: record the v1.0.0 release and what is still open
Status header, the docs/15 progress table and the docs/00 §10 manual list now
say where the project actually is: all six phases done, v1.0.0 tagged and
released, submitted to the Chrome Web Store and in review.

§10 gains two items that were being carried in commit messages and memory
rather than anywhere a reader would find them:

- `npm run dev:firefox` is untested against the dependency overrides. Four of
  them sit under web-ext-run and no gate exercises that script. Firefox is a
  v1.0 non-goal so it blocks nothing, but nobody should assume it works.
- The 2 s parse budget is unmeasured on a real browser. The recorded 2869 ms is
  a jsdom figure and settles nothing either way.

The decision log gains the overrides rationale and why the release
announcement is continue-on-error.

The review-habit note is updated with phase 4 and 5 (19-of-33 and 8-of-20
confirmed), plus the two patterns this build kept demonstrating: the worst
findings were in work added earlier in the same branch, and three defects
reached main that no automated gate could have caught — a missing space, a
glyph that reads as a letter, and a permission grant that failed CI at startup
with no jobs and no log.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-26 18:33:22 +07:00
..