architecture-viewerlisted

# Architecture viewer 1. Inspect selection with harness integrations show architecture-viewer --json. Use an explicit invocation override only when requested. Report unavailable implementations; never silently change the selection or install an alternative. 2. Run harness integrations doctor architecture-viewer to obtain the selected adapter's actual capabilities. Missing required capabilities are errors, not evidence that a different viewer was selected. 3. Prepare an authorized immutable snapshot. For the upstream adapter use architecture-diagram profile 1, an explicit project root, optional source/metrics roots, and the SHA-256 of the exact profile bytes. Keep the profile and roots inside that project unless the user pre-authorized an additional adapter root. Preserve missing observations; report projection omissions. 4. Validate with harness viewer validate --input INPUT_JSON, then invoke harness viewer open --input INPUT_JSON. Record the returned session_reference, adapter, document identity, revision, digest, actual capabilities and mapping/evidence paths. 5. For an update, query harness viewer status --session REFERENCE, prepare a new immutable input, then use harness viewer replace-document --session REFERENCE --input REPLACEMENT_JSON --request-id REQUEST_UUID. Include the observed expected_revision. Only an acknowledged successful result means the viewer accepted the document. 6. Preserve the request ID when inspecting uncertain o