feat(framework): delivery artefacts declare their type #650

Outcome

Every delivery artefact declares what it is, so a reader can filter on it.

Scope

Measured on this repository. Backlog artefacts are complete; delivery artefacts are mute.

One new field per file. No task_id is repeated anywhere: the folder name already is the identifier.

• Includes: the templates under plugins/aidd-pm/skills/*/assets/ and plugins/aidd-dev/skills/01-plan/assets/.
• Includes: the status vocabulary these files may use, aligned with plan-status.md rather than invented alongside it.
• Excludes: migrating documents already written.
• Excludes: any change to backlog artefacts, which are already correct.

Why this is not cosmetic

The kanban's own product brief records the consequence of the gap: "--type cannot work against this framework's own documents", because "the plan template defines objective and status only". A project whose documents carry no frontmatter reads as empty. The board cannot show what the documents do not declare.

Done When

• Each template above emits its type on creation.
• Filtering by type on a freshly generated task folder returns every artefact in it.
• No status vocabulary is introduced that plan-status.md does not already define.
• A document generated before this change still parses, and is reported as untyped rather than failing.

Completion Evidence

A generated task folder whose every artefact is listed, typed, by the board.

Relations