@llipe.com/dev-tasks 0.11.0 → 0.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/agents/developer.md +105 -43
- package/.claude/agents/github-ops.md +48 -4
- package/.claude/agents/housekeeping.md +44 -7
- package/.claude/agents/qa-engineer.md +24 -11
- package/.claude/agents/researcher.md +26 -6
- package/.claude/agents/technical-writer.md +61 -6
- package/.claude/agents/ux-engineer.md +1 -0
- package/.claude/agents/verifier.md +48 -6
- package/.claude/commands/developer.md +2 -266
- package/.claude/commands/infra-engineer.md +92 -0
- package/.claude/commands/planner.md +44 -23
- package/.claude/commands/product-engineer.md +21 -9
- package/.claude/commands/researcher.md +4 -5
- package/.claude/commands/technical-writer.md +1 -1
- package/.claude/hooks/branch-guard.sh +30 -0
- package/.claude/hooks/git-guard.sh +483 -22
- package/.claude/skills/activity-codebase-research/SKILL.md +4 -11
- package/.claude/skills/activity-generate-spec/SKILL.md +34 -10
- package/.claude/skills/activity-grill/SKILL.md +150 -0
- package/.claude/skills/activity-init/SKILL.md +121 -71
- package/.claude/skills/activity-refine/SKILL.md +75 -15
- package/.claude/skills/activity-test-standards/SKILL.md +25 -0
- package/.claude/skills/aws-ops/SKILL.md +155 -0
- package/.claude/skills/deploy-ops/SKILL.md +121 -0
- package/.claude/skills/fly-ops/SKILL.md +138 -0
- package/.claude/skills/git-ops/SKILL.md +27 -7
- package/.claude/skills/implement/SKILL.md +49 -4
- package/.claude/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.claude/skills/memo-cli-usage/SKILL.md +66 -13
- package/.claude/skills/plan/SKILL.md +43 -1
- package/.claude/skills/supabase-ops/SKILL.md +109 -0
- package/.github/agents/developer.agent.md +70 -19
- package/.github/agents/github-ops.agent.md +46 -4
- package/.github/agents/housekeeping.agent.md +43 -7
- package/.github/agents/infra-engineer.agent.md +139 -0
- package/.github/agents/planner.agent.md +25 -4
- package/.github/agents/product-engineer.agent.md +21 -9
- package/.github/agents/qa-engineer.agent.md +23 -11
- package/.github/agents/researcher.agent.md +25 -6
- package/.github/agents/technical-writer.agent.md +60 -6
- package/.github/agents/verifier.agent.md +46 -5
- package/.github/instructions/implement.instructions.md +49 -4
- package/.github/instructions/plan.instructions.md +43 -1
- package/.github/prompts/infra-engineer.prompt.md +12 -0
- package/.github/prompts/product-engineer-init.prompt.md +5 -6
- package/.github/prompts/researcher.prompt.md +4 -5
- package/.github/prompts/technical-writer.prompt.md +1 -1
- package/.github/skills/activity-codebase-research/SKILL.md +4 -16
- package/.github/skills/activity-generate-spec/SKILL.md +34 -10
- package/.github/skills/activity-grill/SKILL.md +145 -0
- package/.github/skills/activity-init/SKILL.md +120 -70
- package/.github/skills/activity-refine/SKILL.md +75 -15
- package/.github/skills/activity-test-standards/SKILL.md +25 -0
- package/.github/skills/aws-ops/SKILL.md +150 -0
- package/.github/skills/deploy-ops/SKILL.md +116 -0
- package/.github/skills/fly-ops/SKILL.md +133 -0
- package/.github/skills/git-ops/SKILL.md +27 -7
- package/.github/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.github/skills/memo-cli-usage/SKILL.md +66 -13
- package/.github/skills/supabase-ops/SKILL.md +104 -0
- package/.kiro/agents/developer.md +71 -20
- package/.kiro/agents/github-ops.md +46 -4
- package/.kiro/agents/housekeeping.md +44 -8
- package/.kiro/agents/infra-engineer.md +102 -0
- package/.kiro/agents/planner.md +33 -15
- package/.kiro/agents/product-engineer.md +24 -12
- package/.kiro/agents/qa-engineer.md +24 -12
- package/.kiro/agents/researcher.md +26 -7
- package/.kiro/agents/technical-writer.md +63 -9
- package/.kiro/agents/verifier.md +47 -6
- package/.kiro/skills/activity-codebase-research/SKILL.md +4 -11
- package/.kiro/skills/activity-generate-spec/SKILL.md +34 -10
- package/.kiro/skills/activity-grill/SKILL.md +150 -0
- package/.kiro/skills/activity-init/SKILL.md +121 -71
- package/.kiro/skills/activity-refine/SKILL.md +75 -15
- package/.kiro/skills/activity-test-standards/SKILL.md +25 -0
- package/.kiro/skills/aws-ops/SKILL.md +155 -0
- package/.kiro/skills/deploy-ops/SKILL.md +121 -0
- package/.kiro/skills/fly-ops/SKILL.md +138 -0
- package/.kiro/skills/git-ops/SKILL.md +27 -7
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.kiro/skills/memo-cli-usage/SKILL.md +66 -13
- package/.kiro/skills/supabase-ops/SKILL.md +109 -0
- package/.kiro/steering/implement.md +49 -4
- package/.kiro/steering/plan.md +43 -1
- package/AGENTS.md +60 -109
- package/AGENTS.md.template +124 -0
- package/CHANGELOG.md +163 -0
- package/CLAUDE.md +23 -18
- package/CLAUDE.md.template +103 -0
- package/README.md +168 -146
- package/TESTING.md +84 -148
- package/bundle-manifest.json +43 -2
- package/dist/bin/dev-tasks.js +65 -3
- package/dist/bin/dev-tasks.js.map +1 -1
- package/dist/{adapters/cli → bin}/parse-args.d.ts +2 -6
- package/dist/bin/parse-args.d.ts.map +1 -0
- package/dist/{adapters/cli → bin}/parse-args.js +2 -18
- package/dist/bin/parse-args.js.map +1 -0
- package/dist/core/checks/decision-log-format.d.ts +44 -0
- package/dist/core/checks/decision-log-format.d.ts.map +1 -0
- package/dist/core/checks/decision-log-format.js +171 -0
- package/dist/core/checks/decision-log-format.js.map +1 -0
- package/dist/core/checks/docs-structure.d.ts +82 -0
- package/dist/core/checks/docs-structure.d.ts.map +1 -0
- package/dist/core/checks/docs-structure.js +285 -0
- package/dist/core/checks/docs-structure.js.map +1 -0
- package/dist/core/checks/glossary.d.ts +178 -0
- package/dist/core/checks/glossary.d.ts.map +1 -0
- package/dist/core/checks/glossary.js +651 -0
- package/dist/core/checks/glossary.js.map +1 -0
- package/dist/core/checks/index.d.ts +19 -0
- package/dist/core/checks/index.d.ts.map +1 -0
- package/dist/core/checks/index.js +16 -0
- package/dist/core/checks/index.js.map +1 -0
- package/dist/core/checks/run.d.ts +22 -0
- package/dist/core/checks/run.d.ts.map +1 -0
- package/dist/core/checks/run.js +51 -0
- package/dist/core/checks/run.js.map +1 -0
- package/dist/core/distribution/doctor.d.ts +46 -1
- package/dist/core/distribution/doctor.d.ts.map +1 -1
- package/dist/core/distribution/doctor.js +161 -2
- package/dist/core/distribution/doctor.js.map +1 -1
- package/dist/core/distribution/index.d.ts +9 -3
- package/dist/core/distribution/index.d.ts.map +1 -1
- package/dist/core/distribution/index.js +5 -2
- package/dist/core/distribution/index.js.map +1 -1
- package/dist/core/distribution/install-if-absent.d.ts +46 -0
- package/dist/core/distribution/install-if-absent.d.ts.map +1 -0
- package/dist/core/distribution/install-if-absent.js +81 -0
- package/dist/core/distribution/install-if-absent.js.map +1 -0
- package/dist/core/distribution/install.d.ts.map +1 -1
- package/dist/core/distribution/install.js +5 -0
- package/dist/core/distribution/install.js.map +1 -1
- package/dist/core/distribution/migrate-docs.d.ts +64 -0
- package/dist/core/distribution/migrate-docs.d.ts.map +1 -0
- package/dist/core/distribution/migrate-docs.js +139 -0
- package/dist/core/distribution/migrate-docs.js.map +1 -0
- package/dist/core/distribution/profiles.d.ts +49 -0
- package/dist/core/distribution/profiles.d.ts.map +1 -1
- package/dist/core/distribution/profiles.js +45 -0
- package/dist/core/distribution/profiles.js.map +1 -1
- package/dist/core/distribution/update.d.ts +14 -0
- package/dist/core/distribution/update.d.ts.map +1 -1
- package/dist/core/distribution/update.js +77 -3
- package/dist/core/distribution/update.js.map +1 -1
- package/dist/core/distribution/workspace.d.ts +84 -0
- package/dist/core/distribution/workspace.d.ts.map +1 -0
- package/dist/core/distribution/workspace.js +276 -0
- package/dist/core/distribution/workspace.js.map +1 -0
- package/dist/core/exit-codes.d.ts +15 -35
- package/dist/core/exit-codes.d.ts.map +1 -1
- package/dist/core/exit-codes.js +15 -36
- package/dist/core/exit-codes.js.map +1 -1
- package/dist/core/index.d.ts +1 -6
- package/dist/core/index.d.ts.map +1 -1
- package/dist/core/index.js +1 -7
- package/dist/core/index.js.map +1 -1
- package/package.json +17 -32
- package/templates/claude/settings.json +48 -0
- package/templates/domain/ubiquitous-language.md +28 -0
- package/templates/infra/environments.yaml +16 -0
- package/templates/infra/redaction-patterns.txt +47 -0
- package/templates/runbooks/README.md +14 -0
- package/templates/runbooks/runbook-template.md +40 -0
- package/templates/scripts/deploy-status.sh +89 -0
- package/templates/scripts/deploy-verify.sh +85 -0
- package/templates/scripts/deploy.sh +284 -0
- package/templates/scripts/release.sh +170 -0
- package/templates/scripts/rollback.sh +109 -0
- package/templates/workflows/deploy-dev.yml +66 -0
- package/templates/workflows/deploy-prod.yml +66 -0
- package/templates/workflows/rollback.yml +77 -0
- package/.claude/skills/activity-contract-validation/SKILL.md +0 -167
- package/.github/skills/activity-contract-validation/SKILL.md +0 -167
- package/.kiro/skills/activity-contract-validation/SKILL.md +0 -167
- package/dist/adapters/cli/catalog-build.d.ts +0 -30
- package/dist/adapters/cli/catalog-build.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-build.js +0 -73
- package/dist/adapters/cli/catalog-build.js.map +0 -1
- package/dist/adapters/cli/catalog-query.d.ts +0 -13
- package/dist/adapters/cli/catalog-query.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-query.js +0 -329
- package/dist/adapters/cli/catalog-query.js.map +0 -1
- package/dist/adapters/cli/catalog-scaffold.d.ts +0 -24
- package/dist/adapters/cli/catalog-scaffold.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-scaffold.js +0 -46
- package/dist/adapters/cli/catalog-scaffold.js.map +0 -1
- package/dist/adapters/cli/catalog-validate.d.ts +0 -35
- package/dist/adapters/cli/catalog-validate.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-validate.js +0 -122
- package/dist/adapters/cli/catalog-validate.js.map +0 -1
- package/dist/adapters/cli/ctx-assemble.d.ts +0 -19
- package/dist/adapters/cli/ctx-assemble.d.ts.map +0 -1
- package/dist/adapters/cli/ctx-assemble.js +0 -293
- package/dist/adapters/cli/ctx-assemble.js.map +0 -1
- package/dist/adapters/cli/ctx-fetch.d.ts +0 -49
- package/dist/adapters/cli/ctx-fetch.d.ts.map +0 -1
- package/dist/adapters/cli/ctx-fetch.js +0 -267
- package/dist/adapters/cli/ctx-fetch.js.map +0 -1
- package/dist/adapters/cli/extract-all.d.ts +0 -31
- package/dist/adapters/cli/extract-all.d.ts.map +0 -1
- package/dist/adapters/cli/extract-all.js +0 -374
- package/dist/adapters/cli/extract-all.js.map +0 -1
- package/dist/adapters/cli/extract-asyncapi.d.ts +0 -26
- package/dist/adapters/cli/extract-asyncapi.d.ts.map +0 -1
- package/dist/adapters/cli/extract-asyncapi.js +0 -142
- package/dist/adapters/cli/extract-asyncapi.js.map +0 -1
- package/dist/adapters/cli/extract-component.d.ts +0 -24
- package/dist/adapters/cli/extract-component.d.ts.map +0 -1
- package/dist/adapters/cli/extract-component.js +0 -198
- package/dist/adapters/cli/extract-component.js.map +0 -1
- package/dist/adapters/cli/extract-detect.d.ts +0 -19
- package/dist/adapters/cli/extract-detect.d.ts.map +0 -1
- package/dist/adapters/cli/extract-detect.js +0 -98
- package/dist/adapters/cli/extract-detect.js.map +0 -1
- package/dist/adapters/cli/extract-openapi.d.ts +0 -29
- package/dist/adapters/cli/extract-openapi.d.ts.map +0 -1
- package/dist/adapters/cli/extract-openapi.js +0 -111
- package/dist/adapters/cli/extract-openapi.js.map +0 -1
- package/dist/adapters/cli/extract-schema.d.ts +0 -15
- package/dist/adapters/cli/extract-schema.d.ts.map +0 -1
- package/dist/adapters/cli/extract-schema.js +0 -39
- package/dist/adapters/cli/extract-schema.js.map +0 -1
- package/dist/adapters/cli/index.d.ts +0 -6
- package/dist/adapters/cli/index.d.ts.map +0 -1
- package/dist/adapters/cli/index.js +0 -5
- package/dist/adapters/cli/index.js.map +0 -1
- package/dist/adapters/cli/init.d.ts +0 -37
- package/dist/adapters/cli/init.d.ts.map +0 -1
- package/dist/adapters/cli/init.js +0 -336
- package/dist/adapters/cli/init.js.map +0 -1
- package/dist/adapters/cli/parse-args.d.ts.map +0 -1
- package/dist/adapters/cli/parse-args.js.map +0 -1
- package/dist/adapters/cli/scope-gate.d.ts +0 -25
- package/dist/adapters/cli/scope-gate.d.ts.map +0 -1
- package/dist/adapters/cli/scope-gate.js +0 -157
- package/dist/adapters/cli/scope-gate.js.map +0 -1
- package/dist/adapters/cli/scope.d.ts +0 -26
- package/dist/adapters/cli/scope.d.ts.map +0 -1
- package/dist/adapters/cli/scope.js +0 -172
- package/dist/adapters/cli/scope.js.map +0 -1
- package/dist/adapters/cli/validate-component.d.ts +0 -24
- package/dist/adapters/cli/validate-component.d.ts.map +0 -1
- package/dist/adapters/cli/validate-component.js +0 -62
- package/dist/adapters/cli/validate-component.js.map +0 -1
- package/dist/adapters/cli/verify-contract-diff.d.ts +0 -21
- package/dist/adapters/cli/verify-contract-diff.d.ts.map +0 -1
- package/dist/adapters/cli/verify-contract-diff.js +0 -69
- package/dist/adapters/cli/verify-contract-diff.js.map +0 -1
- package/dist/adapters/cli/verify-drift.d.ts +0 -24
- package/dist/adapters/cli/verify-drift.d.ts.map +0 -1
- package/dist/adapters/cli/verify-drift.js +0 -103
- package/dist/adapters/cli/verify-drift.js.map +0 -1
- package/dist/adapters/cli/verify-impact.d.ts +0 -23
- package/dist/adapters/cli/verify-impact.d.ts.map +0 -1
- package/dist/adapters/cli/verify-impact.js +0 -119
- package/dist/adapters/cli/verify-impact.js.map +0 -1
- package/dist/adapters/mcp/index.d.ts +0 -5
- package/dist/adapters/mcp/index.d.ts.map +0 -1
- package/dist/adapters/mcp/index.js +0 -2
- package/dist/adapters/mcp/index.js.map +0 -1
- package/dist/bin/dt.d.ts +0 -7
- package/dist/bin/dt.d.ts.map +0 -1
- package/dist/bin/dt.js +0 -647
- package/dist/bin/dt.js.map +0 -1
- package/dist/core/catalog/build.d.ts +0 -143
- package/dist/core/catalog/build.d.ts.map +0 -1
- package/dist/core/catalog/build.js +0 -475
- package/dist/core/catalog/build.js.map +0 -1
- package/dist/core/catalog/checks/index.d.ts +0 -18
- package/dist/core/catalog/checks/index.d.ts.map +0 -1
- package/dist/core/catalog/checks/index.js +0 -18
- package/dist/core/catalog/checks/index.js.map +0 -1
- package/dist/core/catalog/checks/v01-schema.d.ts +0 -17
- package/dist/core/catalog/checks/v01-schema.d.ts.map +0 -1
- package/dist/core/catalog/checks/v01-schema.js +0 -57
- package/dist/core/catalog/checks/v01-schema.js.map +0 -1
- package/dist/core/catalog/checks/v02-v03-identity.d.ts +0 -14
- package/dist/core/catalog/checks/v02-v03-identity.d.ts.map +0 -1
- package/dist/core/catalog/checks/v02-v03-identity.js +0 -60
- package/dist/core/catalog/checks/v02-v03-identity.js.map +0 -1
- package/dist/core/catalog/checks/v04-referential-integrity.d.ts +0 -7
- package/dist/core/catalog/checks/v04-referential-integrity.d.ts.map +0 -1
- package/dist/core/catalog/checks/v04-referential-integrity.js +0 -32
- package/dist/core/catalog/checks/v04-referential-integrity.js.map +0 -1
- package/dist/core/catalog/checks/v05-domain-existence.d.ts +0 -6
- package/dist/core/catalog/checks/v05-domain-existence.d.ts.map +0 -1
- package/dist/core/catalog/checks/v05-domain-existence.js +0 -23
- package/dist/core/catalog/checks/v05-domain-existence.js.map +0 -1
- package/dist/core/catalog/checks/v06-v07-paths.d.ts +0 -29
- package/dist/core/catalog/checks/v06-v07-paths.d.ts.map +0 -1
- package/dist/core/catalog/checks/v06-v07-paths.js +0 -107
- package/dist/core/catalog/checks/v06-v07-paths.js.map +0 -1
- package/dist/core/catalog/checks/v08-v10-contracts.d.ts +0 -13
- package/dist/core/catalog/checks/v08-v10-contracts.d.ts.map +0 -1
- package/dist/core/catalog/checks/v08-v10-contracts.js +0 -70
- package/dist/core/catalog/checks/v08-v10-contracts.js.map +0 -1
- package/dist/core/catalog/checks/v11-manual-fields.d.ts +0 -16
- package/dist/core/catalog/checks/v11-manual-fields.d.ts.map +0 -1
- package/dist/core/catalog/checks/v11-manual-fields.js +0 -60
- package/dist/core/catalog/checks/v11-manual-fields.js.map +0 -1
- package/dist/core/catalog/checks/v12-cycles.d.ts +0 -8
- package/dist/core/catalog/checks/v12-cycles.d.ts.map +0 -1
- package/dist/core/catalog/checks/v12-cycles.js +0 -28
- package/dist/core/catalog/checks/v12-cycles.js.map +0 -1
- package/dist/core/catalog/checks/v13-orphan-contracts.d.ts +0 -7
- package/dist/core/catalog/checks/v13-orphan-contracts.d.ts.map +0 -1
- package/dist/core/catalog/checks/v13-orphan-contracts.js +0 -33
- package/dist/core/catalog/checks/v13-orphan-contracts.js.map +0 -1
- package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts +0 -8
- package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts.map +0 -1
- package/dist/core/catalog/checks/v14-v15-lifecycle.js +0 -42
- package/dist/core/catalog/checks/v14-v15-lifecycle.js.map +0 -1
- package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts +0 -7
- package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts.map +0 -1
- package/dist/core/catalog/checks/v16-deprecated-consumers.js +0 -47
- package/dist/core/catalog/checks/v16-deprecated-consumers.js.map +0 -1
- package/dist/core/catalog/checks/v17-low-confidence.d.ts +0 -7
- package/dist/core/catalog/checks/v17-low-confidence.d.ts.map +0 -1
- package/dist/core/catalog/checks/v17-low-confidence.js +0 -32
- package/dist/core/catalog/checks/v17-low-confidence.js.map +0 -1
- package/dist/core/catalog/checks/v18-low-payload.d.ts +0 -7
- package/dist/core/catalog/checks/v18-low-payload.d.ts.map +0 -1
- package/dist/core/catalog/checks/v18-low-payload.js +0 -33
- package/dist/core/catalog/checks/v18-low-payload.js.map +0 -1
- package/dist/core/catalog/checks/v19-domain-membership.d.ts +0 -8
- package/dist/core/catalog/checks/v19-domain-membership.d.ts.map +0 -1
- package/dist/core/catalog/checks/v19-domain-membership.js +0 -55
- package/dist/core/catalog/checks/v19-domain-membership.js.map +0 -1
- package/dist/core/catalog/coverage.d.ts +0 -39
- package/dist/core/catalog/coverage.d.ts.map +0 -1
- package/dist/core/catalog/coverage.js +0 -62
- package/dist/core/catalog/coverage.js.map +0 -1
- package/dist/core/catalog/graph.d.ts +0 -49
- package/dist/core/catalog/graph.d.ts.map +0 -1
- package/dist/core/catalog/graph.js +0 -114
- package/dist/core/catalog/graph.js.map +0 -1
- package/dist/core/catalog/index-model.d.ts +0 -96
- package/dist/core/catalog/index-model.d.ts.map +0 -1
- package/dist/core/catalog/index-model.js +0 -8
- package/dist/core/catalog/index-model.js.map +0 -1
- package/dist/core/catalog/index.d.ts +0 -5
- package/dist/core/catalog/index.d.ts.map +0 -1
- package/dist/core/catalog/index.js +0 -2
- package/dist/core/catalog/index.js.map +0 -1
- package/dist/core/catalog/queries.d.ts +0 -69
- package/dist/core/catalog/queries.d.ts.map +0 -1
- package/dist/core/catalog/queries.js +0 -165
- package/dist/core/catalog/queries.js.map +0 -1
- package/dist/core/catalog/resolve.d.ts +0 -47
- package/dist/core/catalog/resolve.d.ts.map +0 -1
- package/dist/core/catalog/resolve.js +0 -318
- package/dist/core/catalog/resolve.js.map +0 -1
- package/dist/core/catalog/scaffold.d.ts +0 -31
- package/dist/core/catalog/scaffold.d.ts.map +0 -1
- package/dist/core/catalog/scaffold.js +0 -141
- package/dist/core/catalog/scaffold.js.map +0 -1
- package/dist/core/catalog/validate-component.d.ts +0 -50
- package/dist/core/catalog/validate-component.d.ts.map +0 -1
- package/dist/core/catalog/validate-component.js +0 -105
- package/dist/core/catalog/validate-component.js.map +0 -1
- package/dist/core/catalog/validate.d.ts +0 -71
- package/dist/core/catalog/validate.d.ts.map +0 -1
- package/dist/core/catalog/validate.js +0 -103
- package/dist/core/catalog/validate.js.map +0 -1
- package/dist/core/context/assemble.d.ts +0 -126
- package/dist/core/context/assemble.d.ts.map +0 -1
- package/dist/core/context/assemble.js +0 -197
- package/dist/core/context/assemble.js.map +0 -1
- package/dist/core/context/cache.d.ts +0 -60
- package/dist/core/context/cache.d.ts.map +0 -1
- package/dist/core/context/cache.js +0 -236
- package/dist/core/context/cache.js.map +0 -1
- package/dist/core/context/exit-codes.d.ts +0 -28
- package/dist/core/context/exit-codes.d.ts.map +0 -1
- package/dist/core/context/exit-codes.js +0 -28
- package/dist/core/context/exit-codes.js.map +0 -1
- package/dist/core/context/fetch.d.ts +0 -55
- package/dist/core/context/fetch.d.ts.map +0 -1
- package/dist/core/context/fetch.js +0 -112
- package/dist/core/context/fetch.js.map +0 -1
- package/dist/core/context/index.d.ts +0 -11
- package/dist/core/context/index.d.ts.map +0 -1
- package/dist/core/context/index.js +0 -8
- package/dist/core/context/index.js.map +0 -1
- package/dist/core/context/init.d.ts +0 -179
- package/dist/core/context/init.d.ts.map +0 -1
- package/dist/core/context/init.js +0 -532
- package/dist/core/context/init.js.map +0 -1
- package/dist/core/context/layers/architecture-layer.d.ts +0 -13
- package/dist/core/context/layers/architecture-layer.d.ts.map +0 -1
- package/dist/core/context/layers/architecture-layer.js +0 -24
- package/dist/core/context/layers/architecture-layer.js.map +0 -1
- package/dist/core/context/layers/contracts-layer.d.ts +0 -13
- package/dist/core/context/layers/contracts-layer.d.ts.map +0 -1
- package/dist/core/context/layers/contracts-layer.js +0 -83
- package/dist/core/context/layers/contracts-layer.js.map +0 -1
- package/dist/core/context/layers/conventions-delta-layer.d.ts +0 -13
- package/dist/core/context/layers/conventions-delta-layer.d.ts.map +0 -1
- package/dist/core/context/layers/conventions-delta-layer.js +0 -37
- package/dist/core/context/layers/conventions-delta-layer.js.map +0 -1
- package/dist/core/context/layers/flow-layer.d.ts +0 -14
- package/dist/core/context/layers/flow-layer.d.ts.map +0 -1
- package/dist/core/context/layers/flow-layer.js +0 -61
- package/dist/core/context/layers/flow-layer.js.map +0 -1
- package/dist/core/context/layers/index-layer.d.ts +0 -13
- package/dist/core/context/layers/index-layer.d.ts.map +0 -1
- package/dist/core/context/layers/index-layer.js +0 -77
- package/dist/core/context/layers/index-layer.js.map +0 -1
- package/dist/core/context/layers/primary-layer.d.ts +0 -16
- package/dist/core/context/layers/primary-layer.d.ts.map +0 -1
- package/dist/core/context/layers/primary-layer.js +0 -61
- package/dist/core/context/layers/primary-layer.js.map +0 -1
- package/dist/core/context/layers/secondary-layer.d.ts +0 -19
- package/dist/core/context/layers/secondary-layer.d.ts.map +0 -1
- package/dist/core/context/layers/secondary-layer.js +0 -52
- package/dist/core/context/layers/secondary-layer.js.map +0 -1
- package/dist/core/context/session-lock.d.ts +0 -114
- package/dist/core/context/session-lock.d.ts.map +0 -1
- package/dist/core/context/session-lock.js +0 -90
- package/dist/core/context/session-lock.js.map +0 -1
- package/dist/core/context/tokens.d.ts +0 -35
- package/dist/core/context/tokens.d.ts.map +0 -1
- package/dist/core/context/tokens.js +0 -88
- package/dist/core/context/tokens.js.map +0 -1
- package/dist/core/extract/asyncapi/declared.d.ts +0 -19
- package/dist/core/extract/asyncapi/declared.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/declared.js +0 -168
- package/dist/core/extract/asyncapi/declared.js.map +0 -1
- package/dist/core/extract/asyncapi/index.d.ts +0 -12
- package/dist/core/extract/asyncapi/index.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/index.js +0 -8
- package/dist/core/extract/asyncapi/index.js.map +0 -1
- package/dist/core/extract/asyncapi/payloads.d.ts +0 -20
- package/dist/core/extract/asyncapi/payloads.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/payloads.js +0 -421
- package/dist/core/extract/asyncapi/payloads.js.map +0 -1
- package/dist/core/extract/asyncapi/topics.d.ts +0 -27
- package/dist/core/extract/asyncapi/topics.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/topics.js +0 -368
- package/dist/core/extract/asyncapi/topics.js.map +0 -1
- package/dist/core/extract/asyncapi/types.d.ts +0 -129
- package/dist/core/extract/asyncapi/types.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/types.js +0 -5
- package/dist/core/extract/asyncapi/types.js.map +0 -1
- package/dist/core/extract/asyncapi/validate.d.ts +0 -29
- package/dist/core/extract/asyncapi/validate.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/validate.js +0 -156
- package/dist/core/extract/asyncapi/validate.js.map +0 -1
- package/dist/core/extract/component.d.ts +0 -204
- package/dist/core/extract/component.d.ts.map +0 -1
- package/dist/core/extract/component.js +0 -258
- package/dist/core/extract/component.js.map +0 -1
- package/dist/core/extract/detect.d.ts +0 -35
- package/dist/core/extract/detect.d.ts.map +0 -1
- package/dist/core/extract/detect.js +0 -89
- package/dist/core/extract/detect.js.map +0 -1
- package/dist/core/extract/index.d.ts +0 -12
- package/dist/core/extract/index.d.ts.map +0 -1
- package/dist/core/extract/index.js +0 -6
- package/dist/core/extract/index.js.map +0 -1
- package/dist/core/extract/ladder.d.ts +0 -79
- package/dist/core/extract/ladder.d.ts.map +0 -1
- package/dist/core/extract/ladder.js +0 -70
- package/dist/core/extract/ladder.js.map +0 -1
- package/dist/core/extract/openapi/index.d.ts +0 -43
- package/dist/core/extract/openapi/index.d.ts.map +0 -1
- package/dist/core/extract/openapi/index.js +0 -142
- package/dist/core/extract/openapi/index.js.map +0 -1
- package/dist/core/extract/openapi/route1.d.ts +0 -36
- package/dist/core/extract/openapi/route1.d.ts.map +0 -1
- package/dist/core/extract/openapi/route1.js +0 -333
- package/dist/core/extract/openapi/route1.js.map +0 -1
- package/dist/core/extract/openapi/route2-introspect.d.ts +0 -18
- package/dist/core/extract/openapi/route2-introspect.d.ts.map +0 -1
- package/dist/core/extract/openapi/route2-introspect.js +0 -249
- package/dist/core/extract/openapi/route2-introspect.js.map +0 -1
- package/dist/core/extract/openapi/route2.d.ts +0 -69
- package/dist/core/extract/openapi/route2.d.ts.map +0 -1
- package/dist/core/extract/openapi/route2.js +0 -211
- package/dist/core/extract/openapi/route2.js.map +0 -1
- package/dist/core/extract/openapi/route3.d.ts +0 -26
- package/dist/core/extract/openapi/route3.d.ts.map +0 -1
- package/dist/core/extract/openapi/route3.js +0 -737
- package/dist/core/extract/openapi/route3.js.map +0 -1
- package/dist/core/extract/openapi/types.d.ts +0 -125
- package/dist/core/extract/openapi/types.d.ts.map +0 -1
- package/dist/core/extract/openapi/types.js +0 -5
- package/dist/core/extract/openapi/types.js.map +0 -1
- package/dist/core/extract/openapi/validate.d.ts +0 -29
- package/dist/core/extract/openapi/validate.d.ts.map +0 -1
- package/dist/core/extract/openapi/validate.js +0 -200
- package/dist/core/extract/openapi/validate.js.map +0 -1
- package/dist/core/extract/orm/drizzle.d.ts +0 -20
- package/dist/core/extract/orm/drizzle.d.ts.map +0 -1
- package/dist/core/extract/orm/drizzle.js +0 -283
- package/dist/core/extract/orm/drizzle.js.map +0 -1
- package/dist/core/extract/orm/information-schema.d.ts +0 -26
- package/dist/core/extract/orm/information-schema.d.ts.map +0 -1
- package/dist/core/extract/orm/information-schema.js +0 -142
- package/dist/core/extract/orm/information-schema.js.map +0 -1
- package/dist/core/extract/orm/prisma.d.ts +0 -23
- package/dist/core/extract/orm/prisma.d.ts.map +0 -1
- package/dist/core/extract/orm/prisma.js +0 -234
- package/dist/core/extract/orm/prisma.js.map +0 -1
- package/dist/core/extract/orm/typeorm.d.ts +0 -22
- package/dist/core/extract/orm/typeorm.d.ts.map +0 -1
- package/dist/core/extract/orm/typeorm.js +0 -269
- package/dist/core/extract/orm/typeorm.js.map +0 -1
- package/dist/core/extract/orm/types.d.ts +0 -97
- package/dist/core/extract/orm/types.d.ts.map +0 -1
- package/dist/core/extract/orm/types.js +0 -6
- package/dist/core/extract/orm/types.js.map +0 -1
- package/dist/core/extract/prompt.d.ts +0 -21
- package/dist/core/extract/prompt.d.ts.map +0 -1
- package/dist/core/extract/prompt.js +0 -79
- package/dist/core/extract/prompt.js.map +0 -1
- package/dist/core/extract/provider.d.ts +0 -121
- package/dist/core/extract/provider.d.ts.map +0 -1
- package/dist/core/extract/provider.js +0 -6
- package/dist/core/extract/provider.js.map +0 -1
- package/dist/core/extract/providers/node-ts.d.ts +0 -69
- package/dist/core/extract/providers/node-ts.d.ts.map +0 -1
- package/dist/core/extract/providers/node-ts.js +0 -320
- package/dist/core/extract/providers/node-ts.js.map +0 -1
- package/dist/core/extract/render/schema-md.d.ts +0 -16
- package/dist/core/extract/render/schema-md.d.ts.map +0 -1
- package/dist/core/extract/render/schema-md.js +0 -140
- package/dist/core/extract/render/schema-md.js.map +0 -1
- package/dist/core/extract/report.d.ts +0 -125
- package/dist/core/extract/report.d.ts.map +0 -1
- package/dist/core/extract/report.js +0 -52
- package/dist/core/extract/report.js.map +0 -1
- package/dist/core/extract/schema.d.ts +0 -34
- package/dist/core/extract/schema.d.ts.map +0 -1
- package/dist/core/extract/schema.js +0 -146
- package/dist/core/extract/schema.js.map +0 -1
- package/dist/core/extract/workspaces.d.ts +0 -33
- package/dist/core/extract/workspaces.d.ts.map +0 -1
- package/dist/core/extract/workspaces.js +0 -193
- package/dist/core/extract/workspaces.js.map +0 -1
- package/dist/core/providers/index.d.ts +0 -6
- package/dist/core/providers/index.d.ts.map +0 -1
- package/dist/core/providers/index.js +0 -2
- package/dist/core/providers/index.js.map +0 -1
- package/dist/core/providers/tracker.d.ts +0 -74
- package/dist/core/providers/tracker.d.ts.map +0 -1
- package/dist/core/providers/tracker.js +0 -38
- package/dist/core/providers/tracker.js.map +0 -1
- package/dist/core/scope/calibration.d.ts +0 -25
- package/dist/core/scope/calibration.d.ts.map +0 -1
- package/dist/core/scope/calibration.js +0 -52
- package/dist/core/scope/calibration.js.map +0 -1
- package/dist/core/scope/closure.d.ts +0 -31
- package/dist/core/scope/closure.d.ts.map +0 -1
- package/dist/core/scope/closure.js +0 -68
- package/dist/core/scope/closure.js.map +0 -1
- package/dist/core/scope/gate.d.ts +0 -41
- package/dist/core/scope/gate.d.ts.map +0 -1
- package/dist/core/scope/gate.js +0 -165
- package/dist/core/scope/gate.js.map +0 -1
- package/dist/core/scope/index.d.ts +0 -18
- package/dist/core/scope/index.d.ts.map +0 -1
- package/dist/core/scope/index.js +0 -12
- package/dist/core/scope/index.js.map +0 -1
- package/dist/core/scope/partition.d.ts +0 -36
- package/dist/core/scope/partition.d.ts.map +0 -1
- package/dist/core/scope/partition.js +0 -78
- package/dist/core/scope/partition.js.map +0 -1
- package/dist/core/scope/prompt.d.ts +0 -39
- package/dist/core/scope/prompt.d.ts.map +0 -1
- package/dist/core/scope/prompt.js +0 -123
- package/dist/core/scope/prompt.js.map +0 -1
- package/dist/core/scope/scoping.d.ts +0 -52
- package/dist/core/scope/scoping.d.ts.map +0 -1
- package/dist/core/scope/scoping.js +0 -99
- package/dist/core/scope/scoping.js.map +0 -1
- package/dist/core/scope/types.d.ts +0 -77
- package/dist/core/scope/types.d.ts.map +0 -1
- package/dist/core/scope/types.js +0 -5
- package/dist/core/scope/types.js.map +0 -1
- package/dist/core/scope/validate.d.ts +0 -47
- package/dist/core/scope/validate.d.ts.map +0 -1
- package/dist/core/scope/validate.js +0 -90
- package/dist/core/scope/validate.js.map +0 -1
- package/dist/core/verify/asyncapi-diff.d.ts +0 -34
- package/dist/core/verify/asyncapi-diff.d.ts.map +0 -1
- package/dist/core/verify/asyncapi-diff.js +0 -209
- package/dist/core/verify/asyncapi-diff.js.map +0 -1
- package/dist/core/verify/contract-diff.d.ts +0 -39
- package/dist/core/verify/contract-diff.d.ts.map +0 -1
- package/dist/core/verify/contract-diff.js +0 -63
- package/dist/core/verify/contract-diff.js.map +0 -1
- package/dist/core/verify/drift.d.ts +0 -47
- package/dist/core/verify/drift.d.ts.map +0 -1
- package/dist/core/verify/drift.js +0 -122
- package/dist/core/verify/drift.js.map +0 -1
- package/dist/core/verify/impact.d.ts +0 -22
- package/dist/core/verify/impact.d.ts.map +0 -1
- package/dist/core/verify/impact.js +0 -93
- package/dist/core/verify/impact.js.map +0 -1
- package/dist/core/verify/index.d.ts +0 -10
- package/dist/core/verify/index.d.ts.map +0 -1
- package/dist/core/verify/index.js +0 -9
- package/dist/core/verify/index.js.map +0 -1
- package/dist/core/verify/openapi-diff.d.ts +0 -29
- package/dist/core/verify/openapi-diff.d.ts.map +0 -1
- package/dist/core/verify/openapi-diff.js +0 -291
- package/dist/core/verify/openapi-diff.js.map +0 -1
- package/dist/core/verify/types.d.ts +0 -138
- package/dist/core/verify/types.d.ts.map +0 -1
- package/dist/core/verify/types.js +0 -5
- package/dist/core/verify/types.js.map +0 -1
- package/schemas/component.schema.json +0 -203
- package/schemas/flow.schema.json +0 -75
- package/schemas/scope-output.schema.json +0 -62
|
@@ -65,7 +65,7 @@ The task list **MUST** follow this structure:
|
|
|
65
65
|
|
|
66
66
|
- [ ] 1.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
67
67
|
|
|
68
|
-
- [ ] 1.1 [First implementation step]
|
|
68
|
+
- [ ] 1.1 [First implementation step] (D-NN, when traceable — omit otherwise)
|
|
69
69
|
- [ ] 1.2 [Second implementation step]
|
|
70
70
|
- [ ] 1.x Verify Acceptance Criterion: [Criterion 1]
|
|
71
71
|
- [ ] 1.y Verify Acceptance Criterion: [Criterion 2]
|
|
@@ -74,8 +74,48 @@ The task list **MUST** follow this structure:
|
|
|
74
74
|
- [ ] 2.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
75
75
|
- [ ] 2.1 [First implementation step]
|
|
76
76
|
- ...
|
|
77
|
+
|
|
78
|
+
## Decisions Consumed
|
|
79
|
+
|
|
80
|
+
| ID | Decision (short form) |
|
|
81
|
+
| ---- | --------------------- |
|
|
82
|
+
| D-NN | … |
|
|
77
83
|
```
|
|
78
84
|
|
|
85
|
+
## Decision Citations
|
|
86
|
+
|
|
87
|
+
A task line that derives from a specific decision cites it inline, at the
|
|
88
|
+
end of the line: `- [ ] 3.2 Add cap-reached prompt (D-55)` (FR-16).
|
|
89
|
+
|
|
90
|
+
- Citations reference the feature's own `decisions-<feature>.md` by
|
|
91
|
+
unqualified `D-NN` — a task list belongs to exactly one feature, so the
|
|
92
|
+
qualified `<feature>#D-NN` form `activity-refine`/`activity-generate-spec`
|
|
93
|
+
use for cross-feature reuse is never needed here.
|
|
94
|
+
- This is **additive only**: a task with no traceable decision cites none.
|
|
95
|
+
You **MUST NOT** fabricate a citation to give a task one.
|
|
96
|
+
- The task list closes with a `## Decisions Consumed` section aggregating
|
|
97
|
+
every decision ID cited anywhere in the list, in the same `ID | Decision
|
|
98
|
+
(short form)` table shape the decision log itself uses. A task list that
|
|
99
|
+
cites no decisions still includes the section, empty (header plus
|
|
100
|
+
table skeleton, no rows) — consistent with how `activity-refine`'s and
|
|
101
|
+
`activity-generate-spec`'s own `## Decisions` sections may legitimately
|
|
102
|
+
be empty.
|
|
103
|
+
|
|
104
|
+
## Package Attribution
|
|
105
|
+
|
|
106
|
+
Every task **MUST** name the package it changes (FR-63), so a reader can
|
|
107
|
+
tell the blast radius from the task list without opening the diff.
|
|
108
|
+
|
|
109
|
+
- Read the package map in `docs/tech.md` for the package list.
|
|
110
|
+
- Write the package in the sub-task text, in brackets, first:
|
|
111
|
+
`- [ ] 1.1 [@acme/api] Add the token-refresh endpoint`.
|
|
112
|
+
- A sub-task touching several packages lists them all. A sub-task that
|
|
113
|
+
touches _most_ packages is usually the wrong size — split it.
|
|
114
|
+
- In a **single-package repository the bracket is omitted**, not left
|
|
115
|
+
empty. It is optional there, never blank.
|
|
116
|
+
- Non-code tasks (docs, workflow files) that belong to no package use
|
|
117
|
+
`[repo root]`.
|
|
118
|
+
|
|
79
119
|
## Conversion Guidelines
|
|
80
120
|
|
|
81
121
|
When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
@@ -94,6 +134,7 @@ When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
|
94
134
|
- If schema or data-model changes are involved, migration tasks are **required by default**; omission is allowed only with an explicit documented opt-out rationale.
|
|
95
135
|
- Migration flows **MUST** include: create migration artifact, document rollback/impact, request user confirmation before apply, apply migration after confirmation, and verify applied state.
|
|
96
136
|
- If the story involves data models, you **SHOULD** include a sub-task to generate seed data.
|
|
137
|
+
- When `workstream/decisions-<feature>.md` exists, you **MUST** cite the decision ID inline (`… (D-NN)`) on any sub-task whose approach or scope traces to a specific decision row, and **MUST** populate the closing `## Decisions Consumed` section with every ID cited anywhere in the list. This is additive only — a sub-task with no traceable decision cites none; do not fabricate a citation.
|
|
97
138
|
|
|
98
139
|
3. **Context:** You **MAY** add a `> Note:` block under the parent task for quick reference (User Story text or Business Rules), but the checkbox structure **MUST** remain clean.
|
|
99
140
|
4. **Relevant Files:** You **MUST** aggregate all "Files to Create/Modify" from selected stories into the top-level `Relevant Files` section.
|
|
@@ -139,6 +180,7 @@ If this is a **greenfield project** or a **new component**, you **MUST** include
|
|
|
139
180
|
5. You **MUST** ensure all Implementation Steps, Acceptance Criteria, and Testing requirements are preserved as sub-tasks.
|
|
140
181
|
6. For JS/TS repositories, you **MUST** prefer `pnpm` commands and canonical script names in generated tasks.
|
|
141
182
|
7. You **MUST** ensure each task includes both implementation and test/validation steps, including edge-case validation.
|
|
183
|
+
7a. When a decision log exists for the feature, you **MUST** cite the decision ID inline on any traceable sub-task and populate the closing `## Decisions Consumed` section (FR-16) — additively, never fabricated.
|
|
142
184
|
8. For schema/data-model changes, you **MUST** include migration lifecycle tasks and an explicit user-confirmation gate before applying migrations unless an opt-out rationale is documented.
|
|
143
185
|
9. You **MUST** update the corresponding GitHub Issue(s) with the task checklist by delegating to `github-ops` whenever possible. If no issue exists, you **MUST** ask the user whether to create one first.
|
|
144
186
|
10. You **MUST** save the task list file.
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: supabase-ops
|
|
3
|
+
description: "Supabase CLI command sets, db diff migration flow, drift rule, backup/revert sources, inventory findings, and Cloud log table for infra-engineer. Use when planning or applying Supabase infrastructure changes."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Supabase Operations (supabase-ops)
|
|
7
|
+
|
|
8
|
+
Per-surface mechanism skill for `infra-engineer`. It supplies the Supabase CLI command sets, resource tiers, the `db diff` migration flow, the drift rule, backup and revert sources, inventory findings, and the Supabase Cloud log table. It does not restate the agent's working loop, approval, revert, or backup rules — those live in the agent body. Supabase is the one platform with a genuine plan mechanism (`db diff`), and its keys are the highest-value secrets in the stack.
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
> **RFC 2119 Notice:** The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
|
|
13
|
+
|
|
14
|
+
## Tool declaration
|
|
15
|
+
|
|
16
|
+
| Field | Value |
|
|
17
|
+
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
18
|
+
| `name` | `supabase` |
|
|
19
|
+
| `probe` | `supabase --version` (expects `2.x`) |
|
|
20
|
+
| `floor` | Supabase CLI `2.x`; minimum `2.11`. A `1.x` install is `below-floor`. |
|
|
21
|
+
| `auth_probe` | `supabase projects list` |
|
|
22
|
+
| `remediation` | "Install Supabase CLI v2 and run `supabase login` (or export `SUPABASE_ACCESS_TOKEN`); link the project with `supabase link --project-ref <ref>`. This skill never auto-installs and offers no fallback." |
|
|
23
|
+
|
|
24
|
+
Identity is asserted by comparing the linked project ref (from `supabase projects list` / the linked `project_ref`) with the target environment's `supabase.project_ref`; a mismatch is `wrong-identity` and blocks.
|
|
25
|
+
|
|
26
|
+
## Resource tiers
|
|
27
|
+
|
|
28
|
+
| Tier | Supabase resources |
|
|
29
|
+
| --------------- | ------------------------------------------------------------------------------------- |
|
|
30
|
+
| **foundation** | project, plan, compute add-on, read replicas, PITR |
|
|
31
|
+
| **application** | schema, migrations, RLS policies, roles, storage buckets, auth config, Edge Functions |
|
|
32
|
+
| **ephemeral** | preview branches, which carry an `ExpiresAt` tag and a cleanup step |
|
|
33
|
+
|
|
34
|
+
Foundation changes are routed to `tier0_tool`, never written by this agent. Project deletion is refused for a production-mapped project.
|
|
35
|
+
|
|
36
|
+
## Migration flow (db diff as plan)
|
|
37
|
+
|
|
38
|
+
1. `supabase db diff -f "$NAME"` produces the migration SQL — this **is** the plan. Do not push before it is reviewed.
|
|
39
|
+
2. **Destructive statements** (`DROP`, `TRUNCATE`, `ALTER ... DROP COLUMN`, type narrowing) are itemized separately in `plan.md`, each as its own line requiring named approval.
|
|
40
|
+
3. Confirmation is required before `supabase db push` to any shared or production project. The push runs only after the human approves that step.
|
|
41
|
+
4. Verification: `supabase migration list` shows the new migration applied on the remote.
|
|
42
|
+
5. **Drift rule:** a non-empty `supabase db diff` against the remote with **no pending local migration** is reported as drift and **never pushed**. Drift is reported, never reconciled by pushing. The agent records the drift in `result.md` and stops.
|
|
43
|
+
|
|
44
|
+
```sh
|
|
45
|
+
supabase db diff -f add_orders_table # plan
|
|
46
|
+
# review the generated migration; itemize destructive statements
|
|
47
|
+
supabase db push # apply, only after confirmation
|
|
48
|
+
supabase migration list # verify
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
## Backup
|
|
52
|
+
|
|
53
|
+
Before any production step touching schema or data, record a backup: `supabase db dump -f backup.sql --data-only` (and a schema dump) **or** a recorded PITR restore point when PITR is enabled on the project. The backup artifact reference and the restore command are recorded in `result.md` before the step applies. Revert of a schema change is a forward migration that reverses it, applied through the same confirmed flow; there is no silent `db reset` against a shared project.
|
|
54
|
+
|
|
55
|
+
## Discovery order
|
|
56
|
+
|
|
57
|
+
Discovery prefers **Supabase MCP read-only** when present, then the **CLI**, then the **Management API**, and records which path was used in the inventory `_generated` block. Writes never go through MCP — MCP is read-only for discovery only. No MCP write, ever.
|
|
58
|
+
|
|
59
|
+
## Inventory and findings
|
|
60
|
+
|
|
61
|
+
Inventory files under `infra/inventory/supabase/<ref>.json` carry the standard `_generated` header and these fields:
|
|
62
|
+
|
|
63
|
+
- `has_legacy_keys: bool` — reported as a finding when legacy (pre-publishable/secret) keys are still in use.
|
|
64
|
+
- `rls_disabled_tables: []` — tables with row-level security disabled, reported as findings.
|
|
65
|
+
|
|
66
|
+
Inventory contains **no key material**, masked or otherwise. Reporting `has_legacy_keys` or `rls_disabled_tables` never includes the key or a sample row.
|
|
67
|
+
|
|
68
|
+
## Secrets
|
|
69
|
+
|
|
70
|
+
- Edge Function secrets are set with `supabase secrets set KEY=value` / `supabase secrets unset KEY`, from the source of truth, never a transcript.
|
|
71
|
+
- **Publishable versus secret keys** are distinguished at every reference: a `sb_publishable_*` key is client-safe; a `sb_secret_*` key and the `service_role` JWT are server-only and never leave a secret store.
|
|
72
|
+
- No AWS Secrets Manager entry for a Supabase-only workload; Supabase secrets stay on Supabase.
|
|
73
|
+
|
|
74
|
+
## Supabase Cloud log table
|
|
75
|
+
|
|
76
|
+
Retrieval, retention, and query bounds are grounded in `workstream/research-supabase-logs.md` (researcher pass, 2025-09-12). Key facts cited from that artifact:
|
|
77
|
+
|
|
78
|
+
- **The Supabase CLI has no log command on Cloud.** The scriptable path is the Management API logs endpoint `GET /v1/projects/{ref}/analytics/endpoints/logs`, which runs a ClickHouse-dialect SQL/LQL query over a unified logs stream filtered by a `source` column; the Dashboard Logs Explorer is the interactive equivalent. `supabase inspect db ...` is Postgres diagnostics, not service logs.
|
|
79
|
+
- **Time bounds are mandatory in practice:** the endpoint uses `iso_timestamp_start` / `iso_timestamp_end`, the window MUST be ≤ 24 hours, and an omitted range queries only the last minute — so every triage query states an explicit UTC window before it runs.
|
|
80
|
+
|
|
81
|
+
| Service surface | Source selector / collection | Retrieval path |
|
|
82
|
+
| --------------- | ------------------------------------------------------------- | --------------------------------------- |
|
|
83
|
+
| Postgres | `source = postgres_logs` | Management API logs endpoint; Dashboard |
|
|
84
|
+
| API (PostgREST) | API Gateway collection | Management API logs endpoint; Dashboard |
|
|
85
|
+
| Auth (GoTrue) | Auth collection | Management API logs endpoint; Dashboard |
|
|
86
|
+
| Storage | Storage collection | Management API logs endpoint; Dashboard |
|
|
87
|
+
| Realtime | Realtime collection | Management API logs endpoint; Dashboard |
|
|
88
|
+
| Edge Functions | `source = edge_logs` / `function_edge_logs` / `function_logs` | Management API logs endpoint; Dashboard |
|
|
89
|
+
|
|
90
|
+
**Retention caveat (cite the research artifact, re-confirm at citation time):** built-in log retention is short and plan-gated — Free ≈ 1 day, Pro ≈ 7 days, Team ≈ 28 days, Enterprise ≈ 90 days. Because low-tier retention is short, logs MUST be captured at incident time; Log Drains (Team/Enterprise) is the long-retention path. Exact `source` strings for API/Auth/Storage/Realtime are UNCONFIRMED in the research and must be verified from the Logs Explorer source list before hardcoding. All log output passes through the redaction pattern set before it reaches a transcript or file.
|
|
91
|
+
|
|
92
|
+
## Cost entries and sweep
|
|
93
|
+
|
|
94
|
+
Cost entries listed on every Supabase plan:
|
|
95
|
+
|
|
96
|
+
- **Plan** tier (Free/Pro/Team/Enterprise) base.
|
|
97
|
+
- **Compute** add-on size.
|
|
98
|
+
- **Read replicas**.
|
|
99
|
+
- **PITR** add-on.
|
|
100
|
+
- **Preview branches**.
|
|
101
|
+
- **Egress**.
|
|
102
|
+
|
|
103
|
+
Sweep categories (read-only, reported never remediated):
|
|
104
|
+
|
|
105
|
+
- Preview branches past their `ExpiresAt` tag.
|
|
106
|
+
- Preview branches without any `ExpiresAt` tag.
|
|
107
|
+
- Paid but idle projects.
|
|
108
|
+
- Read replicas with no traffic.
|
|
109
|
+
- PITR enabled on a non-production project.
|
|
@@ -74,7 +74,7 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
74
74
|
8. **Update Relevant Files:** You **MUST** keep the task file's Relevant Files section accurate.
|
|
75
75
|
9. **English-only outputs:** You **MUST** produce English-only output for docs, comments, and generated content.
|
|
76
76
|
10. **Documentation gate before completion:** Before marking a story/issue complete or converting the PR to Ready for Review, you **MUST** invoke `technical-writer` to update current-state docs and keep `/docs` aligned with implemented behavior.
|
|
77
|
-
11. **ADR enforcement:** If `/docs/
|
|
77
|
+
11. **ADR enforcement:** If `/docs/tech.md` changes during the documentation pass, you **MUST** ensure a new ADR is created in `/docs/adr/`.
|
|
78
78
|
12. **GitHub hygiene:** All issues, PRs, labels, milestones, and comments **MUST** conform to `github-ops` conventions.
|
|
79
79
|
13. **Git operations:** For complex git operations (rebase, merge conflicts, branch updates), you **SHOULD** invoke the `git-ops` skill for standardized procedures.
|
|
80
80
|
14. **DESIGN.md compliance:** If a sub-task changes UI behavior, visual styling, or component variants, you **MUST** verify compliance with `/DESIGN.md` and update `/DESIGN.md` when the visual contract changes.
|
|
@@ -83,9 +83,8 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
83
83
|
17. **Migration safety gate:** For schema/data-model changes, you **MUST** obtain explicit user confirmation before running any migration apply command.
|
|
84
84
|
18. **Mandatory verifier audit trigger:** You **MUST** invoke `verifier` in `audit` mode post-implementation and pre-PR-ready, for every issue you implement, with no path that skips the call. This is not optional and is not gated behind user request. You **MUST** post the resulting human-readable summary to the issue/PR via `github-ops` comment conventions as part of this same step. Drift findings from the audit **MUST NOT** block completion — remediation of Unintended drift and PRD/spec changelog updates for Intended drift are routed through `product-engineer`'s `activity-drift-reconciliation` skill, not handled inline by `developer`.
|
|
85
85
|
19. **Test-first design (default approach):** The default development approach is **test-first design**. For each sub-task that introduces or modifies behavior, you **MUST** write or update tests _before_ writing the implementation code, unless the sub-task is purely infrastructure/config with no testable behavior. When a `verifier` Design Mode test plan exists (`/workstream/test-plan-*.md`), you **MUST** use it as the primary guide for which tests to write first. If no test plan exists, derive test cases from the acceptance criteria in the task list before coding.
|
|
86
|
-
20. **
|
|
87
|
-
21. **
|
|
88
|
-
22. **Mandatory QA coverage gate:** You **MUST** invoke `qa-engineer` at the completion gate, immediately before the `verifier` audit, for every issue you implement. Record its result as `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`. The gate **MAY** be skipped only with a recorded non-empty reason; omitting the field is treated as incomplete. Its procedure lives in the `qa-engineer` prompt and its skills and **MUST NOT** be restated here.
|
|
86
|
+
20. **Mandatory QA coverage gate:** You **MUST** invoke `qa-engineer` at the completion gate, immediately before the `verifier` audit, for every issue you implement. Record its result as `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`. The gate **MAY** be skipped only with a recorded non-empty reason; omitting the field is treated as incomplete. Its procedure lives in the `qa-engineer` prompt and its skills and **MUST NOT** be restated here.
|
|
87
|
+
21. **Platform-write prohibition — route to `infra-engineer`:** You **MUST NOT** emit or execute a platform write command — this includes `aws`, `flyctl`, `supabase`, and Cloudflare API writes. When a sub-task's work is a platform write, you **MUST** hand it to `infra-engineer` instead of running it yourself, so the approval, revert, and backup gates bind. The sub-task kinds that route are: **secrets**, **deploy**, **DNS**, **certificates**, **IAM policy**, and **migrations against a shared or cloud project**. This rule narrows rule 19's "purely infrastructure/config" exemption: that exemption covers only local, version-controlled edits (config files, scaffolding, `.env.example`) and is **not** a licence to run platform writes — a sub-task that would touch a live platform is never treated as exempt and always routes here. This routing is conditional: a sub-task with no platform-write scope never invokes `infra-engineer`, and an infra-shaped but local-only sub-task (for example, editing `.env.example` or a config template checked into the repo) stays with `developer`. When you do route, name `infra-engineer` explicitly rather than attempting the command.
|
|
89
88
|
|
|
90
89
|
---
|
|
91
90
|
|
|
@@ -114,18 +113,40 @@ Follow `.github/instructions/implement.instructions.md`:
|
|
|
114
113
|
|
|
115
114
|
---
|
|
116
115
|
|
|
116
|
+
## Runbook Delivery in the Same PR (FR-49a)
|
|
117
|
+
|
|
118
|
+
A script or workflow that ships without a runbook is a procedure that
|
|
119
|
+
lives in one person's head until they leave. These **MUST** arrive with a
|
|
120
|
+
runbook in the **same draft PR**, not a follow-up issue:
|
|
121
|
+
|
|
122
|
+
- every script added or materially changed under `templates/scripts/`
|
|
123
|
+
- every workflow under `templates/workflows/` and `.github/workflows/`
|
|
124
|
+
- every `infra-engineer` change kind — secrets, deploy, DNS,
|
|
125
|
+
certificates, IAM policy, migrations
|
|
126
|
+
|
|
127
|
+
Updating an existing runbook satisfies this; a new file is required only
|
|
128
|
+
when no runbook covers the procedure. Add the new file to
|
|
129
|
+
`docs/runbooks/README.md` and to `EXPECTED_RUNBOOKS` in
|
|
130
|
+
`test/unit/runbook-set.test.ts`, or the suite fails on the undeclared
|
|
131
|
+
file — which is the reminder working, not a problem with it.
|
|
132
|
+
|
|
133
|
+
A PR that skips this is flagged by the `verifier`'s runbook-coverage
|
|
134
|
+
finding. That finding is advisory and does not block the PR; this rule
|
|
135
|
+
is what it is measuring against.
|
|
136
|
+
|
|
117
137
|
## Integration with Other Agents
|
|
118
138
|
|
|
119
|
-
| Agent | Relationship
|
|
120
|
-
| ------------------ |
|
|
121
|
-
| `product-engineer` | Produces the task lists and refined issues that `developer` executes
|
|
122
|
-
| `planner` | Orchestrates multi-story runs — delegates each story to `developer` in Execute Mode with an integration branch override
|
|
123
|
-
| `researcher` | May be invoked by `developer` for troubleshooting/diagnosis when a bug or regression is unclear; conditional, never mandatory
|
|
124
|
-
| `verifier` | Invoked by `developer` in `audit` mode, post-implementation and pre-PR-ready, mandatory and non-skippable — reports fidelity/drift; findings route to `product-engineer`'s `activity-drift-reconciliation` for remediation
|
|
125
|
-
| `qa-engineer` | Invoked by `developer` at the completion gate, before the `verifier` audit — owns the testing standard, missing test harnesses, and coverage/gap reporting; `developer` still authors feature tests under rule 19
|
|
126
|
-
| `technical-writer` | Invoked by `developer` before PR is marked ready — updates `/docs`
|
|
127
|
-
| `housekeeping` | Can be invoked during implementation for lint/type/test-wiring fixes
|
|
128
|
-
| `
|
|
139
|
+
| Agent | Relationship |
|
|
140
|
+
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
141
|
+
| `product-engineer` | Produces the task lists and refined issues that `developer` executes |
|
|
142
|
+
| `planner` | Orchestrates multi-story runs — delegates each story to `developer` in Execute Mode with an integration branch override |
|
|
143
|
+
| `researcher` | May be invoked by `developer` for troubleshooting/diagnosis when a bug or regression is unclear; conditional, never mandatory |
|
|
144
|
+
| `verifier` | Invoked by `developer` in `audit` mode, post-implementation and pre-PR-ready, mandatory and non-skippable — reports fidelity/drift; findings route to `product-engineer`'s `activity-drift-reconciliation` for remediation |
|
|
145
|
+
| `qa-engineer` | Invoked by `developer` at the completion gate, before the `verifier` audit — owns the testing standard, missing test harnesses, and coverage/gap reporting; `developer` still authors feature tests under rule 19 |
|
|
146
|
+
| `technical-writer` | Invoked by `developer` before PR is marked ready — updates `/docs` |
|
|
147
|
+
| `housekeeping` | Can be invoked during implementation for lint/type/test-wiring fixes |
|
|
148
|
+
| `infra-engineer` | Invoked conditionally when a sub-task requires a platform write (secrets, deploy, DNS, certificates, IAM policy, or cloud/shared migrations); `developer` **MUST NOT** run these commands itself and hands the sub-task off so the approval/revert/backup gates bind — never mandatory when a story has no infra scope |
|
|
149
|
+
| `github-ops` | Defines conventions for all GitHub artifacts — `developer` follows these rules |
|
|
129
150
|
|
|
130
151
|
### Codebase Research for Troubleshooting (Conditional)
|
|
131
152
|
|
|
@@ -150,6 +171,14 @@ When diagnosing a bug, regression, or unclear failure during implementation, you
|
|
|
150
171
|
|
|
151
172
|
## memo-cli Integration (When Available)
|
|
152
173
|
|
|
174
|
+
### Bank Declaration
|
|
175
|
+
|
|
176
|
+
This agent's bank id is `developer-memory`, stable for the agent's life (PRD §15). Export it before any memo command in the session:
|
|
177
|
+
|
|
178
|
+
```bash
|
|
179
|
+
export MEMO_BANK=developer-memory
|
|
180
|
+
```
|
|
181
|
+
|
|
153
182
|
### Availability Check
|
|
154
183
|
|
|
155
184
|
At the start of every execution session, check if memo-cli is configured:
|
|
@@ -163,7 +192,15 @@ which memo && memo setup validate
|
|
|
163
192
|
|
|
164
193
|
### Session Start — Restore Context
|
|
165
194
|
|
|
166
|
-
When memo is available,
|
|
195
|
+
When memo is available and `memo --version` is `1.3.0` or later, restore context with a single call:
|
|
196
|
+
|
|
197
|
+
```bash
|
|
198
|
+
memo recall "<story or issue description>" --bank $MEMO_BANK --json
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
`recall` returns one bundle — SELF, POLICIES, SHARED, MINE, LAST SESSION, CONFLICTS — in a single `<4s` call (SELF/MINE/LAST SESSION are omitted when `$MEMO_BANK` is unset or resolves to `kb`). If `memo recall` exits `2` (embeddings failure), surface the warning on stderr and continue the session without recalled context rather than blocking.
|
|
202
|
+
|
|
203
|
+
**Fallback — `memo --version` is below `1.3.0`:** run the four-command sequence instead:
|
|
167
204
|
|
|
168
205
|
```bash
|
|
169
206
|
memo list --limit 20 --json
|
|
@@ -173,7 +210,7 @@ memo search "<story or issue description>" --limit 10 --json
|
|
|
173
210
|
memo search "<key contract or dependency>" --scope related --limit 5 --json
|
|
174
211
|
```
|
|
175
212
|
|
|
176
|
-
Review results and produce a short synthesis before implementation:
|
|
213
|
+
Review results (either path) and produce a short synthesis before implementation:
|
|
177
214
|
|
|
178
215
|
- Constraints to preserve
|
|
179
216
|
- Rejected alternatives to avoid
|
|
@@ -192,10 +229,13 @@ Choose the most specific entry type:
|
|
|
192
229
|
|
|
193
230
|
### Intent Entry — Before Starting a Story
|
|
194
231
|
|
|
195
|
-
Write an intent entry **before beginning implementation** of any story or issue:
|
|
232
|
+
Write an intent entry **before beginning implementation** of any story or issue, as an episodic entry scoped to this session in this agent's bank:
|
|
196
233
|
|
|
197
234
|
```bash
|
|
198
235
|
memo write \
|
|
236
|
+
--kind episodic \
|
|
237
|
+
--session ISSUE-<n> \
|
|
238
|
+
--bank $MEMO_BANK \
|
|
199
239
|
--rationale "Context: Starting ISSUE-<##> because <trigger/need>. Decision: implement via <approach>, preserving <constraints/non-goals>, with expected files <key files>. Impact: affects <user/module/contract impact> and introduces risks <if any>." \
|
|
200
240
|
--tags "<domain>,issue-<number>,intent,<impact-tag>[,<boundary-tag>]" \
|
|
201
241
|
--entry-type decision \
|
|
@@ -207,10 +247,13 @@ memo write \
|
|
|
207
247
|
|
|
208
248
|
### Outcome Entry — After Completing a Story
|
|
209
249
|
|
|
210
|
-
Write an outcome entry as part of the **Completion Gate**, after all tests pass and before converting the PR to Ready for Review:
|
|
250
|
+
Write an outcome entry as part of the **Completion Gate**, after all tests pass and before converting the PR to Ready for Review, as an episodic entry scoped to this session in this agent's bank:
|
|
211
251
|
|
|
212
252
|
```bash
|
|
213
253
|
memo write \
|
|
254
|
+
--kind episodic \
|
|
255
|
+
--session ISSUE-<n> \
|
|
256
|
+
--bank $MEMO_BANK \
|
|
214
257
|
--rationale "Context: Completed ISSUE-<##> after implementing <scope>. Delivery: shipped <behavior>, deviations <none|details>, AC <x/y> verified. Impact: quality gates test=<pass|fail>; lint=<pass|fail>; format:check=<pass|fail>; typecheck=<pass|fail>; audit=<pass|fail>; docs=<clean|drift-fixed>; migration=<none|details>." \
|
|
215
258
|
--tags "<domain>,issue-<number>,outcome,gates-pass[,<impact-tag>][,<boundary-tag>]" \
|
|
216
259
|
--entry-type decision \
|
|
@@ -222,6 +265,14 @@ memo write \
|
|
|
222
265
|
--json
|
|
223
266
|
```
|
|
224
267
|
|
|
268
|
+
Session sequence numbers (`--seq`) auto-increment per `--session`; do not pass `--seq` explicitly unless replaying a specific position.
|
|
269
|
+
|
|
270
|
+
ADR and durable-decision entries are **not** written by `developer` — they stay `--kind semantic` in `kb`, authored by `technical-writer` with `--provenance <csv>` (citing the episodic ids that informed the decision) or `--manual`, per PRD K3.
|
|
271
|
+
|
|
272
|
+
### Session Close
|
|
273
|
+
|
|
274
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
275
|
+
|
|
225
276
|
---
|
|
226
277
|
|
|
227
278
|
## Completion Gate (Mandatory for Every Story/Issue)
|
|
@@ -237,7 +288,7 @@ Before marking a Story/Issue done:
|
|
|
237
288
|
7. `technical-writer` agent **MUST** have run and produced both a delta report and a drift/stale-doc validation result.
|
|
238
289
|
8. `/docs` **MUST** be updated to current state.
|
|
239
290
|
9. `/workstream` **SHOULD** be cleaned (active artifacts retained, obsolete artifacts archived/removed).
|
|
240
|
-
10. If memo-cli is available, outcome entry **MUST** be written to memo before PR conversion.
|
|
291
|
+
10. If memo-cli is available, an episodic outcome entry **MUST** be written to `$MEMO_BANK` (`memo write --kind episodic --session ISSUE-<n> --bank $MEMO_BANK …`) before PR conversion.
|
|
241
292
|
11. PR **MUST** be ready, approved, and merged.
|
|
242
293
|
12. You **MUST NOT** close the GitHub Issue until all conditions above are met.
|
|
243
294
|
13. For multi-story implementations, you **MUST** run a checklist cross-check between GitHub Issue tasks and `/workstream/tasks-*.md` and report any mismatch resolution.
|
|
@@ -200,6 +200,19 @@ Rules:
|
|
|
200
200
|
- The attribution value **MUST** identify the assisting system and version when available (for example, `GitHub Copilot v1`, `Claude Code v3`).
|
|
201
201
|
- The `## Why` section **MUST** reference the appropriate issue (`Closes #<number>` or `Refs #<number>`). If no issue exists, it **MUST** reference the motivating commit (`Refs <sha>`).
|
|
202
202
|
|
|
203
|
+
### Change-Record PR Shape (infra-engineer)
|
|
204
|
+
|
|
205
|
+
When `infra-engineer` delegates its change-record draft PR (S-001 AC-11), the PR **MUST** follow this shape:
|
|
206
|
+
|
|
207
|
+
- **Title prefix:** `infra:` — for example, `infra: apply <ChangeId> to <environment>`.
|
|
208
|
+
- **Label:** `infra-change`.
|
|
209
|
+
- **Body sections**, each citing the `ChangeId`:
|
|
210
|
+
- `## Change` — the `ChangeId`, target environment, and resolved identity.
|
|
211
|
+
- `## Plan` — a link or reference to the recorded `plan.md` for this `ChangeId`.
|
|
212
|
+
- `## Apply` — the applied steps (from `commands.sh`) and the `result.md` outcome.
|
|
213
|
+
- `## Revert` — the reverse-order `rollback.sh` reference and any backup id / restore command.
|
|
214
|
+
- The draft PR is opened against the default branch and stays draft until a human reviews it; `infra-engineer` never self-merges it.
|
|
215
|
+
|
|
203
216
|
### Multi-Line Body Formatting
|
|
204
217
|
|
|
205
218
|
Collapsed/mangled PR and issue bodies (headings, checklists, and paragraphs all flattened into one line) are a recurring failure mode. To prevent this, the following is **mandatory**, not a preference order:
|
|
@@ -239,18 +252,20 @@ Branch names **MUST** follow this pattern:
|
|
|
239
252
|
| ------------- | -------------------------------- | ------------------------------------- |
|
|
240
253
|
| `issue` | Single GitHub Issue | `issue/42-rate-limiting` |
|
|
241
254
|
| `story` | PRD-driven user story | `story/S-003-password-reset` |
|
|
242
|
-
| `fix` | Bug fix | `fix/87-session-expiry` |
|
|
243
|
-
| `chore` | Maintenance task | `chore/91-upgrade-node` |
|
|
244
|
-
| `docs` | Documentation only | `docs/45-api-reference` |
|
|
245
255
|
| `integration` | Multi-story consolidation branch | `integration/prd-auth-password-reset` |
|
|
246
256
|
|
|
247
257
|
Rules:
|
|
248
258
|
|
|
249
259
|
- **MUST** use lowercase and hyphens only (no underscores, no camelCase).
|
|
250
260
|
- Short description **MUST** be 2–5 words, hyphen-separated.
|
|
251
|
-
- Branches of type `issue
|
|
261
|
+
- Branches of type `issue` and `story` **MUST** include the issue or story number.
|
|
252
262
|
- Branches of type `integration` **MUST** identify the plan, PRD, or milestone being consolidated.
|
|
253
263
|
|
|
264
|
+
## Branch-Type Merge Rules
|
|
265
|
+
|
|
266
|
+
- Issue and story PRs **MUST** merge by squash with source-branch deletion. The planner merges them into an integration branch; the user merges them into `main`.
|
|
267
|
+
- Integration PRs **MUST** merge into `main` by merge commit, and only the user may merge them.
|
|
268
|
+
|
|
254
269
|
---
|
|
255
270
|
|
|
256
271
|
## Labels
|
|
@@ -318,6 +333,33 @@ Rules:
|
|
|
318
333
|
|
|
319
334
|
---
|
|
320
335
|
|
|
336
|
+
## Tags
|
|
337
|
+
|
|
338
|
+
Tags are the production deploy trigger. They **MUST** be trustworthy, so their creation is tightly constrained.
|
|
339
|
+
|
|
340
|
+
### Format
|
|
341
|
+
|
|
342
|
+
```
|
|
343
|
+
v<major>.<minor>.<patch>
|
|
344
|
+
```
|
|
345
|
+
|
|
346
|
+
Example: `v1.4.0`
|
|
347
|
+
|
|
348
|
+
Rules:
|
|
349
|
+
|
|
350
|
+
- Tags **MUST** be annotated (`git tag -a`), never lightweight.
|
|
351
|
+
- Tags **MUST** be created by a human. Agents **MUST NOT** create, move, delete, or push tags — this is enforced by `git-guard` rule 4.
|
|
352
|
+
- A tag **MUST** point at a commit on `main`.
|
|
353
|
+
- Tags **MUST** be immutable: once pushed, a tag is never moved, re-pointed, force-updated, or deleted.
|
|
354
|
+
- Prerelease tags (e.g., `v1.0.0-rc.1`, `v1.0.0-beta`) **MUST NOT** be used in v1; only exact `v<major>.<minor>.<patch>` tags are valid.
|
|
355
|
+
- A milestone `v<major>.<minor>` **MUST** be closed when its `v<major>.<minor>.0` tag exists.
|
|
356
|
+
|
|
357
|
+
### Relationship to Milestones
|
|
358
|
+
|
|
359
|
+
A milestone tracks the scope of a minor version (`vX.Y`); the tag `vX.Y.0` marks its release. Patch tags (`vX.Y.1`, `vX.Y.2`, …) do not open new milestones.
|
|
360
|
+
|
|
361
|
+
---
|
|
362
|
+
|
|
321
363
|
## Audit Mode
|
|
322
364
|
|
|
323
365
|
When invoked with `audit` as input, `github-ops` **MUST**:
|
|
@@ -29,13 +29,48 @@ Inform if any of these are missing or if you see other relevant tools (e.g. `pre
|
|
|
29
29
|
|
|
30
30
|
## What You Fix
|
|
31
31
|
|
|
32
|
-
| Domain | Fix | Never touch
|
|
33
|
-
| --------------------- | ------------------------------------------------------------------ |
|
|
34
|
-
| **Lint** | Auto-fixable errors, unused imports, formatting | Linter config files, disabling rules
|
|
35
|
-
| **Types** | Missing annotations, wrong return types, safe `any` fixes | Signatures that change runtime behavior
|
|
36
|
-
| **Unit tests** | Broken imports, wrong mock paths, outdated snapshots (re-gen only) | Assertions, test logic, coverage config
|
|
37
|
-
| **Integration tests** | Broken imports, fixture paths, env variable references | What is being tested, assertion outcomes
|
|
38
|
-
| **E2E tests** | Broken imports, selector updates after non-logic renames | Test flows, what interactions are tested
|
|
32
|
+
| Domain | Fix | Never touch |
|
|
33
|
+
| --------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
34
|
+
| **Lint** | Auto-fixable errors, unused imports, formatting | Linter config files, disabling rules |
|
|
35
|
+
| **Types** | Missing annotations, wrong return types, safe `any` fixes | Signatures that change runtime behavior |
|
|
36
|
+
| **Unit tests** | Broken imports, wrong mock paths, outdated snapshots (re-gen only) | Assertions, test logic, coverage config |
|
|
37
|
+
| **Integration tests** | Broken imports, fixture paths, env variable references | What is being tested, assertion outcomes |
|
|
38
|
+
| **E2E tests** | Broken imports, selector updates after non-logic renames | Test flows, what interactions are tested |
|
|
39
|
+
| **Infrastructure** | Nothing — never touch | `infra/`, `.github/workflows/deploy-*.yml`, `rollback.yml`, `templates/scripts/`, `templates/workflows/` — even to fix a lint or formatting error; leave them alone and route to `infra-engineer` |
|
|
40
|
+
|
|
41
|
+
## Documentation Is Not Yours
|
|
42
|
+
|
|
43
|
+
You do **not** organize documentation (FR-51). `technical-writer` owns
|
|
44
|
+
`docs/` structure and content, its indexes, and `docs/runbooks/`.
|
|
45
|
+
|
|
46
|
+
A `validate` failure from the docs-structure check — a stale index, a
|
|
47
|
+
malformed runbook, a dangling `related` entry — routes to
|
|
48
|
+
`technical-writer`, not to you. Do not fix it by editing docs, and do not
|
|
49
|
+
silence the check.
|
|
50
|
+
|
|
51
|
+
Tooling setup you _do_ own that is a repeatable procedure still needs a
|
|
52
|
+
runbook in the same PR (FR-49a); see the rule below.
|
|
53
|
+
|
|
54
|
+
## Runbook Delivery in the Same PR (FR-49a)
|
|
55
|
+
|
|
56
|
+
A script or workflow that ships without a runbook is a procedure that
|
|
57
|
+
lives in one person's head until they leave. These **MUST** arrive with a
|
|
58
|
+
runbook in the **same draft PR**, not a follow-up issue:
|
|
59
|
+
|
|
60
|
+
- every script added or materially changed under `templates/scripts/`
|
|
61
|
+
- every workflow under `templates/workflows/` and `.github/workflows/`
|
|
62
|
+
- every `infra-engineer` change kind — secrets, deploy, DNS,
|
|
63
|
+
certificates, IAM policy, migrations
|
|
64
|
+
|
|
65
|
+
Updating an existing runbook satisfies this; a new file is required only
|
|
66
|
+
when no runbook covers the procedure. Add the new file to
|
|
67
|
+
`docs/runbooks/README.md` and to `EXPECTED_RUNBOOKS` in
|
|
68
|
+
`test/unit/runbook-set.test.ts`, or the suite fails on the undeclared
|
|
69
|
+
file — which is the reminder working, not a problem with it.
|
|
70
|
+
|
|
71
|
+
A PR that skips this is flagged by the `verifier`'s runbook-coverage
|
|
72
|
+
finding. That finding is advisory and does not block the PR; this rule
|
|
73
|
+
is what it is measuring against.
|
|
39
74
|
|
|
40
75
|
## Hard Rules
|
|
41
76
|
|
|
@@ -46,6 +81,7 @@ Inform if any of these are missing or if you see other relevant tools (e.g. `pre
|
|
|
46
81
|
5. You **MUST NOT** add new dependencies without asking first.
|
|
47
82
|
6. You **MUST NOT** delete tests. Mark broken ones: `// TODO(housekeeping): escalate — [reason]`
|
|
48
83
|
7. You **MUST NOT** edit config files: `eslint.config.*`, `tsconfig*.json`, `jest.config.*`, `vite.config.*`, `playwright.config.*`, lockfiles, or `package.json` — unless a package change was explicitly confirmed.
|
|
84
|
+
8. You **MUST NOT** touch infrastructure paths — `infra/`, `.github/workflows/deploy-*.yml`, `rollback.yml`, `templates/scripts/`, `templates/workflows/` — even when a deploy workflow has a lint or formatting error. Leave the file as-is and, when a fix is warranted, route it to `infra-engineer` rather than editing it yourself.
|
|
49
85
|
|
|
50
86
|
## Decision Protocol
|
|
51
87
|
|