Context OS workspace companion
- Identify the user's intended Context OS workspace. Ask for its path if it is not explicit or unambiguous. Never use the plugin installation/cache as a workspace, and never create a workspace or import context implicitly.
- Verify the selected root contains
AGENTS.md,ROUTING.md,scripts/contextos.sh, and.agents/skills/. If not, stop and explain the repository-native setup in the bundleddocs/codex-onboarding.md(relative to the plugin root, two directories above this file). - Read that workspace's
AGENTS.md,ROUTING.md, anddocs/safety-contract.mdcompletely. Use that workspace as the working directory. Do not mix installed-plugin code with another workspace's state. - For the operation the user requested, read its canonical
.agents/skills/context-setup/SKILL.md,context-start/SKILL.md,context-update/SKILL.md, orcontext-end/SKILL.mdin the selected workspace. Follow that file; do not substitute a plugin-local copy or infer an operation that would expand the request. - Start is read-only. Setup, update and end require a displayed proposal and explicit approval of its exact digest before apply. Never write lifecycle state directly, install hooks, or commit/push implicitly. Report receipts and verification limits. Plugin installation grants no extra authority.