docs: reconcile with v3.0.0–v3.2.0 reality (README, CHANGELOG backfill, FONTS recipe, DEPLOYMENT) - #397
Merged
Merged
Conversation
…NGELOG backfill, FONTS recipe, DEPLOYMENT theme prose)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
📚 What
/documentreconciliation after the theming epoch (v3.0.0 → v3.2.0). Drift was audited docs-vs-code across the repo; every concrete DEPLOYMENT.md value checked against the compose files came back ✓ (tools/check-doc-drift.shgreen before and after) — the fixes below are the prose that had fallen behind./editor+ save-as-own + guarded uninstall v3.2.0); "Persona Catalog" → Community Catalog;db/range 02..32; engine pin correctly attributed toengine/Dockerfile; the--pinnedno-rollback nuance (README previously claimed unconditional rollback)./wardrobenaming ruling) and v3.2.0 (F104 M2: widened font law, editor, save-as-own behindThemeWriteGatewith the fail-closed 409, in-statement uninstall guard, disclosure re-audit).--name-IDs='*'(the revision that shipped with Space Grotesk); the old "known limitation" paragraph reframed — the one open item (re-subsetting the five original vendored faces for OFL-record parity) is explicitly flagged as a/designdecision, not decided here; enforcement section documents the T205 vendored ∪ installed widening and all three write-path call sites.🚩 Flagged, not decided (owed to /design)
(ARCHITECTURE.md/MEMORY.md updates were made in the local planning corpus, which doesn't ship.)