Skip to content

Author doc-approval app manifest and multi-component manifests #112

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedCannot proceed until blocker is resolveddocumentationImprovements or additions to documentation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions