architecture-view

name	architecture-view
description	Use when the user asks to open the architecture viewer, view diagrams, inspect node evidence, export the local architecture map, or troubleshoot hello-scholar map view/export behavior.

Architecture View

Mission

Open, inspect, or export the local hello-scholar architecture viewer. This skill is operational: it does not scan the repository and does not modify architecture facts.

Boundaries

• Do not modify architecture-map.json.
• Do not semantically scan code.
• Follow the native architecture boundary in ../references/native-boundaries.md; use the hello-scholar local viewer only.
• Keep the server bound to localhost through the CLI default.
• Use export only when the user asks for a portable artifact.

Load Reference

Read ../references/native-boundaries.md and references/viewer-operations.md for CLI commands, troubleshooting, and expected viewer capabilities.

Workflow

1. Check for hello-scholar/architecture/architecture-map.json.
2. If missing, tell the user to run $architecture-map or ~map after enabling architecture-onboarding.
3. If present, run or recommend:
   • hello-scholar map status
   • hello-scholar map validate
   • hello-scholar map view [--port <port>] [--open]
4. For export requests, use:
   • hello-scholar map export --format html
   • hello-scholar map export --format markdown
   • hello-scholar map export --format mermaid
5. Report the local URL, local-only boundary, validation warnings, and export path.

Viewer Expectations

The local viewer should allow the user to:

• browse project overview, run/test/build notes, evidence coverage, optional lenses, views, and flows
• render Mermaid diagrams locally
• click nodes to inspect summary, paths, evidence, confidence, and tags
• inspect edges from the edge list or rendered labels when available
• inspect numbered call sequences
• see diagnostics, unknowns, drift warnings, and weak or missing evidence claims
• search nodes, paths, and evidence
• pan, zoom, fit, and switch light/dark backgrounds
• auto-refresh when the map file changes

Troubleshooting

• If the map is missing, do not start an empty viewer.
• If Mermaid is unavailable, report that raw diagrams will still be shown.
• If the port is occupied, rely on CLI fallback or choose another port.
• If the browser shows stale UI, ask for a hard refresh after the server restarts.
• If export HTML lacks Mermaid rendering, report the fallback clearly and keep raw diagrams accessible.