story

# Storybloq - Project Context & Session Management storybloq tracks tickets, issues, roadmap, and handovers in a `.story/` directory so every AI coding session builds on the last instead of starting from zero. Invocation differs by client: use `/story` in Claude Code, `$story` in Codex, or ask naturally to use the Storybloq skill. **Client profile.** Resolve the profile once per invocation. `STORYBLOQ_CLIENT=codex` selects `{ id: "codex", displayName: "Codex", storyCommand: "$story" }`; unset, `claude`, or an unknown value selects `{ id: "claude", displayName: "Claude Code", storyCommand: "/story" }`. Render the resolved `storyCommand` in user-facing instructions. Capabilities such as structured questions, task navigation, exact-message relay, and subagents are separate exact-name runtime gates, not profile fields. **Client task identity.** A Codex SessionStart hook may inject `[storybloq-client-task]` with `client=codex` and an opaque `id`. Use that validated id. If the marker is absent, probe only the corresponding variable with the read-only command `printenv CODEX_THREAD_ID` or `printenv CLAUDE_CODE_SESSION_ID`; never dump the environment. IDs must match `[A-Za-z0-9][A-Za-z0-9._:-]{0,127}`. Missing or malformed identity never blocks the legacy workflow, but it cannot prove same-task ownership. Task identity is accidental-concurrency protection, not a security boundary; when identity is unavailable, guide ownership checks preserve the legacy fail-open behavior. Pass a ...