Include Base's source dependencies in the canonical workspace manifest #11

Goal

Make the canonical base-workspace manifest accurately describe the repositories required to develop and validate Base on a clean Ubuntu/macOS workspace.

Background

Base source development requires sibling checkouts of base-bash-libs and base-cli. The current manifest includes base-cli but omits base-bash-libs, so basectl workspace update never visits that checkout. A stale or incompatible base-bash-libs checkout can therefore remain unnoticed until basectl test base fails.

The manifest also includes base-cli-demo and base-bash-libs-demo. These are useful first-party validation/demo repositories, but they are not required to run Base itself and should not make a fresh workspace clone fail or grow unnecessarily.

Scope

• Add base-bash-libs as a required repository.
• Preserve base-cli as a required repository.
• Keep base-cli-demo and base-bash-libs-demo in the manifest as optional repositories.
• Add repository validation that protects this required/optional dependency contract.
• Document the distinction between Base source dependencies and optional demos.

Acceptance criteria

• workspace.yaml contains required base, base-bash-libs, and base-cli entries with the expected repositories and main branch.
• workspace.yaml contains base-cli-demo and base-bash-libs-demo as optional entries.
• A validation command fails if a required dependency is removed or a demo is accidentally made required.
• The manifest remains valid YAML and the repository validation passes.
• No change is made to Base runtime dependency resolution or to the demo repositories themselves.

Validation

• ./tests/validate.sh
• git diff --check

Project fields

• Status: In Progress
• Priority: P2
• Area: Workspace
• Initiative: Adoption Polish
• Size: S

Agent assignment

Implementation and validation are assigned to the coding agent; keep the change limited to the canonical workspace manifest and its repository-owned validation/documentation.