feat(framework): template override mechanism for skill templates

Start by locating the skills that read bundled assets/*-template.md files and the aidd-context:03-context-generate scaffold entry point. Trace how each template is selected, then inspect aidd-context:02-project-memory on next and seed aidd_docs/overrides/README.md. Done means all template reads use the documented project, home-directory, then bundled cascade, including empty files, while non-template files remain unchanged.

Problem

Plugins ship skills with bundled assets/*-template.md files. A team that wants its own wording has one option today: edit the template in place. Every plugin update then overwrites it or conflicts.

Scope

• Cascade, first match wins: aidd_docs/overrides/<plugin>/<skill>/<file> → ~/.aidd/overrides/<plugin>/<skill>/<file> → the bundled assets/<file>.
• An override replaces the whole file. A present file is used even when empty: presence is the selection.
• Retrofit every skill that reads a *-template.md with the cascade.
• aidd-context:03-context-generate injects the cascade when it scaffolds a new template-shipping skill.
• Seed aidd_docs/overrides/README.md so a user finds the mechanism.

Acceptance criteria

• A project override survives a plugin update, with no conflict and no re-edit.
• With no override present, every skill behaves exactly as today.
• An empty override file is honoured as an override, not ignored as blank.
• A skill scaffolded after this lands ships the cascade without the author writing it.

Out of scope

Only assets/*-template.md is overridable. Actions, references, SKILL.md and frontmatter stay frozen.

No drift detection: an override applies silently even when the bundled template changes upstream. Accepted, and worth its own issue if it bites.

Note

The original issue named aidd-context:02-project-init as the skill that seeds the override doc. That skill no longer exists — it is aidd-context:02-project-memory on next.