Track Oh-My-Pi 16.3.10 upstream release

[a5c-ai]

Upstream version check

• Agent: Oh-My-Pi / OMP CLI
• Previous graph version: 16.3.4
• Latest upstream version: 16.3.10
• Package checked: @oh-my-pi/pi-coding-agent
• Release notes: https://github.com/can1357/oh-my-pi/releases/tag/v16.3.10
• Package/homepage metadata: npm view @oh-my-pi/pi-coding-agent@latest returned 16.3.10, homepage https://omp.sh, repository github.com/can1357/oh-my-pi
• Published: 2026-07-06T07:52:59Z from GitHub release metadata

Release research

I checked npm latest for @oh-my-pi/pi-coding-agent and read the official GitHub v16.3.10 release notes. This supersedes the existing 16.3.6 tracking issue because upstream advanced through 16.3.10 before this daily run completed.

Real changes identified

• Empty completion handling: Ollama/Ollama Cloud EOS-only completions now retry empty stops with a single output token before the agent loop can halt silently.
• Strict tool fallback: Claude Sonnet 5 requests through feature-gated gateways such as Azure Foundry or OpenAI-compatible relays now classify strict-tool rejection and retry without strict tools, remembering the downgrade for the session.
• Model discovery: LiteLLM rich discovery now ignores unusable sentinel placeholders and continues to /v2/model/info for real models.
• TUI/subagent performance: running subagent HUD display is limited to 8 items with a summary; registry/observer updates are coalesced; nested subagent trees are capped per level; obsolete task partial-result spinner repaint loop is disabled.
• Browser cleanup: browser run-end/tab-close aborts are observed and routine teardown aborts are downgraded to log lines rather than causing unhandled rejections that exit the shared session.
• RPC/session stats: get_session_stats responses now include context-window usage so RPC clients can render context meters.
• Vision model startup: cached llama.cpp vision models refresh /props metadata before being exposed as text-only.
• IRC wake/wait: IRC-woken yielded subagents reset stale yield termination state and irc wait drains pending IRC asides before queued-interrupt aborts.
• Terminal/process cleanup: terminal restore is registered on the normal CLI fatal path; expected cleanup errors can be marked and fatal cleanup has a 10s deadline.

Likely affected system surfaces

• AgentVersion graph: add agentVersion:omp:16-3-10 with concrete retry, strict-tool fallback, TUI, browser cleanup, RPC, vision, IRC, and cleanup notes.
• Stream/tool retry handling: strict-tool rejection fallback and empty-stop retry mean adapter retry classification should account for nonfatal strict-tool downgrades and empty completion retries.
• Provider/model discovery: LiteLLM placeholder filtering and llama.cpp vision metadata refresh affect model catalog/discovery assumptions.
• TUI/session observers: high-subagent rendering and observer update coalescing may affect snapshot tests or UI event expectations.
• Browser tool lifecycle: browser teardown aborts should be treated as expected cleanup instead of fatal session errors.
• RPC clients: get_session_stats now includes context-window usage, so RPC schemas/context meter renderers should be updated if they currently drop that field.
• IRC integration: wake/wait semantics changed for yielded subagents and queued interrupts.
• Process cleanup: postmortem expected-cleanup markers and 10s cleanup deadline affect crash/exit handling assumptions.

Install/package changes

No package-name or install method migration was published. Continue to use npm install -g @oh-my-pi/pi-coding-agent for the upstream package.

Migration steps

No user migration steps were published in the release notes.

Assimilation checklist

• Add AgentVersion record agentVersion:omp:16-3-10 with evidence from the official v16.3.10 release notes.
• Review OMP retry classification: model strict-tool rejections should downgrade/retry without strict tools rather than fail the session.
• Review empty completion handling: Ollama/Ollama Cloud EOS-only empty stops should be represented as retryable before loop halt.
• Update RPC/session capability metadata for get_session_stats context-window usage.
• Review browser lifecycle handling so routine browser teardown aborts are not treated as fatal adapter errors.
• Review TUI/subagent observer assumptions for bounded HUD display and coalesced progress repaints.
• Review model discovery metadata for LiteLLM placeholder filtering and llama.cpp vision /props refresh.
• Review IRC integration notes for yielded subagent wake and irc wait pending-aside behavior.

[a5c-ai]

Triage Summary

• One-line: Track and assimilate the upstream Oh-My-Pi 16.3.10 release into Atlas AgentVersion/catalog graph metadata.

Critical Evaluation

