Repository navigation
docs(rfc): accept rfc-remote-crew-sidebar - #16699
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Confirm iamwhatever actually made this acceptance, for example with a PR comment or approval. An agent opened the PR on their behalf, and the status flip is the whole change. [DESIGN-REVIEWED] 8249e02 Description read[DESCRIPTION-READ] f2f6d8159f876f88526f5ecb930e19ee7b4b4602bf5c7fe0e436120248df6f99 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Record maintainer iamwhatever's acceptance of the remote-crew sidebar RFC (option (b): the peer owns a crew session and the local dashboard is only a window, plus per-machine sidebar groups). Status moves from draft to accepted, doc-pr names #16489, the prose status line and the directory README row say so, and the decision is written under the document's Open questions with its date. Nothing is implemented on main.
b2d4294 to
8249e02
Compare
Problem / Motivation
Goal: Record maintainer iamwhatever's acceptance of
rfc-remote-crew-sidebar, so "the peer owns a crew session, the local dashboard is only a window, plus per-machine sidebar groups" is a decision on main.The RFC merged in #16489 as
status: draft. The First Principles lane reads RFC status off the base branch, anddraftis not a decision. The wave PRs that build it (per-machine sidebar groups, the window view) change what a person sees, so they need the decision on main first.Why it matters
The design is accepted. Until main says so, every implementation PR for its waves BLOCKs on "product-shape change without accepted RFC", however green its other checks are.
Not a goal
doc-pr, the audit fields and the recorded decision.What changed (motivation → approach → change)
This follows the directory's acceptance convention (as for
rfc-terminal-exit-closes-tabin #15531):docs/request-for-change/rfc-remote-crew-sidebar.md:status: draftbecomesstatus: accepted.doc-pris set to 16489, the PR that merged the document.audited-atis re-read against current main.docs/request-for-change/README.md: the table row readsaccepted("the decision, not yet the code"), and the audit log gains one sentence for the move.The main-side reading is re-verified at
f31e2f7091:remote_relay.py,useInstanceSessions.ts,ssh_tunnel_manager.py,diagnostics.pyand the other files the RFC cites are unchanged sincee698e8ca7a; the two that moved (chat_handlers.py,ChatPage.tsx) changed in code the RFC does not cite. So "nothing here is built" still holds.This PR records maintainer iamwhatever's acceptance. Opened by an agent on iamwhatever's behalf.
Backwards compatibility
Compatible: documentation only; nothing main accepts changes.
Removes nothing: only an RFC status and its index row change.
Tests
N/A, docs only.
scripts/docs-lint.shandscripts/docs_lint.py --testpass locally, and the one related test file,test/test_pr_quality_gates.py, passes.Manual verification
N/A, docs only.
Related Issues
Part of #6180. Records the decision for the RFC merged in #16489. Related: #7445, #10618, #10826, #14585.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)