Repository navigation
fix(governance): register active proposal directories - #290
Conversation
Agent-Identity: Manus Task-Ref: REG-01 Signed-off-by: Manus <manus@manus.im>
github-project-automation
Bot
moved this to Todo
in @timerloggedout-spec's untitled project team planning
|
Mention Blocks like a regular teammate with your question or request: @blocks review this pull request Run |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Proposal process checklist
Refs: PROCESS · CONSENSUS · registry.yaml |
|
context_key: pr-290-fixproposal-registry-orphans Feedback excerptInstructions
|
|
cycle_id: pr-290-f144be300253 Agent peer response gateProvider state:
Pending: Authorized interactive controls:
A provider-owned checkbox/button requires an authorized Operator Action Executor. The second-pass reviewer remains blocked until matching provider completion evidence is ingested for this SHA. |
|
@coderabbitai full review cycle_id: pr-290-f144be300253 Autonomous OPERATOR-token request for a current-SHA provider review. A command request is not review completion; await provider evidence. |
|
|
|
|
PR Summary by QodoRegister orphan active proposals in the governance registry
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
|
context_key: pr-290-fixproposal-registry-orphans Feedback excerptHigh-Level Assessment
|
Code Review by Qodo
1. Registry summary truncates entries
|
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
| - id: actions-refinements | ||
| title: "Issue #192 action-integration refinements" | ||
| author: Manus AI | ||
| posted_at: 2026-08-19 |
There was a problem hiding this comment.
1. Registry summary truncates entries 🐞 Bug ◔ Observability
The proposal-lifecycle workflow only prints the first 120 lines of docs/proposals/registry.yaml, and the newly-registered proposals start after that cutoff, so they will not appear in the CI job summary. This makes reviewers/operators miss the newly-added registrations in the workflow output even when validation passes.
Agent Prompt
### Issue description
The `proposal-lifecycle` workflow summarizes only the first 120 lines of `docs/proposals/registry.yaml`, which now excludes newly-added proposal entries (they start after line 120). This reduces observability during PR review and triage.
### Issue Context
The workflow currently uses `sed -n '1,120p'` to build the step summary.
### Fix Focus Areas
- .github/workflows/proposal-lifecycle.yml[30-35]
- docs/proposals/registry.yaml[133-186]
### Suggested change
Replace the `sed -n '1,120p'` line with one of:
- `cat docs/proposals/registry.yaml >> "$GITHUB_STEP_SUMMARY"`
- or increase the range (e.g., `sed -n '1,260p' ...`) if you want a hard cap.
Keep the existing fenced code block markers.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
|
context_key: pr-290-fixproposal-registry-orphans Feedback excerptInstructions
|
Agent-Identity: Manus Task-Ref: #289 Signed-off-by: Manus <manus@manus.im>
github-project-automation
Bot
moved this from Todo
to Done
in @timerloggedout-spec's untitled project team planning
|
head_sha: cc448b4 Peer review gate (ready for second-pass agents)External reviewers polled: CodeRabbit, Devin, Aikido, Sentry, Copilot. Peer activity (truncated): Downstream: |
This branch was successfully deployed
2 participants
Summary\n\nRegisters the three existing active proposal directories that registry validation identified as orphans:\n\n-
actions-refinements\n-icm-architect-integration\n-kimi-cloud-offload\n\nEach entry copies the existing manifest metadata intodocs/proposals/registry.yaml. No proposal content, state, ownership, review record, or governance rule changes.\n\nFixes #289\n\n## Validation\n\n-python3 scripts/proposals/validate_registry.py— passed: 11 proposals consistent with disk.\n- Active-directory reconciliation — passed: no orphan directories remain.\n-git diff --cached --check— passed.\n-python3 scripts/ci/termux_smoke.py— passed.\n\nrepo_gate.pyremains blocked on this branch by the separate, unmerged baseline syntax repair in PR #288 (archwiz/linear_sync.py:237). PR #288 itself passes the repository gate after staging its one-file repair; this PR does not modify that source file.\n\n## Scope boundary\n\nThis is a registry-only governance metadata change. It is intentionally not eligible forautonomous-merge, because proposal/governance paths are excluded by the safety policy.\n\nRelated: #274, #287, #288, and #286.\n\n