project-rules-update

Project Rules Update

Refresh canonical rules only from source-only evidence: source, effective configuration, tests, and observed commands—not Git, PR, release, owner, deadline, or collaboration policy.

Required resources

Read ../../references/project-context.md, ../../references/candidate-ranking.md, ../../references/language-analyzer.md, ../../references/pattern-card.md, ../../references/coverage-contracts.md, ../../references/conflict-and-lifecycle.md, ../../references/code-chain-discovery.md, ../../references/rule-classification.md, ../../references/rule-content-contract.md, ../../references/confirmation-policy.md, ../../references/adapter-content-contract.md, and ../../references/adapters.json. Derive one to three task_terms from the current user source task and target scope (for example API, module, or feature names), and pass each as a repeated --task-term <term>. Save scan JSON in a system temporary file explicitly outside <project-root> so AI can read it during synthesis; use try/finally and Remove-Item after validation. In PowerShell: $scanResult = Join-Path ([IO.Path]::GetTempPath()) ('project-rules-scan-' + [guid]::NewGuid() + '.json'); try { python ../../scripts/scan_project.py <project-root> --task-term <term-1> --task-term <term-2> > $scanResult; Get-Content -Raw $scanResult; ... } finally { Remove-Item -LiteralPath $scanResult -Force -ErrorAction SilentlyContinue }. Use ../../scripts/inspect_symbol.py for material Python ownership. If no valid manifest v2 exists, stop and use project-rules-init.

Update workflow

1. Validate manifest v2, then compute a bounded delta. Expand affected scope through consumers, shared code, configuration, and focused tests.
2. Refresh the source-only context payload and ranked candidates. Tools report facts/candidates/conflicts/static checks; AI synthesizes; humans decide substantive conflicts, strong constraints, and future direction.
3. Revalidate each affected pattern card. Retain unchanged update-plan actions for confirmed cards with their content and exact hash. A missing primary anchor makes a card stale; do not rewrite it from a new file or automatically adopt a new standard.
4. Apply the conflict lifecycle modes: interactive asks, non-interactive omits unresolved claims, strict-ci fails an unresolved critical public API preview. Record lightweight coverage statuses only.
5. Show added, modified, stale, retired, conflict, unchanged, and exact owned write/delete plan. Replacement or deletion requires prior manifest ownership and exact current SHA-256.
6. Review before write: request one explicit write confirmation, atomically apply the approved plan with manifest v2 last, then within that try run python ../../scripts/validate_outputs.py <project-root> --scan-result $scanResult; the finally cleanup runs after validation.