Repository navigation
Conversation
|
Local test evidence for head 810f0fa (rebased onto 401a14b), dev-dsk Linux, Python 3.12.14, Backend related set ( The same 17 node ids were re-run on a pristine detached worktree at the merge-base Changed-area modules ( D12 determinism proof on the 21 new/changed test ids: 20/20 runs at Static gates: |
810f0fa to
5c7f1b2
Compare
|
SAST (Semgrep) on head 5c7f1b2 is an infrastructure red, not a finding. The job failed before semgrep ran: the The previous head's one finding ( Local proof on head 5c7f1b2, same configuration as the job, semgrep 1.78.0, baseline the merge-base Changed-area tests on this head: |
UX Review (Opus 5.5, fork) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5, fork) — 🔴 BLOCKPremise-level review of First-Principles-Verdict: BLOCK product-shape change without accepted RFC: crew/member conductors now get the gateway patrol by default, a shape the base RFC explicitly excludes. Not justified as shipped
What this change shipsInventory (6 items) — 5 justifiedIntent: the patrol should read a crew/member conductor's worker reports even when the conductor arms no loop itself. This is an ADDITION framed as a FIX.
Blockers
[FIRST-PRINCIPLES-REVIEWED] efd1c7f Description read[DESCRIPTION-READ] 3553e6f44759c2752b533bffaee6c4f7aa8c5cddf4f21d13ac6280c66fc0a001 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5, fork) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS This reverses a non-goal in the RFC on the base branch ( Watch
Suggestions
[DESIGN-REVIEWED] efd1c7f Description read[DESCRIPTION-READ] d27f2a5bbb855597398057c167e344ca6dfed74e01c5c39537f83f0cde130217 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 (fork) — ✅ no blocking findingsReviewed |
GPT 6.1 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
5c7f1b2 to
4e5a08d
Compare
|
|
|
|
|
|
|
|
4e5a08d to
e0b814c
Compare
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
A conductor that binds a worker and holds no loop gets a default work-ledger patrol armed by the gateway after the bind commits. On a crew/member-mode conductor that arm never landed: the bind route knows the calling session but not the turn, so it passes no self-arm provenance, and the authorizer refused it as an outside arm with a 409. Member DM threads are the normal conductor shape, so the safety net was inert exactly where it was needed; workers reported to a ledger nobody read. The refusal exists so no outsider's instruction reaches a member's thread through a loop. The default patrol carries none: its text is the fixed PATROL_MESSAGE and it watches the slot's own ledger. So the authorizer now admits it on a crew/member slot as the gateway's own arm, a class distinct from a self-arm: pinned on content (the flag alone does not admit; the message must be the fixed text and the watch the ledger), audited under its own gateway_patrol outcome, and backed by a gateway-patrol trust entry written before the add. The fire-time guard requires the default_patrol bit, the patrol's content on the STORED row (conductor_patrol.is_patrol_loop: the fixed text and this slot's own work-ledger watch) and that trust entry together: the loop store is agent-writable and the entry names only an id and a slot, so a message rewritten under the patrol's own id is refused like any other outside text, and the fire-refusal audit says which of the three failed. The two entry kinds never vouch for each other, so the patrol's wake still cannot reset the conversation and a forged bit of either kind cannot borrow the other's record. default_patrol= is ratcheted to conductor_patrol by a tree-scanning test, like initiator_slot_key. The row pin also holds the SHAPE the patrol is armed in, because the other store fields that put text in front of the model live beside the message: gate stays True (ungated, a persisted claim is dispatched as a structured envelope), the monitor's wake_instructions stays empty (that envelope's action line) and banner stays empty (an interrupted wake restores the banner as the instruction). Because the guard pins the stored content, a message, watch or banner edit of such a patrol through monitor_update or the goal popover would commit a row the guard then refuses at every fire. The update chokepoint, handed the state by both live callers, refuses that edit on a crew/member slot (409) and names the bounds as what stays tunable and the conductor's own monitor_start as the arm that replaces the patrol; an ordinary slot keeps the edit. A digest test pins PATROL_MESSAGE so an edit to the text is made knowing what it does to patrols already stored. Closes kirodotdev#17603
069afe4 to
efd1c7f
Compare
|
Rebased |
The first version of rfc-conductor-default-patrol.md listed arming on a crew- or member-mode conductor as a non-goal, because the bind route cannot prove the turn is the session's own. Two days after it landed the patrol's owner filed kirodotdev#17603 asking for the patrol on exactly those conductors, which are the normal conductor shape; on a live gateway every refusal since 2026-09-24 was a member-mode conductor's bind. This revision records the decision kirodotdev#17603 asks for and how it is kept inside the property section 5 protects. The patrol is admitted on such a slot as the gateway's own arm, never a self-arm: pinned on its fixed text and the slot's own work-ledger watch at arm time, backed by a gateway-patrol trust entry, and re-read against the stored row at fire time, so a message rewritten in the agent-writable store is refused like any other outside text. The self-arm route the issue suggested is recorded as an alternative with the reasons it was not taken. Sections 2, 3, 4, 5, 6 and 8 change; the README row is re-audited against 950be41. The implementation is kirodotdev#18592, which rebases onto this document so its First Principles lane reads the decision from the base. Refs kirodotdev#17603
|
Withdrawn. The author accepts §2 non-goals, §5 and §6 of RFC revision #19893 ( |
|
Thank you @rubencu for the careful work on this, and for the clear write-up when you withdrew it. Closing as you asked in your comment:
The RFC revision on Your branch is kept, and you are welcome to reopen or open a new PR for the self-arm provenance route. Thanks again! |
Problem / Motivation
Goal: a crew/member-mode conductor that dispatches a worker gets the gateway's default work-ledger patrol, so its workers' reports are read even when it arms no loop itself.
After a
work_ledger_record action=bindcommits,conductor_patrol.ensure_patrolarms a defaultwatch="work-ledger"patrol when the slot holds no loop. On a crew/member conductor that arm never landed: the bind route knows the calling session but not the turn, passes noinitiator_slot_key, andautonudge_authzrefuses a blank initiator as an outside arm (409). Live gateway since 2026-09-24: 3 refusals (conductor patrol arm refused for member-kirocrew-conductor ... [status 409]), 0 arms, all on member-mode conductors.That refusal is what
docs/request-for-change/rfc-conductor-default-patrol.md(in-progress) chose as a non-goal, because the bind route cannot prove the turn is the session's own. Two days later the patrol's owner filed #17603 asking for this patrol on crew/member conductors. This PR delivers it, so it changes the shape that RFC decided; #18699 (docs only, for the owner to accept by merging) records the decision, and this PR rebases onto it once it lands so the First Principles lane reads it from the base.Why it matters
Member DM threads are the normal conductor shape, so the safety net was inert where conductors run: done items never accepted, questions and blockers unanswered, goals stalled until a person noticed.
Not a goal
reset_conversation; no change to the ordinary-slot patrol, create-only, the system-stopped re-arm or displacement; no UI.What changed (motivation → approach → change)
The crew/member refusal exists so no outsider's instruction reaches a member's thread through a loop. The default patrol carries none (fixed
PATROL_MESSAGE, the slot's own ledger), so it is admitted as a second class, pinned on content rather than on who called, and the content is re-read off the stored row before every wake.autonudge_authz.py(is_gateway_patrol):default_patrol=Trueadmits a crew/member slot only with the exactPATROL_MESSAGE, thework-ledgerwatch and no structured monitor; auditedgateway_patrol;self_armedoff.autonudge_selfarm.py: trust entries gain akind(self|gateway_patrol; none = self).record_gateway_patrolwrites beforesvc.addunder a reserved id and fails closed (503); each kind's reader answersFalsefor the other, so the wake-reset gate stays closed to the patrol.conductor_patrol.py(is_patrol_loop): the stored-row twin. The row is the patrol only withdefault_patrol is True, the fixed text, this slot's ownwork-ledgerwatch, and the shapeensure_patrolarms:gateTrue (ungated, a persisted claim dispatches a structured envelope), empty monitorwake_instructions(that envelope's action line), emptybanner(restored as the instruction after an interrupted wake): the store fields that put text in front of the model.slack/gateway.py(_dashboard_mode_admits): a crew/member slot fires adefault_patrolrow only whenis_patrol_loopholds AND the gateway-patrol entry names that loop on that slot; content first, because the entry names an id and a slot while the text lives in the agent-writableautonudge.json. The fire-refusal audit carriesdefault_patrol_bitanddefault_patrol_content.autonudge_authz.py(authorize_and_update_nudge,state=kwarg,patrol_content_fixed_refusal): amessage,watchor non-emptybanneredit of a pinned patrol would commit a row refused at every fire (its own text says "tune this loop with monitor_update"), so on a crew/member slot it is refused up front (409), naming the bounds as tunable and the conductor'smonitor_startas the arm that replaces the patrol. Both live callers passstate; ordinary slots keep the edit.monitor-architecture.mdandlearn-cron-dashboard.md: the admission, the fire-time and update rules, and what an edit toPATROL_MESSAGEdoes to stored patrols (re-arm by the conductor's own arm, or a stop plus the next bind).Backwards compatibility
Compatible: every arm admitted today is admitted unchanged (the self-arm branch runs first); the only new admission was a 409. Existing trust entries have no
kindand read as self-arms. Ordinary-slot patrols arm and fire as before, with no entry and no reserved id.Taken away:
authorize_and_update_nudgenow refusesmessage/watch/banneredits of a crew/member patrol. Its callers in the tree, both updated to passstate:src/kiro_crew/dashboard/session_directive_apply.py(_monitor_update, themonitor_updateMCP tool)src/kiro_crew/dashboard/handlers/autonudge.py(api_autonudge_update, the goal popover's PATCH)Nothing else is removed or renamed.
Tests
test/test_conductor_patrol.py: the regressiontest_member_conductor_bind_arms_the_default_patrol[crew|member](bind answerspatrol: armed, fixed message/watch, no self-arm, gateway-patrol entry,gateway_patrolaudit); the arm-time pin refuses other text or no ledger watch; an unwritable record denies 503 before the add; thedefault_patrol=AST ratchet;TestGatewayPatrolTrustEntry; the real-store row pin (ensure_patrol's row passes as stored and reloaded; amessage,gate,bannerorwake_instructionsedit inautonudge.jsonis not the patrol); thePATROL_MESSAGEsha256 pin;TestPatrolContentIsFixedOnACrewMemberSlot(message/watch/banner edits refused 409 with the row unchanged; bounds tunable; pinned values a no-op; ordinary slot and state-less caller keep the edit).test/test_autonudge_member_self_arm.py: through the real_fire_dashboard_nudge, a recorded patrol fires on crew and member; a rewritten message, an ungated row, a banner, awake_instructions, another watch, a forged bit without entry, and either kind's entry under the other's bit are refused and audited;TestTheMemberPatrolKeepsItsContentThroughMonitorUpdate: the patrol's own wake turn cannot rewrite its text throughapply_session_directive, anidle_secstune lands.test/test_autonudge_handlers_cov80.py: the PATCH route hands the app state to the chokepoint; no app,None.Manual verification
N/A — unit coverage sufficient: every path runs through its real code (the HTTP route via
aiohttpmocked requests,_fire_dashboard_nudgevia the real orchestrator, the row pin via a realAutoNudgeServiceon a temporary directory). Gates and local runs: see the evidence comments.Related Issues
Closes #17603. RFC revision: #18699.
Pattern harvest
Rule candidate: review-prompt
Pattern: a trust record that vouches an identity (id and slot) while the payload lives in a store the untrusted side can write; the admission must re-read every payload field that reaches the model against the pinned content at use time, or the record authenticates a label and delivers whatever sits under it.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)