Context
The numbered issue templates currently rely on guidance plus validator checks for type intent. There is still an open policy question about whether templates should explicitly carry deterministic type/labels frontmatter so routing is fully declarative.
Scope
- Review the current template frontmatter shape.
- Decide whether to add deterministic
type and labels metadata to the numbered templates.
- If adopted, define the canonical template-to-type map and update the validator/contracts accordingly.
Acceptance Criteria
- The repository has a documented decision on whether templates should encode deterministic type/label frontmatter.
- If the answer is yes, the mapping is explicit and enforceable.
- If the answer is no, the validator and docs explain why the heuristic-plus-guidance model is the chosen contract.
Notes
- Keep this separate from the project-field automation work.
Context
The numbered issue templates currently rely on guidance plus validator checks for type intent. There is still an open policy question about whether templates should explicitly carry deterministic
type/labelsfrontmatter so routing is fully declarative.Scope
typeandlabelsmetadata to the numbered templates.Acceptance Criteria
Notes