|
| 1 | +# LineageWeave hourly review-repair caller |
| 2 | + |
| 3 | +## Decision |
| 4 | + |
| 5 | +The organization control plane invokes its existing review-repair scheduler for |
| 6 | +`ContextualWisdomLab/LineageWeave` at minute 4 of every hour. The caller scans |
| 7 | +all pull-request bases because LineageWeave uses stacked pull requests, but it |
| 8 | +dispatches at most one repair and waits two hours before retrying an unchanged |
| 9 | +head. A new heartbeat never cancels an in-flight diagnosis. |
| 10 | + |
| 11 | +The caller is deliberately thin. It does not approve, merge, release, or change |
| 12 | +a review-agent identity. It does not create product work. The reusable |
| 13 | +scheduler refetches the current head, reviews, threads, checks, and writer lease |
| 14 | +before dispatching the existing OpenCode repair worker. Independent current-head approval |
| 15 | +and all protected checks remain mandatory. |
| 16 | + |
| 17 | +## Credential and model boundary |
| 18 | + |
| 19 | +The workflow token is read-only. The caller maps only the established |
| 20 | +`PR_REVIEW_MERGE_TOKEN` and `OPENCODE_APPROVE_TOKEN` inputs and permits the |
| 21 | +reusable scheduler's existing OIDC fallback; it never inherits all secrets. |
| 22 | +It does not receive a model credential or provider endpoint and does not use |
| 23 | +`COPILOT_GITHUB_TOKEN`. |
| 24 | + |
| 25 | +Model execution remains inside the reviewed central worker and crosses its |
| 26 | +`contextual-orchestrator` boundary. This caller neither selects a provider nor |
| 27 | +changes contextual-orchestrator discovery, routing, or review-agent secrets. |
| 28 | + |
| 29 | +## Product-gap continuation boundary |
| 30 | + |
| 31 | +This caller closes the missing hourly stacked-PR repair path only. Product-gap |
| 32 | +development after the PR queue empties remains owned by the organization |
| 33 | +commercial-readiness coordinator and an explicitly opted-in, bounded |
| 34 | +repository development entrypoint. LineageWeave does not currently publish |
| 35 | +that entrypoint, and recent coordinator runs failed before inventory because |
| 36 | +their maintainer credential was unavailable. Therefore this workflow is not |
| 37 | +evidence that autonomous product-gap development is operational. |
| 38 | + |
| 39 | +## Verification and rollback |
| 40 | + |
| 41 | +Contract tests bind the cadence, stack scope, dispatch budget, retry floor, |
| 42 | +permissions, explicit secret mapping, absent model credentials, reusable |
| 43 | +scheduler path, and focused quality-workflow coverage. A scheduled run proves |
| 44 | +only accepted dispatch after live state validation; it does not prove a repair, |
| 45 | +approval, merge, release, or product increment. |
| 46 | + |
| 47 | +Rollback is removal of this caller after confirming another enabled workflow |
| 48 | +owns the same LineageWeave writer lease. Do not run duplicate scheduled writers. |
| 49 | + |
| 50 | +## APA 7th references |
| 51 | + |
| 52 | +GitHub. (n.d.). *Control the concurrency of workflows and jobs*. Retrieved |
| 53 | +August 28, 2026, from |
| 54 | +https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency |
| 55 | + |
| 56 | +GitHub. (n.d.). *Events that trigger workflows: Schedule*. Retrieved August |
| 57 | +28, 2026, from |
| 58 | +https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule |
| 59 | + |
| 60 | +GitHub. (n.d.). *Reuse workflows*. Retrieved August 28, 2026, from |
| 61 | +https://docs.github.com/en/actions/how-tos/sharing-automations/reusing-workflows |
| 62 | + |
| 63 | +National Institute of Standards and Technology. (2022). *Secure software |
| 64 | +development framework (SSDF) version 1.1: Recommendations for mitigating the |
| 65 | +risk of software vulnerabilities* (NIST Special Publication 800-218). |
| 66 | +https://doi.org/10.6028/NIST.SP.800-218 |
0 commit comments