v1.0 tag-cut: gap register + execution plan (PR 1/4)#13
Conversation
Single source of truth for the 30 gaps between RC1 and v1.0.0 tag-cut. Integrates the 2026-05-20 RC1 architecture archaeology and six parallel deep-dive subagent reviews (architecture, security, pipeline, embedded-DB, docs, quality). - gap-register.md: 30 gaps in 7 categories with evidence, fix, and effort. - execution-plan.md: 3-day sequenced plan (Day 1 mechanical doc + code, Day 2 storage + CI, Day 3 operator-led governance + tag). - filigree-issue-bodies.md: pre-drafted bodies for the 29 v1.0 issues + 24 v1.1 backlog issues, with dependencies wired. Closes the planning phase of the v1.0 tag-cut work. Subsequent PRs in this branch close the gaps individually.
There was a problem hiding this comment.
Pull request overview
Adds a new canonical planning/artifact set under docs/implementation/v1.0-tag-cut/ to drive the RC1 → v1.0.0 tag-cut process (gap register, execution plan, and pre-drafted Filigree issue bodies), intended to supersede the older v0.1-publish planning surface.
Changes:
- Introduces a v1.0 tag-cut “home” README with reading order and pointers to the planning artifacts.
- Adds a detailed gap register with evidence citations, severities, and exit criteria for tag-cut readiness.
- Adds an execution plan and pre-drafted Filigree issue bodies to operationalize gap closure.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| docs/implementation/v1.0-tag-cut/README.md | Entry-point README describing the new v1.0 tag-cut artifact set and reading order. |
| docs/implementation/v1.0-tag-cut/gap-register.md | Canonical gap register enumerating tag-cut blockers with evidence, fixes, and effort estimates. |
| docs/implementation/v1.0-tag-cut/execution-plan.md | Day-by-day plan sequencing gap closure work across engineering/operator streams. |
| docs/implementation/v1.0-tag-cut/filigree-issue-bodies.md | Templates for filing Filigree issues corresponding to each gap plus v1.1 backlog items. |
Comments suppressed due to low confidence (1)
docs/implementation/v1.0-tag-cut/filigree-issue-bodies.md:19
- This doc introduces a new reusable Filigree label namespace
category:*(e.g.category:docs,category:storage). ADR-025 requires new reusable label namespaces be recorded at first use (docs/clarion/adr/ADR-025-minor-shared-standards.md:25-40). Please either registercategory:*in ADR-025 (MSS-1 table) or switch to an already-standardized label taxonomy.
**Filing convention**: every v1.0 issue gets `release:v1.0` + the
priority-appropriate `priority:Pn` label + a `category:<cat>` label. The
v1.1 backlog items get `release:v1.1` + the same category labels.
## v1.0 issues
### GOV-01 — Live GitHub governance is permissive
- **title**: `[v1.0 blocker] Enable live GitHub governance: branch protection, ruleset, RELEASE_GOVERNANCE_TOKEN`
- **priority**: P1
- **type**: feature
- **labels**: `release:v1.0`, `category:governance`, `tier:a`
- **body**:
> Closes GOV-01 in `docs/implementation/v1.0-tag-cut/gap-register.md`.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| | File | Purpose | | ||
| |------|---------| | ||
| | [`gap-register.md`](gap-register.md) | Single source of truth for every gap between the current RC1 commit and a defensible `v1.0.0` tag. 24 gaps in 7 categories with evidence, fix, and effort. | |
| **Date**: 2026-05-22 | ||
| **Branch**: `RC1` at `4dd7b63` | ||
| **Status**: 24 gaps open against the `v1.0.0` tag-cut criterion. | ||
|
|
| | Code bug (federation error-code) | 1 | 15 min | | ||
| | **Total** | **30** | **~13 hr** | |
|
|
||
| **Date**: 2026-05-22 | ||
| **Closes**: every gap in [`gap-register.md`](gap-register.md). | ||
| **Total effort**: ~13 hours engineering + ~3.5 hours operator. |
| **Filing convention**: every v1.0 issue gets `release:v1.0` + the | ||
| priority-appropriate `priority:Pn` label + a `category:<cat>` label. The | ||
| v1.1 backlog items get `release:v1.1` + the same category labels. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5ff8f6cc83
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| echo "$(git rev-parse HEAD)" > crates/clarion-storage/migrations/published_build.txt | ||
| git add crates/clarion-storage/migrations/published_build.txt | ||
| git commit -m "release: mark v1.0.0 as published-build baseline" |
There was a problem hiding this comment.
The runbook writes published_build.txt using git rev-parse HEAD before the marker commit is created, then creates the commit and tags afterward; this means the recorded ref is the parent commit, not the final v1.0.0 tag commit the plan says STO-03 should capture. If operators follow these exact steps, the migration baseline is anchored to the wrong release ref and the tag-cut audit trail is inconsistent.
Useful? React with 👍 / 👎.
| (The 24-count from the executive summary collapsed some related items; | ||
| this register breaks every item out individually for tracking. The 1.0 | ||
| blocker count is unchanged.) |
There was a problem hiding this comment.
The register says it "breaks every item out individually for tracking" and totals 30 gaps, but Category 7 has no standalone gap and explicitly reuses CI-02, so the summary count is inflated by one. This creates a tracking mismatch versus per-gap execution/issue planning and can cause false "missing issue" or progress-accounting noise when consumers expect one distinct item per counted gap.
Useful? React with 👍 / 👎.
| - **title**: `[v1.0 blocker] Enable live GitHub governance: branch protection, ruleset, RELEASE_GOVERNANCE_TOKEN` | ||
| - **priority**: P1 | ||
| - **type**: feature | ||
| - **labels**: `release:v1.0`, `category:governance`, `tier:a` |
There was a problem hiding this comment.
The document states that every v1.0 issue should include a priority:Pn label, but the provided templates omit that label set (for example GOV-01 uses tier:a without priority:P1). If these templates are used as written, issue metadata will be inconsistent with the declared filing convention, which undermines priority-based filtering/queries during release triage.
Useful? React with 👍 / 👎.
|
Superseded — the v1.0 tag-cut work in this stacked chain has all landed on |
Summary
First of a stacked four-PR series closing the gap between RC1 and a defensible
v1.0.0tag.This PR adds the canonical planning artifacts under
docs/implementation/v1.0-tag-cut/:gap-register.md— single source of truth for the 30 gaps in 7 categories (governance, docs, security, CI, storage, tests, code), evidence-cited to file:line, each with concrete fix + effort.execution-plan.md— day-by-day sequenced plan: Day 1 mechanical doc + code fixes (this PR series), Day 2 storage + CI hardening, Day 3 operator-led governance + smoke + tag-cut.filigree-issue-bodies.md— pre-drafted bodies for 29 v1.0 issues + 24 v1.1 backlog items. All 53 issues are already filed in Filigree with dependencies wired (DOC-06 → DOC-09 → STO-03is the convergence path on the tag-cut commit).README.md— entry point + reading order.Synthesises the 2026-05-20 RC1 architecture archaeology with six parallel deep-dive subagent reviews executed 2026-05-22 (architecture, security, pipeline, embedded-DB, docs, quality).
PR series
v1.0/01-tag-cut-planrelease/1.0v1.0/02-internal-doc-refreshv1.0/03-operator-docsv1.0/04-code-fixesThe integration target
release/1.0is at517d4b8(the pre-dogfood commit). PR #12 (RC1 → main) is superseded by this series; after all four PRs merge torelease/1.0, a finalrelease/1.0 → mainPR will carry the v1.0 stack to main for tag-cut.Closes
Planning-phase work; no gap-register entries directly closed by this PR (the four following PRs close them).
Test plan
No code or operational change. CI floor green on the integration branch.
🤖 Generated with Claude Code