Development record

Routine prompts carry the outbound policy

specclosedspc-2609230612443069

Summary

The remainder of itd-152 that spc-45 did not deliver. spc-45 closed on 2026-09-23 with acceptance criteria 1 to 4 delivered: the scanner.ScrubOutbound primitive, its session-URL and clean-pass tests, and the shared harness-leak pattern set enforced by abcd lint's privacy rule and the record and docs lint harness_leak rule. This spec carries the one criterion that did not ship.

Scope

Acceptance criterion 5 (missing). Given an autonomous routine prompt assembled for a managed repo, when the prompt is composed, then it carries the policy that bans session URLs and harness footers in public text and mandates a post-create re-read-and-strip of every PR, issue and comment the loop creates. At closure the policy exists as the scanner.OutboundPolicy constant (internal/adapter/scanner/outbound.go:28, pinned by internal/adapter/scanner/harnessleak_test.go:228), but no routine-prompt composer embeds it; only lint findings and reports quote it.

Frontmatter

id	spc-2609230612443069
type	spec
lifecycle	closed

.abcd/development/specs/closed/spc-2609230612443069-routine-prompts-carry-the-outbound.md
open on GitHub ↗ · commit history ↗

References1

itd-152Autonomous cloud runs in sibling repos leaked harness attribution footers and a live session URL into public GitHub artifacts: the harness auto-appends a 'Generated with' footer plus a session link when a PR or issue is created, overriding the repos' Assisted-by-only attribution policy (commit messages stayed clean; the leak surface was PR bodies and issue comments, plus GitHub's public edit history retaining the pre-scrub revision). Leak shape only - no session ids reproduced here. Two remedies needed: (a) every autonomous routine prompt must ban session URLs and harness footers in public text AND mandate a post-create re-read-and-strip of every PR/issue/comment the loop creates, because the append happens outside the model's own text; (b) abcd should detect the class - session-URL and harness-footer patterns belong with the shared privacy pattern set (iss-154 family / itd-74 banlist territory) so audit and docs-lint flag them in any committed or posted text.implements

mentions1

spc-45autonomous-cloud-runs-in-sibling-repos-leaked-harness-attrib