Initial setup record — 6 October 2026
The initial repository is available privately at always-akshat/dev-environment. This page records validation of the documentation/tooling repository. It does not declare every development workflow or cloud integration complete.
What passed
Section titled “What passed”| Check | Evidence and scope |
|---|---|
| Reproducible documentation build | Clean npm ci using the pinned documentation runtime; full static build passed on Mac and in Ubuntu CI |
| Automated behavior | 13 tests: invalid contributions, model/view propagation, runtime drift, backup, idempotence, and unsafe-path protection |
| Documentation consistency | Vocabulary, metadata, evidence and entity references, model identities, script syntax, source and rendered links, fragments, iframe targets, HTML titles/language/headings |
| Human interface | Navigation and search; archive recovery page; mobile menu and no horizontal document overflow at width 390 on that page |
| Architecture | Five views generated from one model; API deep link and Fit View worked; the explanation page rendered the embedded diagram |
| Machine baselines | Mac: 7 checks passed. Shipyard: 18 passed. These are availability and drift checks, not comprehensive authentication or application tests |
The initial CI run validated commit 93634d3. Subsequent commits have their own runs in the repository’s Actions tab. Dependency follow-ups records the remaining development-tool advisory; a passing build does not mean a clean dependency audit.
What changed on Shipyard
Section titled “What changed on Shipyard”The repository was cloned to ~/code/dev-environment. The existing active installation remains ~/dev-environment.
The explicit installer updated documentation pointers generated by orca-task.py and orca-appliance.py; it also normalized a trailing blank line in config/versions.env. All nine eligible runtime files then matched the repository. This did not change Orca hook commands or restart running workloads. Existing task instructions are not rewritten retroactively; agents in existing tasks can read this repository directly.
The private backup is ~/dev-environment/state/repository-install/20261006-084551-97l7zz6a. The receipt beside it records installed hashes. Use the tooling update workflow for future changes and rollback.
Afterward, the existing API (15016/health), dashboard proxy (3003/health) and search engine (41061/) returned HTTP 200 on Shipyard loopback. These ports identify that observation, not the ports every future worktree should use. No new application acceptance test, data reseed, or production operation was needed for this documentation change.
Final synchronization limitation
Section titled “Final synchronization limitation”After the successful installation and health checks, SSH to Shipyard timed out twice on port 22. The final documentation-only fast-forward could not run. The last confirmed remote source checkout is the initial commit 93634d3; the earlier runtime update had already completed. The Mac checkout and private GitHub repository contain the full handoff.
No cause was established. Follow connectivity recovery, then check the remote checkout is clean and fast-forward it using the tooling update workflow. These remaining changes are documentation only and require no runtime installation or service restart. Do not treat the earlier health observations as a guarantee of current reachability.
Later updates
Section titled “Later updates”The device-agent contribution completed in PR #1. Its guidance is now incorporated into the contribution checklist. The record above describes the original setup, not current connection health.
For current recovery behavior, see Shipyard power recovery. Remaining work is tracked in known issues and open decisions.