Refresh base-demo AI context for representative environment

[codeforester]

Summary

• refresh .ai-context/manifest.md so it describes the committed representative environment instead of future work
• document the current service catalog, Compose infrastructure, multi-language fixtures, React/Vite console, service dry-run contract, and expanded build targets
• reference Base's docs/tool-boundaries.md from .ai-context/overview.md so AI handoff includes the framework-level tool-boundary policy
• add validation guards so stale future-tense AI-context wording and missing tool-boundary context do not return
• pin the base-bash-libs CI checkout to the same Base v1.5.0-compatible SHA used by Base CI

Root Cause

base-demo grew into the representative environment, but the manifest AI-context note still described services, infrastructure, UI, and environment modeling as future work.

While validating the PR, the macOS GitHub Actions job also exposed a sibling dependency drift: base-demo pinned Base to v1.5.0, but left base-bash-libs floating on main. Current base-bash-libs main no longer matches Base v1.5.0's setup expectations, so the workflow now pins that checkout as well.

The latest Base docs also added the framework-level tool boundary policy, but the AI context did not point agents at that policy when interpreting base-demo's mise, uv, Compose, and AI-context examples.

Closes #162.

Validation

• ./tests/validate.sh
• git diff --check
• /Users/rameshhp/work/base/bin/basectl export-context --format markdown --print