A CPM package is an agent package consisting of an APM manifest plus a
team configuration (team-profile.yaml). The manager translates such a
package into the native config of a target harness. First target:
oh-my-opencode-slim; oh-my-pi, codex, claude and copilot are planned.
- omos/ -> corentic-package-manager/, cpm.py as CLI entry point
- new commands: cpm init [--fill] and cpm setup (guided flow with
interactive model selection from opencode.json(c))
- schema field omos_agent -> harness-neutral runtime_agent
- user mapping moved to ~/.config/cpm/model-mapping.yaml
- provenance suffix .cpm-provenance.json
- skill renamed to cpm-setup
- omos init [--fill]: create user mapping file, interactively resolve
PLACEHOLDER classes by picking from models discovered in
opencode.json(c)
- omos setup: guided flow - show profile summary, create/fill missing
mappings with explicit user choice, then render
- README quickstart updated to the two-command path
- examples/package: copy of the job-application APM package with
corentic.team-profile/v1 declaration (orchestrator, researcher,
writer, checker, notifier)
- examples/model-mapping.yaml: user-side model class mapping with
simple and extended entries
- skills/omos-setup: skill guiding users through
resolve-validate-render and activation
Deterministic translator between APM team profiles and
oh-my-opencode-slim presets. Reads team-profile.yaml, resolves
model classes against a user-local mapping table, generates
namespaced presets plus provenance. Includes check (dry-run),
merge-by-preset-id, custom agent generation from purpose fields,
and MCP availability warnings.
