fix(paseo-omp): support Paseo 0.11.1 and archived history

[omercnet]

Summary

One follow-up PR from the review of all 70 upstream commits between Paseo 0.11.0-beta.5 and 0.11.1.

• Upgrade the five exact Paseo SDK catalog pins together to 0.11.1 and regenerate the lockfile. The lockfile also synchronizes workspace versions that were already released; no package version or changelog is manually bumped.
• Move the controlled Docker canary and its client metadata to official Paseo 0.11.1. The image manifest digest was verified for both linux/amd64 and linux/arm64.
• Render the OMP profile placeholder as a code span so the registry overview sanitizer does not strip it.
• Replay archived OMP history from the authorized native journal without spawning OMP when its original working directory has been removed.

History-only boundary

The public agent.session_open hook is the trusted source of the per-launch history purpose. It strips incoming markers, sets the marker only for a host-selected history resume, and never changes stored cwd/config/persistence. The provider validates the marker and opens a read-only history controller.

History replay retains native-session/workspace identity checks, transcript ownership and symlink protections, output redaction and stable child-session IDs. It starts no OMP process or MCP connection and holds no native-session reservation. Interactive create/resume still rejects a missing cwd; restoring the directory and sending to the archived agent retires the history controller and resumes normal operation with the same opaque persistence handle.

Regression coverage includes marker spoofing, invalid replay requests, read-only operations, authorization failures, symlinked transcripts, redaction, child history, reservation coexistence and the real host hook/adapter lifecycle.

Verification

• All 12 plugins: npm run check, npm run typecheck, and their complete npm test suites passed. Existing unrelated unused-import warnings in beads/gas-city remain unchanged.
• OMP full suite: 875 passed, 7 skipped. The full conformance module was rerun after the final test-title correction: 18 passed.
• Full Docker canary on official Paseo 0.11.1, with real OMP 18.1.15 and 18.2.0: both passed. This covers health/catalog, prompts/tools, MCP, permissions, steering/interruption, persistence, nested subagents, Hub, rewind and plugin RPCs.
• Separate isolated 0.11.1 daemon + normal SDK smoke: import/archive a native journal, cold restart, remove cwd, fetch original archived history, preserve archived state and original cwd, reject interactive resume while cwd is absent, restore cwd and send successfully with unchanged persistence. The OMP process for this smoke is the deterministic existing test fixture.
• Overview rendered with the stable markdown policy: the old raw placeholder disappears; the code span preserves it.
• Independent Astra review completed with no remaining findings.

Compatibility and scope

Existing supported Paseo ranges and legacy navigation fallbacks are retained. Nightly coverage still includes 0.9, 0.10, latest and beta; the Docker canary now targets 0.11.1 rather than 0.9.2. Older-host coverage is the nightly typecheck/unit matrix, not this Docker canary.

Does not include or merge the intentionally breaking changes in #286 or #287, optional compaction-history parity, PR Radar steering changes, or new display metadata. No default/live Paseo daemon was touched. Do not merge automatically.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.