@cxi-lmai/ci-agent-platform 3.0.0 → 3.1.0

package/payload/templates/pipeline-config.template.md

@@ -76,6 +76,15 @@ TODO
 ## Suppressions
 - Path: .claude/memory/review_suppressions.md (sections: Code / Security / Migration / Performance)
 
+## Metrics Conventions
+<!-- Optional. Only needed when the project runs the metrics-snapshot job.
+     The aggregator counts post-merge defects by matching commit subjects, so
+     the patterns have to be agreed rather than guessed. Defaults below match
+     the shipped aggregator. Mark "not used" when the job is off. -->
+- Full revert of a merged change: `Reverts !<iid>`
+- Targeted fix for a defect introduced by a merged change: `Fixes regression from !<iid>`
+- Re-landing work that was reverted: `Reintroduces work from !<iid>`
+
 ## Release
 <!-- Used by the release agent. Mark "not used" if the project has no formal release flow. -->
 - Release title format: <!-- e.g. "Update to x.y.z" --> TODO
@@ -89,7 +98,8 @@ TODO
 
 ## E2E Tests
 <!-- Only for projects with a generated e2e suite. Otherwise: not used.
-     Framework, test dir, fixture import module, test-data prefix, cleanup rules, required tags.
+     Required: framework, test dir, fixture import module, test-data prefix,
+     cleanup rules, required tags, and the base URL used by generated tests.
      Also (the e2e-test-writer relies on these):
      - frontend source dirs + selector strategy (real element IDs vs test-id attributes),
      - spec-file naming/extension convention (one scenario per file),

package/payload/templates/review_suppressions.template.md

@@ -11,15 +11,70 @@
 ## Code Review Suppressions
 
 (none yet)
+<!--
+### Generated output reports a duplicate helper
+- **Pattern:** a generated file contains a helper that resembles a hand-written helper
+- **Why:** the generator owns this output and the apparent duplicate is not maintained independently
+- **Date:** 2026-08-28
+-->
+
+<!--
+### Explicit fallback differs from the usual convention
+- **Pattern:** a narrowly scoped fallback uses a documented exception to the usual convention
+- **Why:** the deviation records a deliberate compatibility decision and is reviewed with its documented context
+- **Date:** 2026-08-28
+-->
+
 
 ## Security Review Suppressions
 
 (none yet)
+<!--
+### Generated metadata includes an unused-looking field
+- **Pattern:** generated metadata declares a field that no direct source reference uses
+- **Why:** the generator requires the field for a downstream consumer, so removing it would make the output incomplete
+- **Date:** 2026-08-28
+-->
+
+<!--
+### Escaped value triggers a broad input warning
+- **Pattern:** a value is passed through a safe escaping idiom that a generic catalog flags
+- **Why:** the idiom applies the required encoding before the value reaches its destination
+- **Date:** 2026-08-28
+-->
+
 
 ## Migration Review Suppressions
 
 (none yet)
+<!--
+### Generated history includes a repeated declaration
+- **Pattern:** generated change history repeats a declaration already represented elsewhere
+- **Why:** the generator preserves both representations so independent consumers can process the history
+- **Date:** 2026-08-28
+-->
+
+<!--
+### Intentional ordering differs from the default
+- **Pattern:** a documented ordering intentionally differs from the usual sequence
+- **Why:** the exception preserves a required transition and is limited to the documented operation
+- **Date:** 2026-08-28
+-->
+
 
 ## Performance Review Suppressions
 
 (none yet)
+<!--
+### Generated lookup repeats a calculation
+- **Pattern:** generated lookup code repeats a small calculation that resembles avoidable work
+- **Why:** the generator emits the calculation to keep each generated branch independent and correct
+- **Date:** 2026-08-28
+-->
+
+<!--
+### Guarded reuse is reported as shared-state risk
+- **Pattern:** a safe reuse idiom protected by an explicit guard is flagged by a generic catalog
+- **Why:** the guard establishes the required boundary before reuse occurs
+- **Date:** 2026-08-28
+-->

package/payload/templates/spec-issue.template.md

@@ -1,6 +1,11 @@
 <!--
-  Spec template for issues intended for autonomous implementation (the ready
-  label). Fill in every mandatory section before applying the label.
+  Spec template for issues intended for autonomous implementation. Use it only
+  when requirements are settled and every mandatory section can be completed
+  unambiguously.
+
+  For early ideation or product discussion, use a feature request. For a
+  reproducible defect, use a bug report. For a documentation-only change, use
+  a docs update. Promote those to a Spec once requirements are settled.
 
   IMPORTANT: the eight section headers below (## 1. Outcome ... ## 8. Out of
   Scope) are load-bearing. The pipeline validates decomposed sub-issues against
@@ -12,6 +17,13 @@
    GitHub default .github/ISSUE_TEMPLATE/spec.md).
 -->
 
+## Spec Readiness
+
+- [ ] All mandatory sections below are filled in and unambiguous.
+- [ ] I understand that applying this project's configured ready label hands this issue to an autonomous implementation agent.
+
+---
+
 > Fill this into the issue DESCRIPTION, not a comment. The pipeline reads only the description for the spec check.
 
 ## 1. Outcome
@@ -31,9 +43,11 @@ TODO
 ## 4. Scope Envelope
 <!-- Be honest about size. One coder session handles roughly the capacity in the
      pipeline config (default ~15 files / ~600 lines). Larger work is decomposed. -->
-- Estimated files touched: TODO
-- Layers / packages affected: TODO
-- Fits in one coder session: TODO (yes / no; if no, decompose first)
+- **Estimated files touched:** TODO
+- **Packages / layers affected:** TODO
+- **Database migration required:** TODO (yes / no)
+- **User-interface changes required:** TODO (yes / no)
+- **Fits in one coder session:** TODO (yes / no; if no, decompose first)
 
 ## 5. Existing Code Anchors
 <!-- <at least one> pointer to model the implementation after: a class, a module,
@@ -43,9 +57,10 @@ TODO
 
 ## 6. Risk Flags
 <!-- Check any that apply. Each checked box may trigger a specialist reviewer and
-     changes how the coder approaches the work. -->
+     changes how the coder approaches the work. Projects add domain-specific
+     risk flags in pipeline-config.md. -->
 - [ ] Schema migration
-- [ ] Security-sensitive (auth, permissions, tenant isolation, secrets)
+- [ ] Security-sensitive (authentication, authorization, permissions, secrets)
 - [ ] Public API contract change
 - [ ] Performance-critical (hot path, large query, batch job, N+1-prone)
 
@@ -53,11 +68,28 @@ TODO
 <!-- <what will be tested> and how we will know it works. Be specific. -->
 - New tests to add: TODO
 - Existing tests that must still pass: TODO
+- Manual verification (if applicable): TODO
 
 ## 8. Out of Scope
 <!-- What this issue deliberately does NOT include. Prevents scope creep. -->
 - TODO
 
+## Open Questions
+<!-- Optional. If this section has unresolved items, keep iterating before
+     applying the configured ready label. -->
+- TODO
+
+## Decomposition Links
+<!-- Optional. Track the parent issue and any child issues created from this
+     specification. -->
+- Decomposed from: TODO
+- Decomposes into: TODO
+
+## References
+<!-- Optional. Link related issues, change requests, design documents, and
+     external resources. -->
+- TODO
+
 <!-- Dependencies (GitHub has no native issue links): to say this issue waits on
      another, write "Blocked by #N" here. The orchestrator's release poll reads
      it back and promotes the issue once #N closes. On GitLab, native issue