docs: record the register #17 WIP preservation snapshot (tag, not a port) - #65
Merged
Merged
Conversation
…ort) Logs into register #17 that the ~3-month-old WIP stash of that exact surface (privacy/terms/refund bodies + ar.ts/en.ts legal keys) is now preserved as the annotated tag snapshot/stash-17-legal-i18n-20260501, pushed to origin and pointing directly at stash commit 3b41621 (base 75331a3) so the April-token provenance survives byte-exact. The row stays OPEN. Nothing was ported. The note records why a deliberate forward-port is required (all six files were rewritten on main since the base; 90bbd2c/P2.6c relit the legal pages) and the two blockers that port must clear first: the UNRATIFIED refund terms in the stash (14-day + refund@ vs the live 7-day + support@, and a backwards "Last updated"), which need a founder ruling before any refund copy ships, and the out-of-scope page.tsx RTL hero hunk. Register #17's row only. Line 8 is untouched, so the Option C frozen-history invariant is trivially preserved (line-8 sha256 identical before and after). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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. Touches one line of
docs/PROGRESS.md— register #17's "Where addressed" cell. Nothing else in the file changed.What this records
The ~3-month-old WIP stash of register #17's exact surface (the three legal page bodies + the
ar.ts/en.tslegalkeys) was the only carrier of unmerged work left in local state. It is now preserved as the annotated tagsnapshot/stash-17-legal-i18n-20260501, pushed to origin, pointing directly at stash commit3b41621(base75331a3, stashed 2026-05-01).No checkout, no
apply, no WIP commit — so the April-token provenance is byte-exact. The stash entry itself was never consumed and is still listed locally.What this does NOT do
Register #17 stays OPEN. Nothing was ported. The tag is an archive point, not a branch — do not merge that ref.
A deliberate forward-port is still required: all six files the stash touches were rewritten on
mainsince its base (notably90bbd2c/P2.6c relit the legal pages), so a rawstash applyconflicts on every file and would clobber P2.6c.Two blockers the eventual port must clear first, both recorded in the row:
main— it states a 14-day money-back guarantee (plus 30-day prorated annual) andrefund@tryknowflow.com, where the shipped page states 7-day andsupport@tryknowflow.com; it also moves "Last updated" backwards to Jan 2026. A founder ruling is required before any refund copy ships.page.tsxRTL hero hunk (rtl:lg:flex-row-reverse) to drop or split.The row also notes the port is larger than this stash: #17 additionally covers the auth left-panel tagline (
login/signup), which the stash does not touch, and #18 folds contact-domain unification into the same pass.Scope discipline
b16500e3…), so the Option C frozen-history invariant holds trivially. I deliberately did not prepend a changelog entry; rationale in the review note below.@@ -116 +116 @@.Checks
npm run typecheck→ exit 0.db-types: this PR touches no SQL migrations, so the regenerated types are byte-identical.🤖 Generated with Claude Code