Broaden autonomous planning and harden Project drains - #36
Conversation
chrisbanes
changed the title
|
| Filename | Overview |
|---|---|
| skills/run-github-project/references/drain-scheduler.md | Adds durable CI-failure parking and recovery rules, but restart restoration can trust stale ticket-local recovery evidence. |
| skills/run-github-project/SKILL.md | Integrates parked claims, refresh gating, merge-policy validation, and canonical replanning into the main workflow. |
| skills/run-github-project/references/planning-lane.md | Defines a unified disposition-aware replan packet and separates autonomous replanning from human-required contract changes. |
| skills/run-github-project/references/project-config.md | Defines canonical live merge-policy fingerprint contents and global drift handling. |
| skills/run-github-project/references/normalized-ticket.md | Excludes unchanged parked implementation claims from ranking and slot accounting while preserving them as unresolved work. |
| skills/run-github-project/references/triage-lane.md | Prevents triage and successful drain completion while parked implementation work remains. |
| skills/to-plan/SKILL.md | Expands autonomous planning authority to repository-supported contract-realizing decisions while retaining stakeholder policy gates. |
| skills/to-plan/references/plan-templates.md | Requires plans to record non-obvious contract-realizing choices and their supporting repository evidence. |
Reviews (2): Last reviewed commit: "Require substantive parked-claim recover..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| record references its permalink and digest. On restart, keep an active matching | ||
| record parked; restore a claim with a valid later resume record without |
There was a problem hiding this comment.
When a resume marker is followed by a restart after the PR head or required-check state has changed back to the same non-converging failure, this path restores the parked claim without revalidating the marker's ticket-local recovery evidence against current live state, causing the claim to regain an implementation slot with a reset repair count.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b8e556db91
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Classify only a required-CI failure isolated to one ticket as parkable. Access, | ||
| authentication, authorization, configuration, review, base-repair, merge, | ||
| ambiguous-mutation, shared-infrastructure, and correlated failures are not | ||
| parkable. Preserve or stop them through their existing failure-isolation rule. |
There was a problem hiding this comment.
When a ticket reaches the parking threshold, this isolation gate should also compare the candidate failure fingerprint against already parked implementation claims. Parked claims are explicitly outside implementation slots, while the later correlation rule only mentions failures appearing in two slots or on the base; after ticket A is parked, ticket B with the same required-check fingerprint can still be treated as isolated and parked instead of stopping as correlated/shared-infrastructure. Include parked records in the isolation check before allowing this path.
Useful? React with 👍 / 👎.
1 participant
Summary
to-planresolve repository-supported contract-realizing decisions across public interfaces, schemas, persistence, seams, and testing strategyrun-github-projectaround one canonical disposition-aware replan packetWhy
The previous category-based planning gate rejected otherwise ready tickets whenever planning touched a public interface, schema, persisted representation, architectural seam, or testing contract. A human-authorized Planning transition should delegate those implementation decisions when repository evidence supports a design that preserves the accepted stakeholder contract.
The drain scheduler could also preserve a repeatedly failing ticket in an occupied slot and stop from a stale queue, even when unrelated Ready or Planning work existed. Terminal ticket-local required-CI failures now become durable parked claims outside implementation capacity, while configuration, policy, access, review, base-repair, ambiguous, correlated, and global failures retain their stricter stop behavior.
Validation
npm run lintpython3 -m unittest skills/run-github-project/scripts/test_rank_tickets.py(66 tests)python3 /Users/chris/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/to-planpython3 /Users/chris/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/run-github-projectreview-and-simplify-changesgate: no findingsponytail-review:Lean already. Ship.