docs(bootstrap): point the module header at createSessionLifter

[chrischall]

Auto-review follow-up for #191.

The file-level comment still described the module as one-shot-only and never mentioned createSessionLifter — so the first thing a reader sees pointed at exactly the shape that PR set out to stop being the default.

Rewritten to lead with the choice: createSessionLifter for anything whose session can expire, bootstrap for genuinely one-shot callers (the user-invoked capture_session tool pattern). Includes the why, since the failure mode is what makes the default matter — capturing a value once is how an MCP ends up working for one credential lifetime and then dying with no way back.

Docs only; 1092 tests pass, typecheck clean.

Closes #192

[claude]

Claude finished @chrischall's task in 44s —— View job

---

Review: docs(bootstrap): point the module header at createSessionLifter

• Analyzed PR context and CLAUDE.md conventions
• Reviewed the documentation changes in detail
• Verified alignment with project architecture and design
• Confirmed tests pass and no code logic was modified

---

Findings

This documentation-only PR updates the module header comment in packages/bootstrap/src/index.ts to better reflect the actual API design choices introduced in #191.

What changed:

• Removed "one-shot" from the module-level description to reflect that both bootstrap() and createSessionLifter() are now first-class entry points
• Rewrote the header to lead with the architectural choice: createSessionLifter for repeatable lifts (expiring sessions), bootstrap for one-shot callers
• Added clear motivation explaining the failure mode: capturing a session once is the most common way to build an MCP that works for one credential lifetime then silently fails with no recovery path

Quality assessment:

✅ Correctness: The documentation accurately describes the API design. The module now explicitly teaches the right pattern first—renewable lifts for session managers—with the one-shot bootstrap() positioned as the escape hatch for genuinely one-shot use cases (user-invoked capture_session tool).

✅ Adherence to conventions: Follows the project's guidance from CLAUDE.md: "Only add one [comment] when the WHY is non-obvious" — this header now explains both what the functions do and why the choice matters (the expiry dead-end failure mode).

✅ Completeness: The createSessionLifter JSDoc (lines 220–272) already covers why renewables are better; this change makes the module landing-page comment point readers there first, closing the loop described in issue #192.

✅ No breaking changes: Docs only; 1092 tests pass, typecheck clean. No code paths modified.

---

Verdict: pass

[github-actions]

✅ Auto-review verdict: pass — Documentation-only PR that correctly reframes the bootstrap module header to lead with createSessionLifter (for renewable sessions) over bootstrap() (for one-shot callers), with clear explanation of the failure modes that motivate the choice. Accurate, well-motivated, no issues.