DEVELOPMENT DOCUMENTATION / SUPPORT & TROUBLESHOOTING
Know the boundary before you depend on it.
Repository evidence is scoped. Development progress is not a production support commitment.
| Area | Available evidence | Still required |
|---|---|---|
| Transport | Authenticated echo, ordered rotation and retained transport replay have local evidence. | Deployment-specific acceptance and platform coverage. |
| Cluster | Private relay routing and declared local cluster gates exist. | Open failure/recovery defects; no automatic Redis HA guarantee. |
| MCP | HTTP/stdio profiles and pinned fixture interoperability. | Remaining isolation, conformance and wider protocol coverage. |
| ACP | Official client bridge conversation and scoped cluster evidence. | Full milestone acceptance, key-rotation and saturation cases. |
| Filesystem | Shared client, four adapters and scoped real-socket tests. | Broader adapter and OS acceptance. |
| Computer use | Pinned command surface, adapter and synthetic fixtures. | Real OS/backend probes and disposable desktop VM acceptance. |
| Packaging | Build from the source checkout. | Private-alpha release gate and supported installation artifacts. |
Configuration rejected
Use client config check or relay check-serve-config, not the legacy bootstrap schema checker. Check unknown fields, endpoint scheme, namespace characters and rotation timing. A dry run does not verify referenced files.
Certificate or connection failure
Run local doctor. Check the device key/certificate pairing, expiry and CA trust; verify the relay hostname and mTLS listener. Do not bypass validation or swap in test credentials.
Connected but access denied
Check the authenticated principal's tenant membership and device/service/operation grant, local export configuration and policy revision. Some inaccessible resources deliberately appear as not found rather than leaking their existence.
Interrupted operation
Distinguish not-dispatched from unknown outcome. Reconcile the application state before retrying writes, clicks or prompts. Do not treat a transport acknowledgement or HTTP 202 as completion.
Reporting a problem
Capture the source revision, platform, selected profile, redacted identifiers, phase and counters. Exclude tokens, private keys, tool payloads, screenshots of private data and user file contents.
Source & review
Reviewed against eb2422008a3a on 2026-09-22. Based on docs/tasks.md, docs/runtime.md, docs/testing.md. Historical test evidence is not a new test run.