• Reporter's analysis is accurate: upstream has advanced to 16.3.10 and the repository graph currently tops out at OMP 16.2.12.
• This is an enhancement/graph-update issue, not a runtime bug in the Oh-My-Pi adapter itself.
• The issue is in scope for Atlas/agent-catalog release tracking.

Root Cause Analysis

• Current graph data includes agentVersion:omp:16-2-12 in packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-01.yaml.
• No local 16.3.10 / 16-3-10 Atlas record, commit, closed PR, or evidence source was found.
• Upstream evidence confirms GitHub release v16.3.10 and npm latest @oh-my-pi/pi-coding-agent@16.3.10, both published on 2026-07-06.
• Catalog consumers read these records through packages/atlas/src/catalog/sdk.ts and packages/atlas/src/catalog/data.ts; tests live in packages/atlas/src/catalog/catalog.test.ts.

Affected Components

• Packages: packages/atlas, agent-catalog/catalog SDK consumers
• Graph areas: packages/atlas/graph/agent-stack/agent-versions/, packages/atlas/graph/catalog-meta/evidence-sources/, and possibly OMP capability/hook/lifecycle references if a specific projection needs to move
• Effort: effort:medium

Recommended Approach

• Add an Atlas AgentVersion/evidence update for agentVersion:omp:16-3-10 with source provenance from the GitHub v16.3.10 release and npm latest metadata.
• Capture release-note clusters in assimilationNotes / releaseHighlights: empty Ollama completion retry, strict-tool fallback, LiteLLM placeholder filtering, TUI/subagent performance bounds, browser cleanup abort handling, get_session_stats context-window usage, llama.cpp vision metadata refresh, IRC wake/wait fixes, and postmortem cleanup behavior.
• Prefer an additive graph/evidence record unless there is a specific reason to move older shared references such as hook mapping, lifecycle/session semantics, or capability support ranges.
• Add or update focused catalog tests proving the new OMP version is discoverable through listAgentVersions() / getAgentVersion().

Reproduction / Verification

• Reproduce stale graph state with: rg '16\.3\.10|16-3-10' packages/atlas
• Verify after implementation with Atlas graph validation and catalog tests, especially packages/atlas/src/catalog/catalog.test.ts.

Related Issues/PRs

• Supersedes older OMP 16.3.6 tracking work in Track Oh-My-Pi 16.3.6 upstream release #1184 for implementation planning.
• Related historical OMP trackers include Track Oh-My-Pi 16.3.5 upstream release #1177, Assimilate Oh-My-Pi 16.3.5 #1169, Track Oh-My-Pi 16.3.4 upstream release #1132, Track Oh-My-Pi 16.3.0 #1115, and Track Oh-My-Pi 16.2.12 #1073.

Priority

• priority:medium: This should be handled soon because the graph is stale for an active upstream release, but it is metadata/catalog work rather than an active production failure.

Risk Analysis

• Risk Level: risk:medium
• Source provenance drift: missing evidence records would make the update hard to audit.
  • Mitigation: add explicit GitHub release and npm metadata evidence and run graph validation.
• Over-updating shared references: changing older OMP ranges could disturb hook, lifecycle, session, or capability projections.
  • Mitigation: keep the update additive unless a specific consumer requires a projection move.
• Incomplete release-note assimilation: 16.3.10 touches AI retries, model discovery, TUI, browser cleanup, RPC stats, IRC, and cleanup behavior.
  • Mitigation: map each release-note cluster into graph metadata or a reviewer checklist.
• Parallel duplicate work with Track Oh-My-Pi 16.3.6 upstream release #1184: older OMP tracker remains open.
  • Mitigation: treat Track Oh-My-Pi 16.3.10 upstream release #1197 as the superseding tracker for 16.3.10 implementation.

Ready for development.

[a5c-ai]

Triage Summary

• One-line: Add Atlas graph/evidence coverage for the Oh-My-Pi / OMP 16.3.10 upstream release, superseding the older 16.3.6 tracker.

Critical Evaluation

• Reporter's analysis is accurate: npm/release metadata in the issue shows @oh-my-pi/pi-coding-agent advanced to 16.3.10, and the repo currently has no agentVersion:omp:16-3-10 graph/evidence record.
• This is not a runtime bug in Babysitter itself. It is stale/incomplete Atlas graph/catalog data that should be updated with source-backed release notes.
• The correct scope is additive catalog assimilation. Do not broaden into runtime adapter changes unless graph validation or existing tests expose a real consumer contract issue.

