docs(adr): ADR 0027 — launch scope is the credential boundary; dir= is never a token selector #92
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/92/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Records the 2026-07-15 owner ruling as ADR 0027: the MCP server's launch scope is its credential scope, and dir= selects a repository, never a token. Exactly two enumerated crossings, both bound to the target checkout's own origin remote — contribute (the existing ADR 0019 worktree→finish flow, now named explicitly) and report (cross-repo issue filing: create/comment plus dedup reads, owner_repo pinned to the clone's origin, typed tool only). The raw API passthrough never resolves foreign credentials (why #87 is closed). Rationale recorded for future devs/agents: blast radius, scope coherence, git/API-plane symmetry, and the perishability of bug context that makes the report crossing necessary. Adds the index row.
Enforcement and the parity pin remain #90; the constrained issue-filing implementation is #59; the unauthed-launch-scope remedies are #88 (connect-time warning) and #89 (in-session OAuth login). Refs #90, #59, #88, #89.