chore: freeze v1 and hand main to the v2 workspace - #616
Conversation
Per blueprint/deploy.md in FSM1/cipher-box-next: one product version, one release train. Deletes pr-release-preview.yml and its scripts, release-gate.yml, cargo-lock-release-sync.yml, and ci-e2e's retrigger job; release-please becomes single-component and dispatch-only until the first v2.0.0 release candidate. v1 is frozen at 07376d0 as branch v1 / tag v1-freeze. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: c831bf0bf829
Root rust-toolchain.toml replaces the src-tauri pin and every rustup default stable step; workflows read the node version from package.json engines via node-version-file instead of hard-coded values. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 24baeffe4e13
.planning/ and .learnings/ are v1-era GSD state, superseded by the v2 blueprint corpus in FSM1/cipher-box-next and preserved on the v1 branch. Drops the matching lint-staged ignore and CodeRabbit path instructions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 20fd4c27a511
Copies blueprint/*.md and the CONTEXT.md glossary from FSM1/cipher-box-next as the normative in-repo source for the v2 build; CLAUDE.md drops the v1 terminology, TEE rules, and api:generate workflow in favor of the v2 pillars, security laws, and blueprint pointers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 5a304c87366d
|
Too many files changed for review. ( |
|
Warning Review limit reached
Next review available in: 29 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (9)
📒 Files selected for processing (2237)
✨ Finishing Touches🧪 Generate unit tests (beta)
|
Uninstalls the repo-local GSD tooling: the tracked profile, the GSD phase ship command, and the GSD-spawned ui-design agents. The untracked install (gsd-core, hooks, agents, commands, manifests) and its settings.local.json hook wiring are removed locally. crypto-privacy-reviewer, resolve-pr-reviews, the statusline hook, and the Entire CLI wiring stay. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 52aebe25f189
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #616 +/- ##
==========================================
+ Coverage 70.15% 77.10% +6.95%
==========================================
Files 160 200 +40
Lines 15570 34738 +19168
Branches 2003 2003
==========================================
+ Hits 10923 26785 +15862
- Misses 4392 7698 +3306
Partials 255 255
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Restores the ship pipeline nuked with the GSD install as /ship: GSD phase sub-commands replaced by the verify, security-review, crypto-privacy-review and simplify skills; todo logging becomes GitHub issues; the release-bot draft-PR dance drops with the deleted preview workflow; the SDK E2E gate generalizes to the blueprint testing.md suite map with the contract suite as the do-not-skip integration gate. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 0a2e480544cf
CLAUDE.md becomes an @AGENTS.md include, matching the pattern used in sibling repos so other agent harnesses read the same instructions. The stale v1-era AGENTS.md is replaced by the v2 instruction set; the inert GSD profile markers and refresh pointer are dropped. The crypto-privacy-review command gets its fence nesting fixed and stops writing reports into the deleted .planning tree. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 6bbb1eeb182e
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 035ca8acb89b
Drops the v1 feature and stack inventory in favor of the v2 design: the blueprint corpus as the documentation index, the target workspace layout, the v2 crypto and trust model, and a clear mid-rewrite status note with v1 frozen on its branch. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: 806bbd0ab71f
The render.yaml build command and the deploy-landing workflow still ran npm against a package-lock.json while the rest of the repo is pnpm. The lockfile is imported to pnpm-lock.yaml, landing pins its packageManager, and both build paths install with a frozen lockfile. Verified locally with a clean pnpm install and build. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UV6UZuSnSwnQE9dtYWE7S2 Entire-Checkpoint: a3756f928279
Executes the v1 freeze per blueprint/deploy.md (now also in-repo at
blueprint/deploy.md). The freeze branch and tag are already pushed:v1/v1-freezeat 07376d0 (cipher-box-v0.45.1 + staging-20260626-release-1); the open release PR #577 was closed unmerged.Commits:
pr-release-preview.yml(+ scripts),release-gate.yml,cargo-lock-release-sync.yml, and ci-e2e's retrigger job.release-please.ymlbecomes single-component (one product version, tagvX.Y.Zfrom 2.0.0, tauri.conf.json via extra-files) and dispatch-only until the first v2.0.0 release candidate. CLAUDE.md and docs/DEPLOYMENT.md updated to match.rust-toolchain.toml(replaces the src-tauri pin and everyrustup default stablestep); node version read frompackage.jsonengines vianode-version-file..planning/and.learnings/(2,200 files) are v1-era state, preserved on thev1branch; lint-staged and CodeRabbit references cleaned.blueprint/*.md+ theCONTEXT.mdglossary copied in as the normative in-repo build spec; CLAUDE.md rewritten for the v2 build (v1 terminology, TEE rules, and the api:generate workflow removed)..claude/— profile, agents, commands, hooks;settings.local.jsonstripped of GSD hook wiring (Entire CLI hooks kept).ship-phasereturns as.claude/commands/ship.md: verify → security/crypto review → simplify → local gates → CodeRabbit → PR → resolve reviews, with GSD sub-commands swapped for the skills flow and todo-logging swapped for deduped GitHub issues.AGENTS.mdthe harness-agnostic source of truth — the v2 instruction set moves toAGENTS.md;CLAUDE.mdbecomes an@AGENTS.mdinclude, so other agent harnesses read the same rules.