feat(setup): docs preset should scaffold content.adf instead of frontend/backend

[SmartBrandStrategies]

Problem

When using charter setup --preset docs, the default manifest.adf scaffolds frontend.adf (triggers: React, CSS, UI) and backend.adf (triggers: API, Node, DB). For pure docs repos (Markdown, Astro, content schemas), neither trigger set is relevant. Migration still routes content to these modules, but the labels feel mismatched.

Source: #27 (Finding 3)

Proposed Solution

When --preset docs is used, scaffold a content.adf module instead of (or alongside) frontend.adf/backend.adf:

• Triggers: Markdown, frontmatter, content schema, Astro, MDX, docs, navigation
• Sections: Content structure conventions, frontmatter standards, doc linting rules

At minimum, adjust the trigger labels in the manifest to be docs-relevant even if the module names stay the same.

Acceptance Criteria

• charter setup --preset docs scaffolds content.adf with docs-relevant triggers
• manifest.adf trigger keywords match documentation workflows
• Existing fullstack preset behavior unchanged
• Tests cover docs preset scaffold output

Dependencies

• Related to the deleted feat/docs-preset branch work

🤖 Generated with Claude Code

[SmartBrandStrategies]

Fixed in packages/cli/src/commands/adf.ts and bootstrap.ts.

• Added CONTENT_SCAFFOLD with Markdown/MDX conventions, frontmatter constraints, and advisory rules
• Updated MANIFEST_DOCS_SCAFFOLD to include content.adf with triggers: Markdown, MDX, frontmatter, content, Astro, navigation, docs, authoring
• charter bootstrap --preset docs now scaffolds: manifest.adf, core.adf, state.adf, content.adf, decisions.adf, planning.adf