[markscott-ms]

Description

Part 4 of 4 of the CALM Hub extensions framework design for #3396. #3520 had all of this in one PR. It is now a stack of PRs, so that each part gets a better review.

Stack (merge in this order):

1. docs(calm-hub): propose extension runtime and security ADRs #3579 ADRs 0009–0012: runtime and security
2. docs(calm-hub): propose extension UI, CLI and MCP ADRs #3580 ADRs 0013–0014: UI, CLI and MCP
3. docs(calm-hub): propose architecture validation and store write seam ADRs #3581 ADRs 0015–0016: validation and write seam
4. docs(calm-hub): model the CALM Hub extensions design in CALM #3582 CALM architecture ← this PR

This PR models the design of ADRs 0009–0016 in CALM.

• calm-4.architecture.json is the system view.
• calm-hub-4-detail.architecture.json is the Hub detail. The Hub node in calm-4 links to it.
• Controls in both files link to the ADRs.
• calm-4 is a moment after current-moment in the timeline, with no valid-from, so it is a future state.

Merge this PR last. The control and timeline links use blob/main URLs, so they work only when all the ADRs are on main.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Code style/formatting changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements
• ✅ Test additions or updates
• 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

• CLI (cli/)
• Schema (calm/)
• CALM AI (calm-ai/)
• CALM Hub (calm-hub/)
• CALM Hub UI (calm-hub-ui/)
• CALM Lab (calm-lab/)
• CALM Models (calm-models/)
• CALM Server (calm-server/)
• CALM Studio (calm-studio/)
• CALM Widgets (calm-widgets/)
• CALMGuard (calm-guard/)
• Documentation (docs/)
• Shared (shared/)
• VS Code Extension (calm-plugins/vscode/)
• Dependencies
• CI/CD

Commit Message Format ✅

docs(calm-hub): model the CALM Hub extensions design in CALM

Testing

• I have tested my changes locally
• I have added/updated unit tests
• All existing tests pass

calm validate passes with no errors or warnings for both architectures and for the timeline. Run it from calm/architecture, because the CLI finds detailed-architecture files from the working directory.

Do not open calm-4.architecture.json in CALM Canvas 0.9.2 and save it. The canvas removes fields from it (#3518, #3519).

Checklist

• My commits follow the conventional commit format
• I have updated documentation if necessary
• I have added tests for my changes (if applicable)
• My changes follow the project's coding standards