chore(roadmap): prepare issue 127 for Copilot pilot - #128
Merged
Conversation
… v1+v2 Master plan (v2 supersedes v1) detailing Stage 0A-6 for a human-controlled Copilot issue implementation pipeline: current-state findings, sources of truth, architecture, staged phases, smallest-safe manual pilot, security/permissions matrix, recovery, and completion contract. Includes plan execution frontmatter (execution-report, completed-phases, current-phase).
Phase 1 (Stage 0A) deliverable: resolves Project node/Status field/option IDs, built-in workflow semantics, GITHUB_TOKEN default-permission audit, Copilot assign-API contract, roadmap drift vs origin/main, and a >=3 pilot candidate ranking including issue #63 (open). No live GitHub mutations performed.
…doff Adds /cg-work execution report per goal-execution contract and updates active-state handoff (evidence status, unresolved Stage 0B approval decision, nextCommand /cg-work phase2). Phase 1 evidence gate passed via executed checks.
Add the approved-but-not-started pilot feature to milestone workflow-maturity at status planned with plan null. - Attach canonical persistent github linkage to issue #127 (repo, issueNumber, issueUrl, createdAt) - Preserve the marker-vs-canonical distinction (compound-gpid-tracked marker is recovery-only) - Milestone status remains derived in-progress; no other roadmap items or historical drift touched
Add the concise Stage 0B evidence note and append the Run 2 (Stage 0B) section to the master-plan execution report. - Evidence note: approved roadmap feature + issue #127 readiness edits, read-only verification, and the confirmed implementation closure for Stage 1 - Execution report Run 2: Steps 1-5 record, deviations (none), Phase 2 NOT completed (handoff to human)
|
Warning Review limit reached
Next review available in: 15 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds v1 and v2 pipeline plans, renders both plans as HTML, records Stage 0A and Stage 0B evidence, links Issue ChangesCopilot issue implementation pipeline
Estimated code review effort: 3 (Moderate) | ~30 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.cg-docs/active-state/current.json:
- Around line 21-22: Add a blocking guard before executing nextCommand in the
phase3 workflow, checking unresolvedDecisions for any entry with blocking set to
true and halting /cg-work phase3 while one remains unresolved. Treat
ready-3-of-4 only as checklist progress, and preserve issue `#127` as Backlog
until Project Status is Ready and explicit approval is received.
In @.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md:
- Line 156: Align item 3 with the other top-level ordered-list items in
.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md:156-156
and .cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline.md:149-149
by removing the extra indentation. Regenerate the corresponding views at
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html:151-158
and
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html:147-154,
and confirm both sections render as semantic ordered lists.
- Around line 14-15: Restore a single authoritative v2 handoff: in
.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md:14-15 keep
phase metadata aligned with completed evidence, and at 821-823 make the next
action the Phase 2 approval gate (or consistently set metadata to Stage 0A if
that is truly current). Regenerate the v2 view at
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html:484-485.
Archive v1 by marking it superseded at
.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline.md:4, replacing
its executable handoff with a v2 reference at 812-814, marking its rendered view
historical rather than canonical at
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html:102,
and regenerating that view’s handoff at 480-481.
- Around line 72-75: Repair the mojibake in
.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md at lines
72-75 and .cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline.md at
lines 65-68 by replacing corrupted sequences with intended characters or stable
ASCII text. Regenerate the corresponding HTML views at
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html:134
and
.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html:130,
then verify no corrupted sequences remain in either source or generated view.
In @.cg-docs/work-reports/2026-08-06-stage-0a-verification.md:
- Line 154: Escape or rewrite the literal pipe in the “Auto-add to project”
table cell so Markdown treats “is: issue|pr” as cell content rather than a
column separator, while preserving the documented filter expression.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 43b1aa86-0c78-4148-9ea5-46b07d88b8f3
📒 Files selected for processing (9)
.cg-docs/active-state/current.json.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline.md.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html.cg-docs/work-reports/2026-08-06-copilot-issue-implementation-pipeline-v2.md.cg-docs/work-reports/2026-08-06-stage-0a-verification.md.cg-docs/work-reports/2026-08-06-stage-0b-evidence.mdroadmap.json
Represent the active state as blocked while the Stage 0B readiness gates remain. - status: blocked; preserve blocking unresolved decision D2 - nextCommand: null (Stage 1 not yet authorized); currentPhase stays 2 - preserve issue #127 as Backlog and ready-3-of-4
Address CodeRabbit findings B-E in the controlled-pipeline plan artifacts. - Repair UTF-8 mojibake in both plan Markdown sources and regenerate views (arrows, dashes, quotes, box drawing) - Fix ordered-list indentation so section 1.7 renders as a semantic <ol> - Make v2 the sole authoritative plan: correct the v2 Next-action gate to the Stage 0B approval gate - Archive v1 with a visible superseded banner and a v2 handoff pointer (status remains a valid schema value) - Escape the literal pipe in the is: issue|pr table cell of the Stage 0A report
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md:
- Around line 562-563: Update the branch-and-PR guidance in the pipeline plan so
merge-completing PRs require a closing keyword: Closes `#N`, Fixes `#N`, or Resolves
`#N`. Reserve Refs `#N` for draft, partial, or uncertain work, and clarify that a
Refs-only PR does not close the issue or trigger the issue’s Status→Done update.
In
@.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html:
- Line 139: Update the ruleset text in the source plan so the complete
identifiers non_fast_forward, actor_id, and current_user_can_bypass each use
Markdown code spans, preventing underscore emphasis rendering. Then regenerate
the corresponding HTML view and verify these identifiers remain intact as code
literals.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e66016bf-ad01-4776-a264-59f10c0e17da
📒 Files selected for processing (6)
.cg-docs/active-state/current.json.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline.md.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.html.cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html.cg-docs/work-reports/2026-08-06-stage-0a-verification.md
🚧 Files skipped from review as they are similar to previous changes (2)
- .cg-docs/work-reports/2026-08-06-stage-0a-verification.md
- .cg-docs/views/plans/2026-08-05-copilot-issue-implementation-pipeline.html
Address the two follow-up CodeRabbit threads on the v2 plan. - Section 5.6 steps 5/5b: a merge-completing pilot PR must carry Closes/Fixes/Resolves #N so the issue auto-closes; Refs #N is reserved for draft/partial/uncertain work and a Refs-only merge does not close the issue or drive issue Status to Done (the Pull request merged workflow updates the PR item only) - Section 1.3 ruleset table: wrap non_fast_forward and actor_id in code spans so the identifiers render as literals (current_user_can_bypass already literal) - Regenerated and verified the v2 HTML view (validated and current)
This was referenced Aug 7, 2026
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.
What this PR does
Completes Stage 0B — pre-pilot preparation of the controlled GitHub Copilot issue-implementation pipeline (plan:
.cg-docs/plans/2026-08-05-copilot-issue-implementation-pipeline-v2.md). It prepares pilot issue #127 to become the one manual Copilot pilot. Issue #127 is NOT implemented by this PR, and no source behavior changes — automatic HTML publication is not modified here.Roadmap feature + canonical linkage
Adds feature
artifact-html-opt-in-default("Make automatic artifact HTML publication opt-in by default") to milestoneworkflow-maturityat strategic statusplanned(approved-but-not-started,plan: null), with canonical persistent GitHub linkage:issueNumber: 127issueUrl: Make automatic artifact HTML publication opt-in by default #127repo: GPID-WB/compound-gpidcreatedAt: 2026-08-06The
compound-gpid-trackedmarker stays recovery/duplicate-detection-only;features[].githubis the canonical linkage.Refs #127
Issue #127 readiness updates
Minimal approved body edits only: filled the
## Roadmap linkageplaceholders (milestoneworkflow-maturity; canonical linkage added) and checked 3 of 4Ready for Copilotboxes (execution contract approved; roadmap feature created and linked; exact allowed-path closure confirmed). The Project-StatusBacklog→Readybox remains unchecked.Review clean-up (CodeRabbit)
Resolved the five review threads: active-state moved to a blocking handoff (
status: blocked,nextCommand: null); v1 plan explicitly archived/superseded (visible banner + v2 pointer); mojibake repaired in both plan sources and regenerated views; ordered-list indentation fixed (semantic<ol>); and theis: issue|prtable pipe escaped. Both plan HTML views were regenerated from canonical Markdown and verified current.Validation performed
. tests\Run-Tests.ps1 -File roadmap→ passed, 0 failures.Backlog, unassigned, and has no linked implementation PR.cg-render-artifact --validate-onlyand--checkon both plans → passed; views current;git diff --checkclean; mojibake scan over plan sources and views clean.Do not assign Copilot
Copilot must not be assigned to issue #127 until this PR is merged into
mainand the issue is manually moved fromBacklogtoReady.Summary by CodeRabbit
Documentation
Planning