docs: log PR #60 (Tier dedup) into PROGRESS.md register #42 (Option C) - #61
Merged
Conversation
Records the merged PR #60 under Option C — a single-purpose changelog entry about #60 only, with PR #59's provenance closed in the header lines (not the changelog prose). Three edit regions, nothing else: - Line 8: PREPEND a #60-only current entry (Tier inline-copy dedup in rate-limit.ts; delta 0/0/0; runtime unchanged; both checks green on 71e1c9d) and advance the "Last updated" stamp to 2026-07-20. The prior #58 current entry is NOT demoted or rewrapped — byte-identical. - Lines 9-10: advance Active-branch + Main-tip to the merged state; the Main-tip provenance chain now names 71e1c9d (PR #60) on top of da57070 (PR #58) via the PR #59 docs merge d5d0171 — this is where #59's zero-mention lag is closed, in provenance, not in changelog prose. - Register #42 row: convert part (b) the Tier inline copy to CLOSED (PR #60), add Tier (#60) to the closed set in the remaining-surface preamble and reword the now-inverted "NOT Message.role alone" clause (Message.role is now the last app-enforced inline union; the rest is structural), and append a parallel Tier-closure clause to the lead marker. The lead's open status and "Message.role primary" are byte-identical; (a) and (c) unchanged. Frozen-history invariant proven: the region from the #58 block's opening paren to end-of-line-8 is byte-identical before/after (sha256 8e5e0b32…), and the #58 block itself is byte-identical (sha256 a66bafd2…) — C did not demote it. Docs-only; Phase 7 stays ⬜; PIVOT_PLAN.md untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tornidomaroc-web
added a commit
that referenced
this pull request
Jul 21, 2026
…64) Records three register moves from one purpose: the db-types REQUIRED check can no longer pass on a wrong result, nor red on a third party's traffic. Logged under Option C — a single-purpose current entry, with docs-PR provenance closed in the header lines, not changelog prose. Four edit regions, nothing else: - Line 8: PREPEND a gate-integrity current entry (#40 closed, #43 opened+closed, #44 opened) and advance the "Last updated" stamp to 2026-07-21. The prior #60/#58 current entry is NOT demoted or rewrapped — byte-identical. - Lines 9-10: advance Active-branch + Main-tip to the merged state. The Main-tip provenance chain now names 3378dd8 (PR #63) on top of d8c8fde (PR #62) on 71e1c9d (PR #60) via the PR #61 docs merge b62cbd5 — this is where PR #62's zero-mention lag is closed, in provenance, not in changelog prose. - Register #40 row: CONVERT IN PLACE to CLOSED (PR #62, merge d8c8fde), per the #38 template for a closed row that keeps its history. The lead flips to ✅ and preserves the original marker after "Was:". The "Where addressed" cell records WHICH branch was taken — the content-aware skip; `storage` was NOT provisioned — so the untaken alternative is not later mistaken for unfinished work, and carries the honest limit (a fail-closed STATIC heuristic with a documented undecidable case, not a proof of application). Columns 2 and 3 are byte-identical: both remain historically accurate. - Register rows #43 and #44 APPENDED, strictly sequential. #43 (closed, PR #63) carries its residual IN the row per the #38 precedent — Docker Hub is also anonymous-quota'd, and a SUPABASE_CLI_VERSION bump can silently fall back to an ECR pull. #44 (open, unfixed) records the npx integrity gap so the class is not considered "handled" because #43 closed. Frozen-history invariant proven, both hashes before == after: primary (Option C region, old entry's opening paren -> EOL8) sha256 d0c031b5a7ee2623e7b0443e337a612411563cea5329235adcc57118e69776fd secondary (first "Prior update" -> EOL8) sha256 22019b90c7ae5884e7531abb7916eb095c41745ed2b80cb01b6ab91a117aaf20 The insert is 2615 bytes and the frozen region shifted right by exactly that (byte 32 -> 2647); "Prior update" markers stay 15, so nothing was demoted. The historical "#40" mention inside the frozen region (now byte 11030) still describes #40 as OPEN and is deliberately UNCHANGED: it was true when written, and editing it would break the invariant. Not touched: §1 (Phase 7 stays ⬜ NOT STARTED — #40 was bucketed Phase 7 and closed early, the phase is unchanged); register #39 (its repo↔live parity claim is unaffected by either fix and the row is marked non-closable); PIVOT_PLAN.md. Docs-only; no code, no migration, no DB. Co-authored-by: Claude Opus 4.8 (1M context) <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.
Docs-only. Logs the already-merged PR #60 (Tier inline-copy dedup in
rate-limit.ts, merge71e1c9d) intodocs/PROGRESS.mdunder Option C: a single-purpose changelog entry about #60 only, with PR #59's provenance closed in the header lines rather than the changelog prose.Three edit regions (nothing else)
71e1c9d) and advance theLast updatedstamp to 2026-07-20. The prior refactor: hoist KnowledgeBase.language domain to a single source of truth #58 current entry is NOT demoted or rewrapped — byte-identical.Active branch+Main tipto the merged state. The Main-tip provenance chain now names71e1c9d(PR refactor: import hoisted Tier in rate-limit instead of inlining the union #60) on top ofda57070(PR refactor: hoist KnowledgeBase.language domain to a single source of truth #58) via the PR docs: register #42 KnowledgeBase.language app-level closure + complete remaining surface #59 docs merged5d0171— where docs: register #42 KnowledgeBase.language app-level closure + complete remaining surface #59's zero-mention lag is closed, in provenance, not in changelog prose.Tierinline copy converted to CLOSED (PR refactor: import hoisted Tier in rate-limit instead of inlining the union #60) (per the row's refactor: hoist file_type domain to a single source of truth #56/refactor: hoist KnowledgeBase.language domain to a single source of truth #58 convention, not deleted); the remaining-surface preamble gainsTier(refactor: import hoisted Tier in rate-limit instead of inlining the union #60) and the now-inverted "NOTMessage.rolealone" clause is reworded (Message.roleis the last app-enforced inline union; the rest is structural); the lead marker gains a parallel Tier-closure clause. The🔎glyph andCLASS STILL OPEN — Message.role primarystay byte-identical; parts (a)/(c) unchanged.Frozen-history invariant (proven)
The region from the #58 block's opening paren to end-of-line-8 is byte-identical before/after (sha256
8e5e0b32…, 33 790 B), and the #58 block itself is byte-identical (sha256a66bafd2…, 2372 B) — C did not demote it. Pre-existing frozen tail unchanged (sha25622019b90…, 31 415 B).Scope
Docs-only; Phase 7 stays ⬜;
PIVOT_PLAN.mduntouched. No code, no DB, no migration. 4 lines changed, +4/−4.