Repository navigation
docs(6.0): correct remaining first-user claims after the stable ship - #778
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
corvid-agent
left a comment
There was a problem hiding this comment.
CoS exact-head COMMENT on tip 59cf61a1 (docs first-user claims after stable ship).
Lifecycle gate FAILURE: cargo run -- change audit --strict reports paths not covered by an active change:
site/src/content/examples/ci-gate.mdxsite/src/content/examples/polyglot.mdxspecs/github/{context,github.spec,requirements,tasks,testing}.md
(ignored_paths note on specs/github/* does not waive SDD policy / configured specs tree.)
Author: cover those paths under the active change (or tip-move with an allowed --no-spec-change rationale where it applies). Tip-move retires this note. Not an APPROVE — gate red.
…er-the-stable-ship
…e-stable-ship verification
corvid-agent
left a comment
There was a problem hiding this comment.
CoS exact-head COMMENT on tip 55e63861 (prior cover was on 59cf61a1 — tip moved).
Lifecycle gate now SUCCESS after materializing change correct-remaining-specsync-6-0-docs-after-the-stable-ship (cover for site/ examples + specs/github/* that failed on the prior tip). Docs/site first-user claims look aligned with promote-executed v6.0.0 + dual-pin Action guidance; Windows dropped from 6.0 RC qualification in the github delta.
coverage still pending on this tip — settle that before human APPROVE/squash. Not an APPROVE (same-actor / coverage settle). Tip-move after further edits retires this note.
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"That's a nice looking export you've got there."
CI Summary
| Check | Status |
|---|---|
| Validate action.yml | ✅ Passed |
| Packaged Action Consumer | ✅ Passed |
| Dependency Audit | ✅ Passed |
| Code Coverage | ✅ Passed |
| Format Check | ✅ Passed |
| Docs Site | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (build, test, clippy) | ✅ Passed |
| VS Code Extension | ✅ Passed |
📋 Spec Validation Details
✅ SpecSync: Passed
| Metric | Value |
|---|---|
| Specs checked | 62 |
| Passed | 62 |
| Errors | 0 |
| Warnings | 0 |
| File coverage | 100% (107/107) |
| LOC coverage | 100% (148484/148484) |
Generated by specsync · Run specsync check --format github to reproduce
Powered by corvid-pet
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59cf61a1ac
ℹ️ 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".
…er-the-stable-ship
…e-stable-ship verification
Superseded by updated review.
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"Caw! Found a shiny new spec!"
CI Summary
| Check | Status |
|---|---|
| Validate action.yml | ✅ Passed |
| Packaged Action Consumer | ✅ Passed |
| Dependency Audit | ✅ Passed |
| Code Coverage | ✅ Passed |
| Format Check | ✅ Passed |
| Docs Site | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (build, test, clippy) | ✅ Passed |
| VS Code Extension | ✅ Passed |
📋 Spec Validation Details
✅ SpecSync: Passed
| Metric | Value |
|---|---|
| Specs checked | 62 |
| Passed | 62 |
| Errors | 0 |
| Warnings | 0 |
| File coverage | 100% (107/107) |
| LOC coverage | 100% (148484/148484) |
Generated by specsync · Run specsync check --format github to reproduce
Powered by corvid-pet
corvid-agent
left a comment
There was a problem hiding this comment.
CoS exact-head COMMENT on tip 3d3a9cc1 (prior cover was on 55e63861 — tip moved again).
Lifecycle + coverage both SUCCESS on this tip (change package cover held through the tip-move). Docs/site first-user claims still look aligned with promote-executed v6.0.0 + dual-pin Action guidance.
Required CI gate was still QUEUED at pulse time — settle that, then parent APPROVE + squash (SpecSync squash-only). Prior tip COMMENT does not cover this SHA.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3d3a9cc1e9
ℹ️ 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".
corvid-agent
left a comment
There was a problem hiding this comment.
COMMENT exact tip 3c1bc380 (moved past prior CoS COMMENT on 3d3a9cc1). Codex follow-ups deferred post-archive look fine. Waiting Required CI (trust/test/coverage/audit/Analyze rust still pending this tip) then parent/CoS APPROVE + squash ahead of #777.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c1bc380f4
ℹ️ 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".
corvid-agent
left a comment
There was a problem hiding this comment.
APPROVE exact tip 3c1bc380 — Required CI / Lifecycle / Trust green; SpecSync champion confirms archive-clean (covering change archived; .specsync/changes/ empty). Squashing now; #777 stays HOLD until its verifying change is archived on tip after this lands.
Summary
Correct remaining first-user 6.0 claims now that
v6.0.0is published.promoteexecuted on 2026-09-09 (run 34418860417) atb9ff3231(qualified asv6.0.0-rc.18).False claims corrected:
docs/RELEASING.md: stopped presenting "cutrc.17and promote" as the next 6.0.0 operator action. Records thatpromoteDID execute forv6.0.0on 2026-09-09. The how-to now uses a 6.0.1 /v6.0.1-rc.1example for the next cut. Dual-pin warning kept (@v6.0.0still embeds6.0.0-rc.14). Homebrew still documented as 5.2.0.docs/ci-confidence.md: "What has actually run" now markspromoteexecuted forv6.0.0andqualifyon RC18. Removed "neither that run nor the final tag exists as of this writing." Windows stays unqualified and unpublished.site/src/content/examples/polyglot.mdx: removed inventedspecsync check --explainas language detection (--explainis the score breakdown). Removed invented[[language_overrides]]. Documents actual detection:Cargo.toml/pyproject.toml/package.jsonplus file extensions. Replaced invented[ignore] pathswithexclude_dirs/exclude_patterns.site/src/content/examples/ci-gate.mdx: removed invented Action inputsscore_thresholdandannotations. Dual-pinsuses: CorvidLabs/spec-sync@v6.0.0withversion: '6.0.0'. PR comments usecomment: true. Score floor isspecsync score --min-score, not an Action input.specs/github/*: RC qualification is Ubuntu and macOS only. Windows is not a 6.0 target. Spec version 31; changelog row 2026-09-10.@v6.0.0still embeds6.0.0-rc.14.docs/6-0-confidence-report.md: dated banner so the pre-ship "promote never executed" remaining-steps list is not read as the current runbook.SDD change
correct-remaining-specsync-6-0-docs-after-the-stable-shipis draft with the interview complete (unapproved; human gate).Test Plan
specsync check --strict github --force(1 passed, 0 warnings)python3 -S .github/scripts/validate-release-version.pyspecsync change approve correct-remaining-specsync-6-0-docs-after-the-stable-ship --actor <name>