content-model: frontmatter - Add operational Markdown profiles #351

Outcome

Add distinct metadata profiles for Agents, Skills, Instructions/Guidelines, Prompts, Reports, Tasks, Plans, Docs and Specs.

Verified context

TOA uses operational Markdown alongside editorial content; the reference organisation schema uses file_type, while some TOA agent/skill files use type. The reference does not provide every requested profile.

Scope

Inventory actual paths and supported discovery formats, then define TOA-specific contracts without blanket key renaming or central governance edits.

Acceptance criteria

• All nine profiles have explicit path mappings, requiredness, existing-key compatibility and examples; actual path gaps remain visible.
• Plans and Specs are distinct, including Spec Kit outputs and placeholders.
• Agent/skill discovery formats and document bodies are preserved; missing metadata is reported, never fabricated.
• Operational records cannot enter public content indexes; fixtures cover each profile and reference-schema incompatibilities.

Boundaries and sources

Creation defines work only; it does not start implementation. Preserve unrelated code, protected assets, editorial wording and existing records. Do not fabricate content, identity, media, manuscript chapters, dates or engagement data. Use approved repository-native authoring, validation, preview and publication decisions; do not provision an external CMS or database. Existing editorial verification remains with its current issues. All acceptance criteria remain unchecked until evidenced.

Repository evidence was inspected on develop at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Recheck before implementation; no build or browser tests were run for this draft. Follow repository instructions and applicable Spec Kit requirements. Paths below refer to this repository.

Sources: repository instructions, application, editorial content.

Branch instructions

• Repository: lightspeedwp/ThisOneTimeOnAcidCom
• Proposed branch: feat/frontmatter-operational-profiles
• Base: develop
• Naming policy: local guide, validator, organisation strategy.
• Pull request template: Organisation .github/PULL_REQUEST_TEMPLATE/pr_feature.md, per inspected local routing; recheck before opening a PR.
• Constraints: Preserve unrelated changes; do not force-push, merge or deploy. Complete applicable Spec Kit requirements before implementation.
• Conflicts or missing evidence: Proposed branch, not an existing branch; collision freedom is unverified. Recheck current branch routing and open governance changes, including PR automation: repo-governance - Add governance automation and validation #346. Older instructions claim branch rules are absent; the inspected local guide and executable validator establish the current convention. This draft creates no branch or pull request.