diff --git a/.agents/skills/test-audit/CAMPAIGN.md b/.agents/skills/test-audit/CAMPAIGN.md index d761f82ad6..045ed0ce0a 100644 --- a/.agents/skills/test-audit/CAMPAIGN.md +++ b/.agents/skills/test-audit/CAMPAIGN.md @@ -30,10 +30,11 @@ prior findings, model if specified, and discovery/edit/publication authority. Tell workers to preserve others' changes. One coordinator owns shared fixtures, routing, and integration. Do not edit a checkout with active test runs. -Keep one ledger: candidate, contract, retain/repair/consolidate/delete/defer, -reason, keeper, baseline, validation, and branch/PR status. Record reviewed areas -with no safe removals too. Discovery stays read-only until ownership is clear; -qualified edits need no additional user-approval round within existing authority. +Keep one ledger in the task: candidate, contract, +retain/repair/consolidate/delete/defer, reason, keeper, baseline, validation, and +branch/PR status. Record reviewed areas with no safe removals too. Discovery +stays read-only until ownership is clear; qualified edits need no additional +user-approval round within existing authority. ## 3. Plan removal of redundant layers @@ -42,11 +43,11 @@ boundary. Look for suites that replay the same behavior through wrappers, mocked collaborators, or provider-specific copies of a shared implementation. Individual cases can look reasonable while the entire layer is redundant. -Produce a compact layer plan: retired suites, retained owner per contract, -unique assertions to transfer, affected routing/commands, validation controls, -and any unused fixtures or production seams. Prefer a boundary that reaches -the responsible code; preserve distinct transport, lifecycle, and permission -risks. If no whole layer qualifies, record that and proceed with justified +Record a compact layer plan in the task: retired suites, retained owner per +contract, unique assertions to transfer, affected routing/commands, validation +controls, and any unused fixtures or production seams. Prefer a boundary that +reaches the responsible code; preserve distinct transport, lifecycle, and +permission risks. If no whole layer qualifies, record that and proceed with justified case-level changes. Large deletions are not a requirement. The coordinator reconciles keeper dependencies across all batches before diff --git a/.agents/skills/test-audit/SKILL.md b/.agents/skills/test-audit/SKILL.md index 3628897471..de1a30a1a2 100644 --- a/.agents/skills/test-audit/SKILL.md +++ b/.agents/skills/test-audit/SKILL.md @@ -67,10 +67,15 @@ Apply this gate to tests added or changed during gardening: ## Completion and reporting +Keep audit decisions, plans, ledgers, and validation evidence in the task and +PR description. Do not create or modify repository documentation, including +`doc/plans/` audit receipts or reports, unless the human explicitly requests +documentation changes. A test cleanup does not need a repository report. + Report removals and keepers, retained/deferred candidates, checks and limitations, distinct cases versus repeated executions, and test/support versus production -LOC. Count documentation separately. Label cost evidence as measured, estimated, -or historical; a proven simplification does not require a measurable speedup. +LOC. Label cost evidence as measured, estimated, or historical; a proven +simplification does not require a measurable speedup. State the actual endpoint: findings, validated local patch, published PR, intermediate merge, or landed in the intended target. Stop at the requested diff --git a/.agents/skills/test-audit/references/paperclip.md b/.agents/skills/test-audit/references/paperclip.md index 56d916fe26..6bbc482d52 100644 --- a/.agents/skills/test-audit/references/paperclip.md +++ b/.agents/skills/test-audit/references/paperclip.md @@ -53,10 +53,11 @@ Resource exhaustion must not be interpreted as a tested product failure or a passing control. Coordinate heavy runs and clean up only owned resources. Follow existing branch/worktree conventions and protect unrelated working-tree -edits. New repository audit plans/receipts belong in -`doc/plans/YYYY-MM-DD--test-audit.md`. Prefer one concise receipt per -coherent batch or campaign. For Paperclip issue work, follow the issue's artifact -and work-product requirements rather than relying only on local paths. +edits. Keep audit plans, decisions, and validation evidence in the Paperclip +execution issue and a concise PR description. Do not add repository audit +documents or `doc/plans/` receipts. Documentation changes require an explicit +human request. When requested artifacts are deliverables, follow the issue's +artifact and work-product requirements rather than relying only on local paths. When publishing is authorized, fill every section of `.github/PULL_REQUEST_TEMPLATE.md`, including exact model information that is diff --git a/.agents/skills/test-audit/references/validation.md b/.agents/skills/test-audit/references/validation.md index 8a86e6452e..9db1807db1 100644 --- a/.agents/skills/test-audit/references/validation.md +++ b/.agents/skills/test-audit/references/validation.md @@ -79,9 +79,11 @@ do not weaken assertions, increase budgets, skip suites, or erase a failing baseline to obtain a green audit. Retry a demonstrated transient problem within a stated bound; a recurring failure needs investigation. -Use PR notes for small changes. For a campaign, keep a compact dated receipt -with revisions, decisions, keepers, commands, results, controls, measurements, -and limitations. Link accessible CI runs/artifacts when they support claims. -Temporary paths and hashes alone do not make evidence durably inspectable. -Do not generate large evidence dossiers for trivial deletions or store raw -logs containing secrets. State precisely which broad checks remain unrun. +Use concise task and PR notes for revisions, decisions, keepers, commands, +results, controls, measurements, and limitations. Keep campaign ledgers and +plans in the task too; do not commit audit documentation or receipts to the +repository. Documentation changes require an explicit human request. Link +accessible CI runs/artifacts when they support claims. Temporary paths and +hashes alone do not make evidence durably inspectable. Do not generate large +evidence dossiers for trivial deletions or store raw logs containing secrets. +State precisely which broad checks remain unrun.