docs: record the v1.0.0 release and what is still open - #8
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the status docs in line with reality now that v1.0.0 is released and
submitted to the store.
docs/00status header: all six phases done, v1.0.0 tagged and released,submitted to the Chrome Web Store and in review.
docs/15progress table: phase 5 ✔, plus a row for the release itself.docs/00 §10: item 5 records the submission and what remains (promo images,the store URL); item 6 records that CodeQL Default setup is already disabled
and which secrets are still optional.
Two open items were only living in commit messages and memory, which is not
where anyone would look for them. They are now in
§10:npm run dev:firefoxis untested against theoverridesblock. Fouroverrides sit under
web-ext-runand no gate exercises that script. Firefoxis a v1.0 non-goal so it blocks nothing — but it should not be assumed to
work.
2869 ms is jsdom and settles nothing.
The decision log gains the
overridesrationale and the reason the releaseannouncement is
continue-on-error. The review-habit note is updated throughphase 5, including the part worth remembering: the worst phase-5 findings were
defects in work added earlier in the same branch, and three defects reached
mainthat no automated gate could have caught — a missing space in thefooter, a glyph that renders as a letter, and a permission grant that failed CI
at startup with no jobs and no log.
🤖 Generated with Claude Code