session-initlisted

# Session Init Bootstrap the documentation structure that all other session-flow skills depend on. Open with one sentence saying what you are about to do and what it will produce. ## When to Use - First time adopting session-flow in a project - Setting up a new repository that will use session-flow skills - When other session-flow skills fail because they cannot find the docs root This is **step 0** of the session-flow chain. Run it once, then never again. ## Workflow ### Step 0: Resolve the Runtime Every record session-flow creates is written by the helper at `<package-root>/scripts/session-flow.py`. Resolve it before creating anything, by the one rule for this host (`references/runtime-integration.md`): - Native Claude plugin: the plugin root the host supplies in `${CLAUDE_PLUGIN_ROOT}`. - Codex: the discovered installed skill and package location. - Standalone copy: the `session-flow-runtime.json` descriptor beside this `SKILL.md`; resolve its `entrypoint` against the descriptor's own directory. Then confirm it answers, with absolute paths for both the interpreter and the entrypoint: ```bash python3 -B "$ENTRYPOINT" --project-root "$PROJECT_ROOT" doctor ``` Read `result.protocol`, `result.record_format`, and `result.runtime`; Step 5a binds the namespace through the same entrypoint. When the interpreter is too old, report `error.detail.install` and stop; when the descriptor, the entrypoint, or a named support file is missing, report what is missing and where it