omp's update checker skips catalog entries without a plugin-entry
version, so CE was invisible to omp plugin upgrade, the 24h catalog
refresh, and marketplace.autoUpdate. Ship .omp-plugin/marketplace.json
(omp's preferred catalog path, read ahead of the Claude copy when both
exist) with a version wired to the root release component via
extra-files jsonpath $.plugins[0].version, mirroring the existing
kimi/grok/devin native-catalog pattern. release:validate gains an omp
arm: plugin-list parity with the Claude catalog, version presence and
drift detection, and a co-located source check.
README now leads with the marketplace flow plus autoUpdate guidance
(notify mode only writes to the debug log), demoting omp install
<git-url> to pin-style and omp plugin link to contributor dev. The
target spec's causal claim is corrected: skills load via provider
scanning of the root skills/ directory; the pi manifest is the
discovery gate and an install-time validation risk, not the loader.
Split out per maintainer request (#1224): omp's session-bucket naming
is still moving (17.2.9 restored the raw scheme), so the install and
prose work here should not be blocked behind it.
omp 17.2.9 restored the legacy raw bucket naming (-<home-rel>,
-tmp-<rel>, --<abs>--) and removed automatic migration (#7646), so both
raw and hashed bucket shapes exist in the wild. Discovery globbed only
the sanitized basename, missing raw buckets whose basename contains
characters the hashed scheme normalizes (e.g. "my repo" in
--Users-test-Code-my repo--).
Add an exact raw-bucket probe for --cwd (canonicalized via physical
paths like omp's resolveEquivalentPath), a raw-basename glob alongside
the sanitized one, and awk dedup for buckets hit by both probe and
glob. Update docs/specs/omp.md for the restored naming scheme.
Address PR #1323 review feedback by updating the historian prompt's platform enum, cwd metadata, cross-tool synthesis guidance, and provenance header. Add a contract regression guard.
- deduplicate all-platform discovery output: Pi and omp share the
PI_CODING_AGENT_SESSION_DIR flat override, so both discoverers emitted
the same files (Codex review P2)
- glob omp's sanitized bucket basename ([^a-zA-Z0-9._-]+ -> "-", edge
dashes stripped, capped at the last 80 chars, empty -> "project",
mirroring session-paths.ts getDefaultSessionDirName) so repos whose
basename omp normalizes (e.g. spaces) are still discovered
- SKILL.md: include omp sessions in the mandatory keyword rerun clause —
omp session headers carry cwd but no git branch, same as Codex/Pi
- detect omp (~/.omp, project .omp/) so `--to all` reports it as a
native plugin install instead of attempting conversion; no --to omp
converter, writer, or manifest (per CONCEPTS.md native-plugin-surface)
- docs/specs/omp.md target spec verified against omp 17.2.7; README
gains omp install/local-dev/limitations coverage
- skills: omp built-in `ask` in blocking-question lists, `task` in
closed subagent enumerations, and `/skill:<name>` user-facing
invocation form across the rendering-rule copies, AGENTS.md, and the
authoring guide
- ce-compound session history: discover omp sessions under
~/.omp/agent/sessions and named-profile roots (honoring
PI_CODING_AGENT_SESSION_DIR/PI_CODING_AGENT_DIR/PI_CONFIG_DIR), detect
omp JSONL via its physical title-slot line before the pi-shaped
header, and reuse pi extraction for omp platform identity
- tests: detection, --to all note, session fixture + discovery/extract
coverage, invocation-rendering parity, and a guarded
omp-native-install smoke test
Closes#1224
Trevin Chow