ops(queue): enroll LineageWeave in queue-health evidence

[seonghobae]

Parent owner: #1150. Incident owner: #712.

Finding

LineageWeave independently reproduces the organization Actions pre-checkout admission class on current security-repair PR ContextualWisdomLab/LineageWeave#1079@c2923950e73c88a9f9fd932332ddd47682da124b, but canonical queue-health owner #1150 cannot observe it because the explicit bounded repository allowlist omits ContextualWisdomLab/LineageWeave.

The unchanged leaf head now supplies a stronger full-lifecycle transition specimen rather than a static queued snapshot. Tests 34815479029, SAST 34815434313, and Required Security 34815434486 all eventually acquired hosted capacity and completed GREEN without rerun/source churn. Required CodeQL language detection 103965453105 is GREEN; compatibility jobs 104064547137 (actions), 104064547154 (javascript-typescript), and 104064547176 (python) later acquired hosted runners and failed closed because authenticated current-head producer verdicts were absent. Coordinator 104180256379 subsequently acquired a hosted runner, validated the exact PR/head/base and receiver identities, and completed GREEN after dispatching the exact matrix to canonical producer run 34922377994, whose validate-dispatch job 104233131441 is currently queued. OpenCode admission and both coverage jobs are GREEN while opencode-review remains fail-closed on missing authenticated exact-head verdict. Strix is terminal failure after zero-finding SARIF plus CO concurrency_limit_exceeded; Noema is terminal cancelled after sidecar provisioning occupancy without a model verdict. The collector therefore must preserve per-job admission and terminal-semantic transitions rather than treating a run or repository as uniformly queued, running, failed, or successful.

No leaf rerun, no-op commit, selector change, cancellation, predecessor-status transfer or gate weakening was used or is authorized.

RED → minimal repair

Test-first commit 1a61773ad358318ab3d5740721e608b55ae1f6f3 extends #1150's exact-equality allowlist contract to require ContextualWisdomLab/LineageWeave while the config still omits it. On that exact commit the test expectation and config are intentionally inconsistent, so test_queue_health_allowlist_is_explicit_and_bounded is a deterministic contract RED.

Causal successor c4054eef3fc3cd84c87ea830b2e94d4145aa34e8 adds only the matching repository entry. Effective delta from parent #1150 is exactly two owner paths:

• config/actions_queue_health_repositories.json: enroll ContextualWisdomLab/LineageWeave;
• tests/test_actions_queue_health_contract.py: preserve the explicit/bounded exact-equality contract with LineageWeave included.

Collector logic, workflow triggers, runner selectors, check conclusions, repository branches, cancellation/rerun behavior and required gates are unchanged. Fresh compare against parent 42bb922f... is ahead 2 / behind 0 and contains only those two paths.

Focused exact-content validation of the current config, workflow contract and test file is GREEN: python -m pytest -q tests/test_actions_queue_health_contract.py → 2 passed. This is focused source-contract evidence only, not hosted acceptance.

Ownership / acceptance

Base is canonical queue-health owner #1150 exact 42bb922f03bf75aed1bc1931d9fbaf04a5433e20, already reconciled onto protected .github/main@91be6442906c7b6b4f600272c953699708394327. This child is Draft/mergeable at exact c4054eef3fc3cd84c87ea830b2e94d4145aa34e8.

Fresh exact-head hosted evidence has materially advanced:

• SAST Semgrep 34835105058: SUCCESS;
• Security 34835105055: changed-scope and gitleaks SUCCESS, Trivy 104031450201 SUCCESS, Scorecard 104031450187 SUCCESS; dependency-review/OSV are applicability-skipped rather than inherited;
• Required OpenCode opencode-review 104171888982: SUCCESS; coverage-source-tree 104171889020: SUCCESS; coverage-evidence 104171889062: SUCCESS;
• CodeQL language detection 103947030238: SUCCESS. Compatibility Python 104029049940 and Actions 104029049998 are terminal fail-closed pending producer verdict, not source-analysis failures;
• CodeQL coordinator 104160005694: SUCCESS after exact-head dispatch. Canonical producer run 34918644376 exists on protected .github/main; its validate-dispatch job 104221633013 remains queued.

There is still no submitted PR review on this exact head, so hosted check progress does not authorize parent integration yet. GREEN requires canonical CodeQL producer/verdict settlement, all then-required exact-head checks terminal, independent review, normal integration into #1150, and then the existing read-only collector producing a snapshot bound to current LineageWeave repository/PR/head/workflow/job identities. Enrollment alone does not resolve hosted capacity starvation.

No self-approval, administrator bypass, force update, destructive rebase, workflow-source copy, cancellation, blind rerun, no-op freshness commit, runner-selector churn, synthetic status, predecessor-evidence transfer or gate weakening is authorized.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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.}

[seonghobae]

Fresh concurrent-owner finding: sibling #2196 enrolls ContextualWisdomLab/disksage in the same two bounded #1150 paths. #2201@9a30272ce33566d9a9c781f868443aac7edafed5 is now the non-force two-parent integration descendant of this exact head (c4054eef...) and #2196@401a6ea6..., preserving both LineageWeave and DiskSage enrollment + exact-equality contract. Do not merge this sibling independently while #2201 is unsettled; its existing checks remain child evidence only and do not transfer to #2201.

[seonghobae]

Fresh LineageWeave successor canary for the already-enrolled repository, 2026-09-17: ContextualWisdomLab/LineageWeave#929@ac60da45aa12d8b85a2f4b45a63ce7df4e4cd539 is open / Ready-for-validation / mergeable on protected main@83eba56149eb802cd63642c507c324c9976ec78e. Its current Tests run 35201709281 has two materialized current-head jobs, Frontend 105137766737 and Full suite/PostgreSQL 105137766936; both remain queued with runner_id=0, empty runner/group identity and steps=[]. They were created at 2026-09-17T08:48:48Z and no leaf rerun/no-op commit/runner-selector mutation has been used.

This is a cleaner current specimen than the historical #1079 generation in the PR body because #929 is intentionally admitted to CI and its unresolved migration-ownership review thread requires hosted PostgreSQL/full-suite GREEN before resolution. The current leaf source has already undergone bounded RED→repair work for translation-ledger migration ownership and pg_temp relation-shadowing; queued jobs are incomplete infrastructure evidence, not a source GREEN or a new source RED. Preserve job-level identity and do not transfer predecessor receipts.

#2200's enrollment delta itself remains unchanged; this comment only refreshes the LineageWeave observation consumed by the canonical read-only queue-health owner. Parent #1150 is still Draft and its source head remains historical relative to today's protected .github/main, so this evidence does not authorize integration or source churn in either owner or leaf.

[seonghobae]

Fresh LineageWeave queue-health successor specimen after a causal product-head move: LineageWeave#929@c40170b274083623bfeadec8693ed8998036d600 is open/Ready-for-validation, not Draft. Tests run 35224149335 exists on that exact head; Full test suite job 105211339260 and Frontend lint, test, build job 105211339453 are both still queued, have no runner assignment, and steps=[]. The preceding RED/intermediate heads are intentionally not used as acceptance evidence.

This is a current exact-head admission specimen only. No leaf rerun, no-op/wake commit, runs-on change, synthetic status, or required-gate weakening is being used. Product/source repair remains in LineageWeave; queue/re-dispatch policy remains canonical here.