docs: runtime-neutral lifecycle in architecture + one-instance prose (#376) #394

New issue

Closed

opened 2026-07-19 10:33:34 +02:00 by dries · 0 comments

dries commented

2026-07-19 10:33:34 +02:00

Owner

Parent

#388 (spec), #376. Spec "Further Notes".

What to build

Document the runtime-neutral lifecycle so the architecture doc and the one-instance-per-project prose match the shipped code.

docs/architecture.md: reflect the new internal/ocruntime package and the reshaped EnsureProjectOpencode seam (endpoint + opaque instance, Runtime abstraction) in the relevant diagram + its bullet list. Keep diagrams ~10 blocks.
Update the one-instance-per-project prose (AGENTS.md worktree section / relevant spec prose) to describe ocman-allocated ports, API health probe, persisted registry with probe-on-recovery, and restart.

Acceptance criteria

Architecture diagram + bullets show internal/ocruntime and the runtime-neutral seam.
One-instance-per-project prose describes allocated ports, /config health, probe-on-recovery, and restart.
No mention of the removed lsof-for-managed-path lifecycle as current behavior.

Blocked by

#391 (registry + recovery)
#392 (restart)
#393 (frontend caps gating)

## Parent #388 (spec), #376. Spec "Further Notes". ## What to build Document the runtime-neutral lifecycle so the architecture doc and the one-instance-per-project prose match the shipped code. - `docs/architecture.md`: reflect the new `internal/ocruntime` package and the reshaped `EnsureProjectOpencode` seam (endpoint + opaque instance, `Runtime` abstraction) in the relevant diagram + its bullet list. Keep diagrams ~10 blocks. - Update the one-instance-per-project prose (AGENTS.md worktree section / relevant spec prose) to describe ocman-allocated ports, API health probe, persisted registry with probe-on-recovery, and restart. ## Acceptance criteria - [ ] Architecture diagram + bullets show `internal/ocruntime` and the runtime-neutral seam. - [ ] One-instance-per-project prose describes allocated ports, `/config` health, probe-on-recovery, and restart. - [ ] No mention of the removed `lsof`-for-managed-path lifecycle as current behavior. ## Blocked by - #391 (registry + recovery) - #392 (restart) - #393 (frontend caps gating)