Repository navigation
Open
Description
Boundary
This work touches the following concrete paths:
.github/workflows/project-automation.ymlspecs/claw/gates.t27specs/claw/gates_pins.t27gen/c/claw/gates.ctools/policy/foreign-exceptions.txtdocs/coordination/github-automation-inventory.mddocs/coordination/project-backfill-plan.mddocs/coordination/project-setup-runbook.md
Parent context: Trinity-S-AI-DNA/t27 epic #9271 (TRI CLAW gate inventory neighborhood). This is operational project-management tooling around the existing gate topology, not a compiler change: no parser, backend or spec-language behavior is touched.
Order: T27_GITHUB_AUTOMATION_V1 (owner, 2026-11-10).
User Scenarios
- Given a new issue is labeled
area/compiler+P1, when one run ofproject-automation.ymlcompletes, then the issue appears on the T27 Delivery board with Status=Triage, Area=Compiler, Priority=P1, set automatically with no human card move. - Given a pull request is merged, when the automation processes the close event, then its board item's Status becomes Done and the issue body, title, state, assignee and labels are untouched.
- Given the owner opens the Triage inbox saved view, when the view loads, then it shows only newly-arrived items (no stale Done or In-progress noise).
Requirements
- FR-001: There MUST be exactly one Projects v2 board named "T27 Delivery" with custom fields Status, Priority, Area only -- no duplicate fields.
- FR-002: The board MUST have exactly 8 saved views covering triage inbox, per-area, per-priority and done/delivery views.
- FR-003: The auto-add workflow MUST be UI-enabled and non-retroactive: only items added after enablement flow through it.
- FR-004: There MUST be one Actions workflow
project-automation.yml, reporting class, using a least-privilegeGH_PROJECT_TOKEN(project write only). - FR-005: The automation MUST never modify issue body, title, state, assignee or labels; it MUST only set project item field values.
- FR-006: Discussions triage MUST happen via labels on linked issues; the automation MUST NOT auto-convert discussions into issues.
- FR-007: Backfill of existing issues MUST run in batches of 25 and MUST wait for explicit owner approval, per
docs/coordination/project-backfill-plan.md. - FR-008: The foreign-language budget MUST be paid by dead-file deletion: 112 deleted lines vs 38 added, satisfying
check_budget(). - FR-009: The
specs/claw/gates.t27inventory row MUST land in the same commit as the workflow file (gate-drift law).
Success Criteria
gh project view <n> --format jsonshows exactly the 3 custom fields Status, Priority, Area.- All 8 saved views exist on the board.
- A test issue labeled
area/compilerreceives Area=Compiler within one workflow run. - own-language / foreign-budget / seal CI checks pass green on the landing PR (exit 0).
- No unintended issue mutations: labels, state, title, body and assignee of member issues are untouched by the automation, verified on the test issue.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Nov 10, 2026
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
FR-001: ... MUST ...gHashTag commentedon Nov 17, 2026
Spec created: specs/automation/github_projects_v2.t27 (typecheck OK, 2 tests pass). Covers #13582 too.
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M6 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.