chore(openspec): rebind runtime-command-authority row to the landed #506 squash

[monkey1sai]

Summary

• chore(openspec): rebind the isolated-branch-stack row to the landed #481 squash #482／fix(openspec): rebind hifi lifecycle to landed snapshot #501／chore(openspec): rebind align-ship-cycle row to the landed #504 squash #512 同型 rebind：implement-runtime-command-authority-and-rejection ledger row 的 subject_commit 指向 fix(viewer): stage-load-timeout state-specific test anchor + honest 5.6 ledger reconcile #506 squash 前的分支 commit（1229171，squash 後非 main ancestor 且分支已刪除），會讓所有 openspec PR 的 machine-truth source observation 以 subject_unavailable／subject_not_ancestor 失敗（實例：PR test(streaming): real-subprocess CAD hardener success-path coverage (#492) #503 run 31561485748 之後的 agent-governance fail）。rebound 至 landed squash cba6265。
• 單檔單行；本機 machine-truth 24/0、metrics 13/0。

AI Coding Governance

Machine values: Change lane = F / B / G / S; Behavior contract changed = yes / no; Requirement source = issue / docs/plans / superpowers spec / existing contract / not applicable.

Item	Result
Change lane	F
Behavior contract changed	no
Linked issue	none（#506 merge 的後續 rebind）
Requirement source	existing contract（openspec lifecycle machine-truth 的 subject ancestry 規則；#482/#501/#512 先例）
CODEOWNERS / owner review	requested
GitNexus evidence	not needed
Browser E2E evidence	not user-facing
Agent workflow changed?	no
Required checks expected	CI / Agent Governance / PR Metadata Contract

Frontend Verification

User-facing changes must pass two independent producers: real frontend/runtime operability evidence and the pinned docs/plans/design-system-reference.manifest.json fidelity gate. Scope is derived from changed paths plus the base/head manifest union; the PR body cannot select an easier screen. mixed and partial_reference_missing permit honest partial work but require Full completion claimed = no. Semantic evidence is produced only by the design-semantic-visual CI Playwright job, never supplied as PR input; PR Metadata Contract validates the live PR metadata, while normal protected CI checks determine mergeability.

Item	Result
Frontend route	not applicable
Main button(s) tested	not applicable
Fixture used	not applicable
Backend API called	not applicable
Runtime action	not applicable
Visible success state	not applicable
E2E command	not applicable
Screenshot / trace	not applicable
Design gate status	not applicable
Design screen(s)	not applicable
Reference-missing route(s) / surface(s)	not applicable
Full completion claimed	no
Design reference manifest	docs/plans/design-system-reference.manifest.json
Visual fidelity result	not applicable
Visual comparison	not applicable
Visual artifacts	not applicable
Manual test steps	not applicable
Known gaps	not applicable

Deploy Path Verification

Required for runtime / Docker / Kit / viewer / ports / env / conversion-service changes.

Item	Result
Affects runtime / docker / Kit / viewer / ports / env?	no
Canonical deploy path updated?	not needed
New root script added?	no
Deploy dry-run command	not applicable
Full deploy tested	not available
Verify command	not applicable
Frontend URL verified	not applicable
Evidence path	openspec/lifecycle-ledger.json（單行 diff）

Self-Referential Bootstrap

Required when the PR changes the verification mechanism itself (deploy path / evidence harness / gate script). Rule: docs/agents/self-referential-bootstrap.md. Open ledger debt in scripts/self-referential-bootstrap-ledger.json blocks further mechanism PRs until fixpoint closure.

Item	Result
Self-referential bootstrap	no
Bootstrap ledger entry	not applicable
Bootstrap reason	not applicable

Validation

• node --test scripts/tests/test-openspec-machine-truth.mjs → 24 pass／0 fail。
• node --test scripts/tests/test-ai-coding-metrics.mjs → 13 pass／0 fail。
• git diff --check → clean。

Known Risks

• 無 runtime 影響（ledger 單行 rebind）。

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@monkey1sai, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 556e5cb0-2f2d-44e8-af5d-9f9af2a7953f

📥 Commits

Reviewing files that changed from the base of the PR and between cba6265 and 744a0a2.

📒 Files selected for processing (1)

• openspec/lifecycle-ledger.json

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR rebinds the subject_commit for the implement-runtime-command-authority-and-rejection lifecycle row in openspec/lifecycle-ledger.json from the pre-squash branch commit (1229171…, discarded by the #506 squash merge and no longer a main ancestor) to the landed squash commit (cba6265…). This restores the OpenSpec machine-truth source observation so that PR CI (agent-governance) no longer fails with subject_not_ancestor / subject_unavailable. It follows the identical remediation pattern established in #482, #501, and #512.

Changes:

• Repoint one ledger row's subject_commit to the permanently reachable landed #506 squash SHA.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[monkey1sai-blip]

Approved by monkey1sai-blip (the reviewer account pinned by the repo's merge governance).

Submitted through scripts/blip_review.py — a scripted approval carrying the operator's authority, pinned to head 744a0a28cba94fbe6d56cd5064305daa83d5c79a. This is the mechanism the GitHub App cannot satisfy: an App's approving review does not count toward required_approving_review_count.