session-reportlisted

Update the session log for today's work. This is the report-writing half of the session lifecycle — it records what happened. No build gating and no worktree finalization. `/session-end` invokes this skill as one of its phases; you can also run it standalone to checkpoint mid-session. ## Project configuration The manifest is this skill's configuration. If `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md` does not exist, the project has not adopted the kit: say so, offer to create it, and stop. Never infer the keys and run anyway. The kit ships the template as `lifecycle-manifest.template.md`; locate the installed copy with `find ~/.claude/plugins -path '*lifecycle-kit*' -name lifecycle-manifest.template.md | head -1`. The marketplace's `ADOPTING.md` carries a repo-inspecting setup prompt. Read `.claude/lifecycle-manifest.md` first (resolve via `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md`). Where a step names a manifest key in `code font` (`log_dir`, `log_pattern`, `branch_pattern`, `docs_log_branch`, `build_commands`, `test_commands`), use that key's value. The suffix examples (`_audio`, `_api`) are illustrative. 1. Determine the session number `N` and the log filename from the branch, never by minting a new number. `/session-start` is the sole authority that mints `N` (it bakes it into the branch name at branch birth); this skill only consumes it. - Normal case, on a `branch_pattern` branch (`feature/session-<N>-<topic>` for Untype):