docs: update session end docs and test count

- CLAUDE.md: document session end confirmation prompt, --yes flag,
  selective staging (data/ only), update test count to 381
- CLAUDE_CHAT_SESSION_INSTRUCTIONS.md: detail session end behavior
  including file review, confirmation, selective staging, abort path

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hooman

CLAUDE.md

@@ -226,8 +226,9 @@ uv run baft session start --session-id my-run  # Start with explicit ID
 uv run baft session status                     # Show active sessions + service health
 uv run baft session sync-check                 # Check if framework remote has new commits
 uv run baft session sync                       # Pull framework + incremental DuckDB import
-uv run baft session end                        # End session (commit + push framework)
+uv run baft session end                        # End session (shows changes, confirms, commits + pushes)
 uv run baft session end -m "added new entity"  # End with commit message
+uv run baft session end --yes                  # Skip confirmation prompt
 ```
 
 ## Session CLI details
@@ -236,7 +237,7 @@ The `baft` CLI provides session lifecycle automation:
 
 - **`baft preflight`** — Validates the entire environment: Python, uv, repos, deps, env vars, NATS, Ollama, DuckDB, framework git status (10 checks)
 - **`baft session start`** — Pulls framework, runs incremental DuckDB import, checks services, registers session marker
-- **`baft session end`** — Unregisters session, commits framework changes, pushes to remote
+- **`baft session end`** — Shows changed files, asks for confirmation, commits only `data/` directory + tracked changes, pushes to remote. Use `--yes/-y` to skip confirmation
 - **`baft session status`** — Shows active sessions, framework git state, service health
 - **`baft session sync-check`** — Fetches remote, reports ahead/behind/diverged status
 - **`baft session sync`** — Fast-forward pulls framework and runs incremental DuckDB import
@@ -257,7 +258,7 @@ All configuration and infrastructure is implemented and working:
 - Telegram-to-source-bundle converter
 - Config resolution script (silo expansion, ${ITP_ROOT} substitution)
 - OpenTelemetry tracing integration (`baft.tracing` module)
-- Unit tests: 356 tests pass (workers, contracts, pipelines, DuckDB import, config resolution, new loom features)
+- Unit tests: 381 tests pass (workers, contracts, pipelines, DuckDB import, config resolution, sessions, new loom features)
 - Helm chart with 24 deployments (13 workers + infra + services), helm lint clean
 - 7 Dockerfiles for container images (worker, router, pipeline, workshop, mcp, import, commit-agent)
 - CI: docs deploy, helm lint, container image build on tag push

docs/CLAUDE_CHAT_SESSION_INSTRUCTIONS.md

@@ -33,11 +33,18 @@ When the analyst says they're done or wants to end the session:
 1. Ask: "Would you like me to commit the framework changes from this
    session? If so, please provide a brief description."
 2. Call `session.end` with their message
-3. Confirm the result:
+3. The CLI will:
+   - Show the list of changed files for review
+   - Ask for confirmation before committing (use `--yes` to skip)
+   - Commit only the `data/` directory and tracked changes (prevents
+     accidental staging of untracked files)
+   - Push to remote
+4. Confirm the result:
    - If committed + pushed: "Changes committed and pushed."
    - If committed but push failed: "Committed locally but push failed.
      Run `baft session sync-check` to diagnose."
    - If no changes: "No framework changes to commit. Session ended."
+   - If analyst cancels at confirmation: "Aborted. Session still active."
 
 ## Available tool namespaces