Author doc-approval app manifest and multi-component manifests

[enricopiovesan]

Summary

Create manifests/doc-approval/ with app manifest, component manifests, and pipeline workflow references (mirroring traverse-starter Phase 2 layout).

Why

doc-approval clients hardcode doc-approval.analyze but have no manifests in this repo. Phase 3 bundling requires manifests + WASM digests at build time.

Depends on

• Multi-capability workflow definition (doc-approval.pipeline issue)

Blocked by

• Traverse capabilities for extract + recommend

Definition of Done

• manifests/doc-approval/app.manifest.json validates with traverse-cli app validate
• Component manifests reference WASM paths + digests
• scripts/ci/phase2_link_traverse.sh extended or parallel script for doc-approval

Validation

export TRAVERSE_REPO=/path/to/Traverse
bash scripts/ci/phase2_link_traverse.sh  # or doc-approval variant
traverse-cli app validate --manifest manifests/doc-approval/app.manifest.json --json

[enricopiovesan]

Dependency correction (2026-07-12): this remains Blocked until the doc-approval pipeline artifacts are complete in Traverse #538 (extract) and #555 (recommend), after which this ticket can move to Ready.

[enricopiovesan]

Dependency correction (2026-07-14): Traverse #538 is superseded under Spec 069. This remains Blocked until Traverse #555 lands, after which canonical analyze -> recommend manifests can move to Ready.

[enricopiovesan]

Blocker update (Traverse Spec 069)

#538 closed — pipeline canonicalized to analyze → recommend (no extract).

Remaining blocker: Traverse #555. Manifests should reference Spec 069 once recommend lands.