v0.8.2 — commit only inside a git repository

Commit only inside a git repository. Tickets, smoke tests and the
helper-tool setup now work on a plain folder that holds two clones — the folder
the tutorial recommends for an existing project — instead of failing at the
first commit.

Fixed

• On a folder that is not a git repository (my-app/ holding backend/ and
  frontend/ clones), /pspt:ticket could not commit the helper-tool files
  (.mcp.json, .claude/, CLAUDE.md, AGENTS.md, .agents/), and none of
  its parent commits — the plan, the approval, each phase, the close-out — had
  anywhere to go. Found by running the real skills on such a folder.

Changed

• One rule, conventions §11:
  a commit is made in each git repository the work touched, and nowhere else.
  A package that is a repository gets its own commit. A parent that is not a
  repository gets none — tickets/, docs/, the tooling files and
  .pspt-smoke/ stay on disk, and the report says so once. No skill runs
  git init.
• A parent that is a repository commits only its own files. backend/ and
  frontend/ are staged into it only when .gitmodules registers them as
  submodules; two plain clones are left to their own repositories.
• A Committed — <sha> box in a ticket reads n/a — not a git repository when
  no repository owns that phase's files. A skipped commit never blocks a step.
• Applies to /pspt:ticket, /pspt:ticket-build, /pspt:fix-flow,
  /pspt:fix-flow-proceed, /pspt:smoke and the tool setup
  (references/prerequisites.md §3.5). /pspt:smoke adds .pspt-smoke/ to
  .git/info/exclude only where there is a repository to exclude it from.

---

Full history: CHANGELOG.md