Refresh stale doc references (Color Guide v3.5, completion-authority tightenings)#85
Merged
Conversation
- Color Guide HTML version string 3.0 → 3.5 to match the v3.5 spec already in force across the codebase (issue #83, PR #84). - completion-authority.md: "Required tightenings (after this doc lands)" rewritten as "Tightenings (implemented)" with a link to PR #82, since all six tightenings have landed. Issue-ref format updated to current E-series naming (#59 Sprint E5 → #59 E5).
AtomicTrxn
force-pushed
the
lucid-mclaren-9f761f
branch
from
May 17, 2026 05:49
5d0c85f to
dc6b627
Compare
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.
Summary
Two stale doc references surfaced during a markdown audit of the repo.
design/Crosscue Color Guide.html— version string bumped3.0→3.5. The codebase has been on v3.5 since PR #84 (Color Guide v3.5 compliance pass), but the HTML's own header still claimed v3.0.docs/architecture/completion-authority.md— the "Required tightenings (after this doc lands)" section described 6 pending TODOs, but all 6 were implemented in PR #82 (E5 follow-up). Rewrote the section as "Tightenings (implemented)" with a per-item summary of what shipped, and dropped the now-irrelevant "Implementation order" section. Also fixed the issue reference format (#59 (Sprint E5)→#59 (E5)) to match current E-series naming.Other doc claims checked (not changed)
The full audit covered all 12 markdown files in the repo. Items intentionally left alone after verification:
README.mdDEPLOYMENT.mdprint()logcat exampledocs/privacy.mddocs/dependency-audit.mdpubspec.lockresolves drift 2.31.0, sqlite3 2.9.4, share_plus 12.0.2Clean files:
CONVENTIONS.md,CONTRIBUTING.md,ROADMAP.md,MODELS.md,crosscue/README.md,docs/index.md,ARCHITECTURE.md.Test plan
grep -rn "Version 3.0\|Sprint E5\|after this doc lands"across docs returns no matchesflutter analyze/flutter testare unaffecteddocs/architecture/completion-authority.mdand confirm the per-item summaries match what PR E5 follow-up: completion authority tightenings (#75) #82 actually shipped