Known limitations and unfinished work

Operational limitations

• One dashboard preview and one browser session are shared cooperatively; there is no automatic human/agent input lock.
• Auth0 can request consent after navigation/reload; saved password login does not mean unattended authentication.
• Orca 1.4.220 CLI cannot execute the remote archive hook; use the verified desktop Delete flow.
• Browser startup after reboot is manual. Controlled AC return passed for host services; complete task restoration and off-LAN access remain untested.
• Staging restore exclusions can leave dependent image rows; the original one-off repair is not a reusable unattended sync.
• Historical analytics/ClickHouse projections are not seeded by streaming CDC.
• Bigtable image access, some runtime secrets, and local lake-api availability remain incomplete.
• Matching agent tools, skills and MCP access across machines is not complete.
• Real-camera, RTSP, GPU/media and appliance macOS workflows remain outside the tested search-engine setup.
• Home test bed: the build server’s .local name fails from another subnet; the DHCP reservation is unproven; a house power loss voids a run; the search-engine swap leaves the container’s image tag unchanged. See the test bed runbook.

Repository boundaries

The maintained scripts are curated from the working installation. A complete fresh-machine bootstrap is not yet proven. Legacy setup scripts can change global Git/shell/toolchain configuration and require review before reuse. Do not run them merely to read documentation.

Appliance lifecycle still depends on its draft application branch and test-port code change. No migration or PR closure is implied by documenting it here.

Maintenance backlog

1. Periodic staging refresh, after fail-safe restoration and active-task coordination are defined.
2. Disk review by task owner and cleanup of scratchpads, worktrees, retained volumes and caches; dry-run and retention policy first.
3. Redacted failure records, recurring-failure review, verified fixes and incorporation into repeatable setup.
4. Periodic read-only comparison of live machine facts and installed revisions with the documentation, to catch changes made outside Git. Define scope and cadence before scheduling.

No cadence, destructive cleanup or automatic remediation is enabled. The repository validator checks contributions; it is not a machine repair daemon.