Assimilate Oh-My-Pi 16.3.5

[a5c-ai]

Upstream version change

• Agent: Oh-My-Pi / OMP
• Previous graph version: 16.3.4
• New upstream version: 16.3.5
• Package checked: @oh-my-pi/pi-coding-agent
• Release notes: https://github.com/can1357/oh-my-pi/releases/tag/v16.3.5

Research summary

The official v16.3.5 release notes include several concrete runtime and adapter-relevant changes:

• OAuthCallbackFlow now serves GET /launch on the loopback callback server and exposes OAuthAuthInfo.launchUrl as a short copy target.
• /mcp reauth and /mcp add preserve OAuth scopes from WWW-Authenticate challenges and protected-resource metadata, fixing insufficient_scope reconnect failures.
• OpenAI-family function tool payloads preserve explicit tool.strict === false for OpenAI Responses, Codex Responses, and completions backends.
• Tool-call validation strips stray trailing line terminators from enum and identifier fields before dispatch.
• Large artifact:// reads avoid materializing full MCP/tool artifacts before selector paging.
• ACP terminal/create now wraps shell commands with the resolved shell and args instead of sending compound shell lines as command with no args.
• Additional fixes cover mnemopi retention, TypeScript LSP diagnostics outside project roots, empty task-branch cherry-picks, worker stderr diagnostics, CUDA tiny-model side runtime installs, and Windows session tail loss after compaction.

Likely affected system surfaces

• MCP OAuth adapter/proxy: launchUrl and scope propagation affect how auth prompts and reconnects should be represented.
• OpenAI/Codex tool serialization: explicit strict:false must be preserved in tool payloads rather than omitted.
• Tool-call argument normalization: parser/validator layers should tolerate and trim line terminators on enum/path/url-style fields while preserving content fields.
• MCP artifact read path: large artifact reads should remain bounded/paged to avoid OOM behavior.
• ACP terminal bridge: terminal/create launch behavior should wrap shell commands using resolved shell+args when compound shell syntax is present.
• Session storage/compaction and worker diagnostics may need regression coverage if OMP behavior is mirrored by adapters.

Migration/install notes

Install remains npm install -g @oh-my-pi/pi-coding-agent. No package rename or install-method migration was published.

Assimilation checklist

• Add AgentVersion agentVersion:omp:16-3-5 with official GitHub release evidence.
• Update MCP OAuth modeling to include OAuthAuthInfo.launchUrl and scope propagation from challenges/resource metadata.
• Check OpenAI/Codex tool serialization keeps explicit tool.strict === false.
• Add or update argument normalization coverage for enum/path/url trailing newline stripping.
• Review artifact:// read handling for bounded selector paging before full materialization.
• Review ACP terminal/create mapping for compound shell commands using resolved shell+args.
• Re-run npm run build --workspace=@a5c-ai/atlas after graph update.

[a5c-ai]

Triage Summary

• One-line: Assimilate upstream Oh-My-Pi @oh-my-pi/pi-coding-agent 16.3.5 into the Atlas agent-version graph and evidence catalog.

Critical Evaluation

• Reporter's analysis is accurate: upstream v16.3.5 exists and the repo currently has OMP graph coverage through agentVersion:omp:16-3-4, with no 16.3.5 / 16-3-5 entry.
• This is an in-scope Atlas/catalog freshness update, not a runtime outage.
• Keep implementation focused on graph/evidence assimilation unless a separate adapter gap is found in live code.

Root Cause Analysis

• Affected files likely include:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-04.yaml
  • packages/atlas/graph/catalog-meta/evidence-sources/upstream-current-2026-07-04.yaml
  • packages/atlas/graph/agent-stack/products/omp.yaml if current graph conventions require adding the new version to has_version
  • packages/atlas/src/catalog/catalog.test.ts or graph claim tests only if extra coverage is needed
• Actual root cause: Atlas has not yet recorded the latest OMP upstream release. Existing graph data includes agentVersion:omp:16-3-4; searches for 16.3.5 / 16-3-5 return no graph entry.
• Upstream evidence checked:
  • GitHub release can1357/oh-my-pi tag v16.3.5, published 2026-07-04.
  • npm metadata for @oh-my-pi/pi-coding-agent@16.3.5; latest is 16.3.5.

Affected Components

• Packages: @a5c-ai/atlas
• Components: atlas, agent-catalog
• Effort: effort:medium

Recommended Approach

• Add a new AgentVersion record for agentVersion:omp:16-3-5 with official release evidence.
• Add/extend an evidence source for the official v16.3.5 GitHub release and npm package metadata.
• Summarize the release highlights without over-porting runtime behavior:
  • OAuth launch URL and OAuth scope propagation.
  • Explicit tool.strict === false preservation for OpenAI-family tool payloads.
  • Tool-call field normalization for trailing line terminators.
  • Bounded large artifact:// reads.
  • ACP terminal/create shell wrapping behavior.
  • Mnemopi, TypeScript LSP, task-branch, worker stderr, CUDA tiny-model, and Windows compaction/session-tail fixes.
• Check whether agent:omp product edges need to include the new version under the repo's current graph conventions.
• Verify with npm run build --workspace=@a5c-ai/atlas.

Reproduction

• rg "16\\.3\\.5|16-3-5" packages/atlas/graph currently finds no OMP 16.3.5 graph record.
• gh release view v16.3.5 --repo can1357/oh-my-pi confirms upstream release notes.
• npm view @oh-my-pi/pi-coding-agent@16.3.5 version time dist-tags name --json confirms npm latest/version metadata.

Related Issues/PRs

• Related prior OMP tracking issues are older versions, not duplicates: Track Oh-My-Pi 16.3.4 upstream release #1132 for 16.3.4, Track Oh-My-Pi 16.3.0 #1115 for 16.3.0, Track Oh-My-Pi 16.2.12 #1073 for 16.2.12.
• Recent graph automation touched the same area, including 9d8fbf02f chore(graph): track upstream agent versions.

Priority

• priority:medium
• Reasoning: meaningful catalog freshness and downstream metadata impact, but no production outage or data-loss symptom.

Risk Analysis

• Risk Level: risk:medium
• Malformed graph/evidence linkage can break Atlas indexing or leave an orphan AgentVersion.
  • Mitigation: add a matching evidence node, use sourced_from, and run the Atlas build/index validation.
• Product/version discoverability gap if agent:omp edges are stale.
  • Mitigation: inspect existing OMP version conventions and update product edges only in the established style.
• Over-scoping into upstream runtime implementation instead of release assimilation.
  • Mitigation: keep this issue graph-only; open separate adapter/runtime issues only if Babysitter code has matching missing behavior.
• Release-note summarization drift.
  • Mitigation: cite official GitHub release and npm metadata in evidence; avoid claims beyond those sources.

Ready for development.