Root Cause Analysis

• Affected graph path: packages/atlas/graph/agent-stack/agent-versions/.
• Affected evidence path: packages/atlas/graph/catalog-meta/evidence-sources/.
• Related product/current metadata paths:
  • packages/atlas/graph/agent-stack/products/omp.yaml
  • packages/atlas/graph/agent-stack/versions/omp-current.yaml
• Verification/test surface:
  • packages/atlas/src/catalog/catalog.test.ts
  • packages/atlas/package.json graph/catalog validation scripts
• Actual root cause: Atlas currently records OMP exact upstream releases through agentVersion:omp:16-3-4; Track Oh-My-Pi 16.3.6 upstream release #1184 separately tracks 16.3.6, but Track Oh-My-Pi 16.3.10 upstream release #1197 supersedes that with the latest 16.3.10 release.
• Code evidence:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml contains agentVersion:omp:16-3-4 with source package @oh-my-pi/pi-coding-agent.
  • rg -n "16\.3\.10|16-3-10|agentVersion:omp:16-3-10" packages/atlas/graph found no 16.3.10 record.
  • Closed PR and commit searches found no merged 16.3.10 assimilation work.

Affected Components

• Packages: @a5c-ai/atlas; Atlas catalog / agent-catalog surface
• Labels: enhancement, atlas, agent-catalog, agent-version-update, graph-update, effort:medium, priority:medium, risk:medium
• Effort: effort:medium

Recommended Approach

Add an additive OMP 16.3.10 AgentVersion graph record with matching evidence.

Suggested implementation steps:

1. Add agentVersion:omp:16-3-10 following the existing OMP exact-version YAML pattern.
2. Add matching evidence-source metadata for the upstream release notes and npm package metadata.
3. Capture the release-impact surfaces from Track Oh-My-Pi 16.3.10 upstream release #1197:
   • empty Ollama/Ollama Cloud EOS-only completion retry behavior
   • strict-tool rejection downgrade/retry behavior
   • LiteLLM placeholder filtering and model-info discovery continuation
   • TUI/subagent HUD and observer coalescing changes
   • browser teardown/tab-close abort handling
   • get_session_stats context-window usage fields
   • llama.cpp vision model /props metadata refresh
   • IRC wake/wait yielded-subagent semantics
   • terminal/process cleanup fatal-path handling and 10s cleanup deadline
4. Treat Track Oh-My-Pi 16.3.6 upstream release #1184 as related/superseded context, not the terminal target.
5. Run Atlas validation/build checks after editing, at minimum graph validation and catalog tests used for upstream agent-version changes.

Reproduction

rg -n "16\.3\.10|16-3-10|agentVersion:omp:16-3-10" packages/atlas/graph
sed -n '179,212p' packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml
gh issue view 1197 --repo a5c-ai/babysitter --json title,body,labels,comments,assignees,state

Expected current result: no 16.3.10 AgentVersion; OMP exact records stop at 16.3.4 in committed graph data.

Related Issues/PRs

• Track Oh-My-Pi 16.3.6 upstream release #1184 tracks OMP 16.3.6 and is now superseded by this 16.3.10 tracker.
• Track Oh-My-Pi 16.3.6 upstream release #1186 was a closed duplicate for OMP 16.3.6.
• Recent related graph-update commit pattern: 9d8fbf02f chore(graph): track upstream agent versions.

Priority

priority:medium

Stale Atlas/agent-catalog metadata can mislead downstream planning and adapter assumptions, and this issue supersedes older pending OMP work. It is not an outage or data-loss issue, and the implementation should be additive, so medium priority is appropriate.

Risk Analysis

Risk Level: risk:medium

• Graph/evidence drift or unresolved sourced_from IDs
  • Mitigation: create matching EvidenceSource records, reference them from the AgentVersion, and run Atlas graph validation plus catalog tests.
• Over-scoping release-note details into runtime adapter behavior
  • Mitigation: keep implementation to source-backed graph/evidence notes unless existing validation or tests identify a real consumer contract gap.
• Implementing stale 16.3.6 work instead of the superseding 16.3.10 issue
  • Mitigation: reference Track Oh-My-Pi 16.3.6 upstream release #1184 as related/superseded and make 16.3.10 the target record.
• Consumer query gaps for the new exact OMP record
  • Mitigation: add or update focused catalog/claim coverage if the new exact record must be queryable, then run @a5c-ai/atlas validation/build checks.