Conversation
why: The capability refactor needs a durable record of the boundary it defines and the guarantees it declines to make. what: - Add a numbered architecture decision collection - Preserve issue #127's proposed capability model and provenance - Link the collection from the contributor project page - Enforce the navigation and source-decision contract
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #130 +/- ##
=======================================
Coverage 86.91% 86.91%
=======================================
Files 46 46
Lines 3874 3874
Branches 583 583
=======================================
Hits 3367 3367
Misses 355 355
Partials 152 152 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
why: Direct-only annotations contradict MCP semantics when tmux aliases and hooks can change the whole call. what: - Define standard hints over the complete call - Keep direct-operation detail in project metadata
why: Pane input can ask tmux to start host-side jobs, so only the direct MCP schema boundary is enforceable. what: - Define the prohibited direct host-command surface - Cite run-shell and status-job escape paths
why: FastMCP visibility rejects disabled calls as well as hiding them, while pane authority remains unchanged. what: - Describe listing and invocation enforcement - Separate MCP surface control from confinement
why: Proposed decisions were phrased as shipped behavior and retained a completed documentation prerequisite. what: - Separate released toolsets from remaining target work - Pin current-surface and gp-sphinx evidence to release tags
why: Durable code citations need tagged revisions and exact line anchors. what: - Anchor the CPython regex signature - Anchor tmux's exit-empty default
why: An ADR defines the model every tmux MCP implements; release state and language-specific mechanics belong elsewhere. what: - Keep CM identifiers attached to plain-English rules - Remove Python implementation status and tooling details - Phrase guarantees and consequences across implementations
why: Ambient tmux configuration can add execution without changing the capability of the requested operation. what: - Scope process reach and tmux effect to the direct operation - State ambient execution in whole-call terms
why: Toolsets alone do not determine which tools a tmux MCP advertises and accepts. what: - Define named inclusion and exclusion precedence - Apply one frozen surface to discovery and invocation - Keep filtering distinct from pane authority
why: Removing one caller's sessions does not empty a socket that other clients also use. what: - State the complete exit-empty condition - Keep socket-wide termination with the operator
why: The decision must constrain every tmux MCP implementation without becoming a Python rollout report or requiring readers to decode internal labels. what: - Define scope, terminology, conformance, and BCP 14 requirements - Separate normative rules from rationale and implementation guidance - Record consequences, rejected alternatives, security limits, and reconsideration criteria - Keep CM identifiers attached to complete plain-English propositions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification
$ uv run ruff format . --check$ uv run ruff check .$ uv run mypy .$ uv run pytest -n 0 --reruns 0$ just build-docsTest plan
CM-*headings.exit-emptyandexit-unattachedbehavior.