Milestone entry type, board config, and review workflow
Problem
ADR-0019 established kanban flow for agent teams. ADR-0020 revised the entity model: milestone is a knowledge artifact (entry type), lanes are board configuration (YAML), review queue is a computed view (query). This item covers the entry type, extension config mechanism, and review workflow additions.
Solution
Extension config files
KBs already require specific extensions for their types (`kb_type: software` implies software-kb). Extensions can own config files in the KB root — separate from `kb.yaml` so each has its own git diff history and no namespace collisions.
For software-kb, the board config lives in `board.yaml` at the KB root:
```yaml lanes: - name: Backlog statuses: [proposed, planned] - name: Ready statuses: [accepted] - name: In Progress statuses: [in_progress] wip_limit: 5 - name: Review statuses: [review] wip_limit: 3 - name: Done statuses: [done, completed] wip_policy: warn # warn | enforce ```
The extension reads this file from the KB path when needed. No changes to core `kb.yaml` schema required.
Milestone entry type
New `milestone` entry type in software-kb extension: