Add external adoption decision and measurable status checkpoints (Vibe Kanban)

[jbax1899]

What changed

This PR updates project docs to fold external-pattern adoption work into practical, trackable guidance:

1. Added decision record:

   • docs/decisions/2026-03-external-pattern-adoption-context-and-tooling.md
   • Defines what we should adopt now vs later from external context/tooling patterns.
   • Replaces abstract gates with measurable acceptance criteria.

2. Updated docs index:

   • docs/README.md
   • Adds the decision record to the docs map.

3. Simplified and clarified current status doc:

   • docs/status/2026-03-13-incident-breakers-status.md
   • Keeps a short snapshot of what landed, what is still open, and what to review next.
   • Adds concrete "next review" timing and one-line context for open items.

Why

The task context was to turn broad architecture/process discussion into execution guidance that current tickets can use immediately.

These changes make the work easier to apply by:

• using measurable gates instead of vague checkpoints
• keeping status docs short and readable for day-to-day use
• making open work legible without requiring extra tracker lookups

Implementation details

• Docs-only changes; no runtime/API behavior changes.
• Acceptance gates now specify reviewer roles, required evidence, and pass/fail triggers.
• Immediate scope items are written as concrete deliverables with test/verification expectations.
• Status tracking now includes an explicit review checkpoint and clearer issue context.

This PR was written using Vibe Kanban

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new architecture decision documenting selective external-pattern adoption for context packaging and tool governance, updates the docs index to reference it, and restructures the incident-breakers status doc into a concise snapshot with landed/open items, guardrails, and validation focus.

Changes

Cohort / File(s)	Summary
Documentation Index docs/README.md	Added a Decisions entry linking to the new decision record for external-pattern adoption and context/tool governance.
Architectural Decisions docs/decisions/2026-03-external-pattern-adoption-context-and-tooling.md	New decision record: defines a versioned, serializable context package envelope and tests, canonical tool outcome taxonomy (executed, skipped, failed) with reason codes and fallback behavior, provider capability signaling with fail‑open semantics, invariants/non-goals, and concrete acceptance gates.
Status Tracking docs/status/2026-03-13-incident-breakers-status.md	Reworked layout: renamed main section to "Snapshot", split purpose, replaced prior incident/breaker breakdown with What Is Landed, What Is Open (JBA-18/19/20), added Guardrails and Validation Focus, and removed older sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Standardize tool invocation contracts and fail-open tooling metadata (Vibe Kanban) #215: Implements the same tool-invocation / ExecutionContext contract and outcome taxonomy described by the new decision doc.
• Reconcile Incident Queue State And Refresh Incident Status Note (Vibe Kanban) #208: Overlaps edits to docs/status/2026-03-13-incident-breakers-status.md and the status narrative.
• Add Runtime Capability Matrix and Reconcile Status Docs (Vibe Kanban) #219: Related documentation updates reconciling runtime/tool governance, fail-open behavior, and outcome/breaker taxonomy.

Poem

🐰 I hopped through docs at morning light,

Wrapped context tidy, gave outcomes sight,
Tools may skip, fail, or run with glee,
Guardrails set where they must be,
A rabbit stamped the doc with delight. 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title directly references the two main changes: adding an external adoption decision document and updating status checkpoints, matching the actual changeset which adds a decision record, updates the docs map, and simplifies status tracking.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vk/35f1-you-are-helping

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}