feat(aidd-context): support OMP project workflows

First read CONTRIBUTING.md and the issue's named entry points: plugins/aidd-context/hooks/hooks.json, hooks/update_memory.js, the tools and AI-mapping references, and scripts/dev-sync.sh and dev-setup.sh. Validate the proposal before implementation, then use the acceptance criteria to verify isolated OMP installation, session_start memory behavior, native path mappings, reload safety, and documentation boundaries.

Problem

AIDD's canonical Claude-format marketplace is consumable by OMP, but the framework has no documented OMP project contract. OMP discovers JS/TS extension factories and native project context under .omp/; AIDD's current hooks/hooks.json declares only Claude-style command hooks. The memory updater writes root CLAUDE.md/AGENTS.md and does not maintain OMP's higher-priority .omp/AGENTS.md. As a result, an OMP session can discover AIDD skills while project memory automation and generated host paths remain unsupported or misleading.

This gap affects OMP users in ordinary projects and developers running AIDD from the framework repository. The existing local .omp install is workstation state, not a portable setup contract.

Scope

• Establish direct OMP use of the existing canonical marketplace, with documented current install, update, and project-scope commands; do not create a second marketplace catalog or release archive for this contribution.
• Add an OMP-native extension factory to aidd-context that refreshes project memory on the documented session_start event using the event context's cwd and the existing update_memory.js implementation.
• Extend project-memory generation to maintain .omp/AGENTS.md as an OMP-specific target, accept omp as a tool argument, and write imports in OMP's supported @../aidd_docs/memory/... form without overwriting unrelated context content.
• Add OMP's verified project paths to the relevant context/onboard/explore and skill, rule, agent, and command generation maps. Hook generation must state that it does not generate OMP JS/TS factories rather than emitting an inert Claude JSON declaration.
• Add a reproducible local framework-repository OMP setup/reload path that uses an isolated OMP profile and the current checkout, without repointing or editing a developer's ordinary OMP marketplace/configuration.
• Update README, architecture and project memory to distinguish direct OMP marketplace/project support from aidd CLI host-target support.
• Keep OMP run-journal telemetry unsupported; do not infer mappings from Claude Stop or PostToolUse.

Acceptance criteria

• A clean isolated OMP profile can add ai-driven-dev/framework, install aidd-context at project scope, and list it as installed using documented commands.
• A real OMP session discovers and invokes an AIDD skill from the installed marketplace plugin.
• A real project-scoped install loads the OMP extension factory from the plugin package and fires it on session_start; the hook passes the OMP project cwd to the existing memory updater.
• With a valid memory block in .omp/AGENTS.md, session start refreshes memory references using OMP @ imports; a second run is byte-idempotent and unrelated file content is preserved.
• Missing aidd_docs/ or an absent/unpaired memory block cannot prevent an OMP session from starting.
• update_memory.js omp changes only .omp/AGENTS.md; existing Claude, Codex/Copilot, and unknown-tool behaviors retain regression coverage.
• Context detection and skill/rule/agent/command generation point to OMP's native documented paths. Hook generation clearly reports that OMP factories are not generated.
• The framework's local setup/reload path tests against an isolated OMP profile and the current checkout; ordinary user marketplace/configuration files remain unchanged.
• README and architecture docs state the supported surfaces, exact OMP version used for runtime evidence, and that aidd --tool omp, OMP translation/release artifacts, and telemetry are not provided by this issue.

Prior art in this repo

• CONTRIBUTING.md: issue validation must move the item to Todo before implementation.
• plugins/aidd-context/hooks/hooks.json and hooks/update_memory.js: existing Claude declaration and reusable memory implementation.
• plugins/aidd-context/skills/02-project-memory/references/tools.md and skills/11-explore/references/ai-mapping.md: existing host mapping locations.
• scripts/dev-sync.sh and scripts/dev-setup.sh: local framework reload/setup conventions.
• cli/src/contexts/tools/domain/profiles/kilo/: evidence-driven precedent for keeping an explicit per-host hook bridge separate from the canonical declarative source.
• #859: completed compatibility spike; its maintainer conclusion keeps host configuration and lifecycle adapters host-specific.
• Current workstation .omp/plugins/installed_plugins.json: project install evidence only; not a tracked framework integration.

Out of scope

• Adding omp to AiToolId, the aidd CLI tool registry, aidd translate --to omp, or the per-tool release matrix.
• Mutating a developer's ordinary/global OMP marketplace registry or configuration.
• OMP telemetry journaling, local cost ingestion, or mappings for turn_end/tool_result until those are independently captured and accepted.
• Generic Claude JSON-to-OMP hook translation or generated OMP hook modules for arbitrary user-authored hooks.
• New OMP-specific commands/agents/rules/MCP formats beyond recording their proven native locations in framework generator guidance.
• Work already owned by #733 (Kimi), #511 (Antigravity), or #916 (portable Markdown agents).

Runtime evidence collected before filing

• OMP 18.3.0: omp plugin list --json reports aidd-context@aidd-framework installed at project scope; omp plugin discover aidd-framework lists the canonical plugins.
• An active OMP 18.3.0 session from this repository ran the AIDD SDLC workflow skill.
• An isolated project hook at .omp/hooks/pre/probe.ts received { "type": "session_start" } with ctx.cwd equal to the project root at OMP startup.
• OMP's current hook docs describe turn_end as the end of each turn and tool_result as post-tool execution. No live payload was captured for either event, so neither is claimed as equivalent to Claude Stop/PostToolUse; telemetry is excluded.
• OMP docs/source checked: marketplace format and package extension loading, native .omp project paths, context-file @ imports, and typed hook events. Runtime version evidence is from omp/18.3.0.

Validation gate

This proposal is not authorization to implement. Per CONTRIBUTING.md, implementation starts only after a Certified Member or Maintainer validates the issue by moving it to Todo.