1 {"at_ms":1787997941779,"kind":"MSG_OUT","payload":"error: GitHub API error 422: An error occurred while adding the sub-issue to the parent issue. Sub issue may only have one parent","peer":"doyle"} 2 {"at_ms":1787998852102,"kind":"MSG_OUT","payload":"comment 5461768445 added to BigscreenVR/spt-bs-releases#238","peer":"doyle"} 3 {"at_ms":1787998852719,"kind":"MSG_OUT","payload":"comment 5461768503 added to BigscreenVR/spt-bs-releases#239","peer":"doyle"} 4 {"at_ms":1787998854513,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#239 flags: (none)","peer":"doyle"} 5 {"at_ms":1787998862247,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#242 → greenlit (github open)\ncascaded to #237, #238, #239, #241, #235, #229","peer":"doyle"} 6 {"at_ms":1787999034530,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N \n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"deployah"} 7 {"at_ms":1788001622761,"kind":"MSG_OUT","payload":"error: bad ref '237': expected #N, repo#N, or owner/repo#N","peer":"doyle"} 8 {"at_ms":1788001655818,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#237 → acceptance (github closed, completed)","peer":"doyle"} 9 {"at_ms":1788001681632,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 10 {"at_ms":1788004650482,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#235 → acceptance (github closed, completed)","peer":"doyle"} 11 {"at_ms":1788005500256,"kind":"MSG_OUT","payload":"error: bad ref '238': expected #N, repo#N, or owner/repo#N","peer":"doyle"} 12 {"at_ms":1788005518837,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#238 → wip (github open)","peer":"doyle"} 13 {"at_ms":1788009861806,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#238 → acceptance (github closed, completed)","peer":"doyle"} 14 {"at_ms":1788013548712,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#239 → wip (github open)","peer":"doyle"} 15 {"at_ms":1788017425804,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#239 → acceptance (github closed, completed)","peer":"doyle"} 16 {"at_ms":1788026029641,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#229 → wip (github open)","peer":"doyle"} 17 {"at_ms":1788026083639,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#229 → acceptance (github closed, completed)","peer":"doyle"} 18 {"at_ms":1788026509091,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 19 {"at_ms":1788026518390,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#241 → wip (github open)","peer":"doyle"} 20 {"at_ms":1788026682567,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#242 SEMAPHORE — IO frames, signal categories, and the single-write seam\nstate: greenlit · type: ?\ngithub: open · updated 2026-08-29T10:20:55Z\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/242\n\n---\nRequester: doyle","peer":"doyle"} 21 {"at_ms":1788026695354,"kind":"MSG_OUT","payload":"{\n \"body\": \"---\\nRequester: doyle\",\n \"comments\": [],\n \"flags\": [],\n \"issue_state\": \"open\",\n \"number\": 242,\n \"ref\": \"BigscreenVR/spt-bs-releases#242\",\n \"state\": \"greenlit\",\n \"state_reason\": null,\n \"tags\": [],\n \"title\": \"SEMAPHORE — IO frames, signal categories, and the single-write seam\",\n \"type\": null,\n \"updated_at\": \"2026-08-29T10:20:55Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/242\"\n}","peer":"doyle"} 22 {"at_ms":1788028324786,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#241 → acceptance (github closed, completed)","peer":"doyle"} 23 {"at_ms":1788035369601,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#243 Residual machine-parsed emitter population: census truncation left 338 shipping token-shaped eprintln! sites unconverted (cli.rs post-line-3164 + stragglers) — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/243","peer":"doyle"} 24 {"at_ms":1788054524259,"kind":"MSG_OUT","payload":"error: bad ref '242': expected #N, repo#N, or owner/repo#N","peer":"deployah"} 25 {"at_ms":1788054531592,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"deployah"} 26 {"at_ms":1788054531648,"kind":"MSG_OUT","payload":"error: unknown milestone subcommand '242' — create, add, or remove","peer":"deployah"} 27 {"at_ms":1788054537062,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#242 SEMAPHORE — IO frames, signal categories, and the single-write seam\nstate: greenlit · type: ?\ngithub: open · updated 2026-08-29T10:20:55Z\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/242\n\n---\nRequester: doyle","peer":"deployah"} 28 {"at_ms":1788054615310,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#242 → acceptance (github closed, completed)\ncascaded to #237, #238, #239, #241, #235, #229","peer":"deployah"} 29 {"at_ms":1788054643359,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-bs-releases spt v0.66.0 (2026-08-30T01:42:43Z) — 7 Request(s) done:\n- #242 SEMAPHORE — IO frames, signal categories, and the single-write seam (late close, within grace)\n- #241 Machine-parsed diagnostic lines can tear between format fragments on shared stderr — convert all emitters to the single-write seam\n- #239 add: shell frames for endpoint boundaries\n- #238 Mid-turn agent output emits IO frames with inline payload (operator ruling 2026-08-28)\n- #237 Published manifest schema carries internal tracker codes in 33 descriptions; sweep + widen the no-internal-codes gate\n- #235 fresh-spawn double-create: wake gate falls back to CLAIM past the 2s dedup deadline, loser spawns a second session\n- #229 Optional-role absence handling is asymmetric: echo_commune absence WARNS, psyche_resume absence STRIKES\nhttps://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.66.0","peer":"deployah"} 30 {"at_ms":1788054674538,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 31 {"at_ms":1788054884870,"kind":"MSG_OUT","payload":"daemon: running (pid 45492, v0.23.0)","peer":"doyle"} 32 {"at_ms":1788054888307,"kind":"MSG_OUT","payload":"daemon: running (pid 45492, v0.23.0)","peer":"doyle"} 33 {"at_ms":1788055317203,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#244 Move current_exe_hash() off the daemon ready path — a ~10s synchronous hash per Linux boot sits inside the ONLINE window (ADR-0018 Q7 behaviour change) — state backlog, type change\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/244","peer":"doyle"} 34 {"at_ms":1788055337601,"kind":"MSG_OUT","payload":"comment 5466133205 added to BigscreenVR/spt-bs-releases#243","peer":"doyle"} 35 {"at_ms":1788055763510,"kind":"MSG_OUT","payload":"comment 5466162318 added to BigscreenVR/spt-bs-releases#243","peer":"doyle"} 36 {"at_ms":1788055826829,"kind":"MSG_OUT","payload":"#245 added to milestone BigscreenVR/spt-bs-releases#23 NOW-SIGNAL\nstate synced: #245 backlog → greenlit","peer":"doyle"} 37 {"at_ms":1788056318690,"kind":"MSG_OUT","payload":"comment 5466200195 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 38 {"at_ms":1788056494121,"kind":"MSG_OUT","payload":"error: milestone needs a subcommand: create <title> | add|remove <mref> <ref>[,<ref>…]","peer":"deployah"} 39 {"at_ms":1788056824354,"kind":"MSG_OUT","payload":"comment 5466232694 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 40 {"at_ms":1788056833650,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#246 endpoint-to-endpoint file transfer: spt send has no --file, and the proven xfer machinery is scoped to a node and the node DRIVING it — state backlog, type addition\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/246","peer":"doyle"} 41 {"at_ms":1788056861043,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#17 blocked by BigscreenVR/spt-bs-releases#246 (native dependency)","peer":"doyle"} 42 {"at_ms":1788057515028,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#247 EDGE_TRANSITIONS: endpoint-level subnet-join transitions with origin node (z joined <subnet> from <node>) — the data source does not exist — state backlog, type addition\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/247","peer":"doyle"} 43 {"at_ms":1788060338862,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#245 → acceptance (github closed, completed)","peer":"doyle"} 44 {"at_ms":1788060341523,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#18 → acceptance (github closed, completed)","peer":"doyle"} 45 {"at_ms":1788060357567,"kind":"MSG_OUT","payload":"comment 5466463321 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 46 {"at_ms":1788063900241,"kind":"MSG_OUT","payload":"comment 5466684852 added to BigscreenVR/spt-bs-releases#113","peer":"doyle"} 47 {"at_ms":1788063901715,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#113 → acceptance (github closed, completed)","peer":"doyle"} 48 {"at_ms":1788067774251,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#44 → acceptance (github closed, completed)","peer":"doyle"} 49 {"at_ms":1788067775856,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#45 → acceptance (github closed, completed)","peer":"doyle"} 50 {"at_ms":1788067788502,"kind":"MSG_OUT","payload":"comment 5466924902 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 51 {"at_ms":1788068689791,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#133 → acceptance (github closed, completed)","peer":"doyle"} 52 {"at_ms":1788068699677,"kind":"MSG_OUT","payload":"comment 5466985682 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 53 {"at_ms":1788068862313,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#254 spt-shells deprecation gate is inert on 2 of 3 session-start paths: cmd_bind and cmd_boundary resolve no manifest, so a compliance-declaring adapter still gets the legacy row — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/254","peer":"doyle"} 54 {"at_ms":1788068901507,"kind":"MSG_OUT","payload":"comment 5466998426 added to BigscreenVR/spt-bs-releases#11","peer":"doyle"} 55 {"at_ms":1788068902055,"kind":"MSG_OUT","payload":"comment 5466998473 added to BigscreenVR/spt-bs-releases#14","peer":"doyle"} 56 {"at_ms":1788068903529,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#11 → acceptance (github closed, completed)","peer":"doyle"} 57 {"at_ms":1788068904797,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#14 → acceptance (github closed, completed)","peer":"doyle"} 58 {"at_ms":1788068913292,"kind":"MSG_OUT","payload":"comment 5466999106 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 59 {"at_ms":1788069588311,"kind":"MSG_OUT","payload":"#16, #17 removed from milestone BigscreenVR/spt-bs-releases#23 NOW-SIGNAL","peer":"doyle"} 60 {"at_ms":1788069592408,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#16 → eval (github open)","peer":"doyle"} 61 {"at_ms":1788069593580,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#17 → eval (github open)","peer":"doyle"} 62 {"at_ms":1788069594226,"kind":"MSG_OUT","payload":"comment 5467039869 added to BigscreenVR/spt-bs-releases#23","peer":"doyle"} 63 {"at_ms":1788077922765,"kind":"MSG_OUT","payload":"error: bad ref '23': expected #N, repo#N, or owner/repo#N","peer":"deployah"} 64 {"at_ms":1788077943085,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#23 → acceptance (github closed, completed)\ncascaded to #11, #14, #18, #44, #45, #133, #113, #245\nskipped terminal #33 (done)","peer":"deployah"} 65 {"at_ms":1788082092778,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-bs-releases spt v0.67.0 (2026-08-30T08:36:37Z) — 9 Request(s) done:\n- #245 now-signal category: UPDATES\n- #133 add: shell adapter [hints]\n- #113 change: bring echo commune cadence in line with legacy SPT\n- #45 idea: endpoint alerts when attachments change\n- #44 add: attachment (controllers/viewers) state change channel for shells\n- #23 NOW-SIGNAL\n- #18 now-signal: SEAL_BRIEF — agent education payload on sealed messages\n- #14 idea: **endpoints** extension of the `[[hints]]` injection CLI for endpoint names\n- #11 major idea: `spt api now-signal [--user-input-json <msg-json>] [--agent-output-json <msgs-json>]`\nhttps://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.67.0","peer":"doyle"} 66 {"at_ms":1788250432951,"kind":"MSG_OUT","payload":"[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered","peer":"perri"} 67 {"at_ms":1788667904268,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"perri"} 68 {"at_ms":1788667925840,"kind":"MSG_OUT","payload":"error: GitHub API error 404: Not Found","peer":"perri"} 69 {"at_ms":1788669358526,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-progress-tool#80 tag scanner scans on io frames (USER_INPUT / AGENT_OUTPUT close) instead of waiting for the tick — state backlog, type feature\nhttps://github.com/BigscreenVR/spt-progress-tool/issues/80","peer":"flynn"} 70 {"at_ms":1788669396662,"kind":"MSG_OUT","payload":"comment 5556927484 added to BigscreenVR/spt-progress-tool#80","peer":"flynn"} 71 {"at_ms":1788669634480,"kind":"MSG_OUT","payload":"comment 5556945871 added to BigscreenVR/spt-progress-tool#80","peer":"flynn"} 72 {"at_ms":1788672629567,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"deployah"} 73 {"at_ms":1788672735743,"kind":"MSG_OUT","payload":"error: body is 1979 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"deployah"} 74 {"at_ms":1788672751162,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#274 docs: publish the [service] manifest section on the docs site — state backlog, type addition\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/274","peer":"deployah"} 75 {"at_ms":1788672774273,"kind":"MSG_OUT","payload":"comment 5557210530 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 76 {"at_ms":1788672776304,"kind":"MSG_OUT","payload":"DISPATCH from deployah via alchemy (BigscreenVR/spt-bs-releases): Request #274 'docs: publish the [service] manifest section on the docs site' (type addition).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/274\nDispatch note: docs-only patch lane, operator-directed 2026-09-06; driver = deployah\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #274' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"deployah"} 77 {"at_ms":1788672776356,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#274 → dispatched to deployah (github open)\npush to deployah: accepted","peer":"deployah"} 78 {"at_ms":1788673084343,"kind":"MSG_OUT","payload":"error: GitHub API error 404: Not Found","peer":"perri"} 79 {"at_ms":1788673108128,"kind":"MSG_OUT","payload":"error: unknown flag --limit","peer":"perri"} 80 {"at_ms":1788673138158,"kind":"MSG_OUT","payload":"[\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 15,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"add: manifest [hints]\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T09:43:58Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-pacer-tool/issues/15\"\n }\n]","peer":"perri"} 81 {"at_ms":1788673262327,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#275 type: ADDITION","peer":"deployah"} 82 {"at_ms":1788673294429,"kind":"MSG_OUT","payload":"comment 5557248719 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 83 {"at_ms":1788673937739,"kind":"MSG_OUT","payload":"comment 5557293796 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 84 {"at_ms":1788676528673,"kind":"MSG_OUT","payload":"BigscreenVR/spt-progress-tool#79 flags: (none)","peer":"flynn"} 85 {"at_ms":1788676548705,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-progress-tool: 1 reconciled\n#79 add: manifest [hints] (backlog → acceptance)","peer":"flynn"} 86 {"at_ms":1788676595845,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-progress-tool alchemy v0.24.0 (2026-09-06T06:36:22Z) — 1 Request(s) done:\n- #79 add: manifest [hints]\nhttps://github.com/BigscreenVR/spt-progress-tool/releases/tag/v0.24.0","peer":"flynn"} 87 {"at_ms":1788676634796,"kind":"MSG_OUT","payload":"daemon: running (pid 43872, v0.24.0)","peer":"flynn"} 88 {"at_ms":1788676651011,"kind":"MSG_OUT","payload":"comment 5557500218 added to BigscreenVR/spt-progress-tool#79","peer":"flynn"} 89 {"at_ms":1788677028512,"kind":"MSG_OUT","payload":"comment 5557530228 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 90 {"at_ms":1788677668684,"kind":"MSG_OUT","payload":"comment 5557579980 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 91 {"at_ms":1788677910284,"kind":"MSG_OUT","payload":"comment 5557597758 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 92 {"at_ms":1788677967195,"kind":"MSG_OUT","payload":"comment 5557602073 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 93 {"at_ms":1788679545840,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 94 {"at_ms":1788681835390,"kind":"MSG_OUT","payload":"comment 5557910586 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 95 {"at_ms":1788681839920,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 96 {"at_ms":1788681895753,"kind":"MSG_OUT","payload":"error: body is 3353 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 97 {"at_ms":1788681939338,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#276 echo-commune host overwrites an agent's unread authored commune drop: one path, two writers, no arbitration — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/276","peer":"doyle"} 98 {"at_ms":1788681972546,"kind":"MSG_OUT","payload":"comment 5557922092 added to BigscreenVR/spt-bs-releases#276","peer":"doyle"} 99 {"at_ms":1788682637868,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 100 {"at_ms":1788682818871,"kind":"MSG_OUT","payload":"file '276-comment.txt' staged (1741 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 101 {"at_ms":1788682822448,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #276 'echo-commune host overwrites an agent's unread authored commune drop: one path, two writers, no arbitration' (type bugfix).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/276\nDispatch note: lane brief: spt-core root ECHO-DIRECT-ROUTE-276-JIT.md — operator-ruled 2026-09-06, land after v0.67.1 on main\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #276' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 102 {"at_ms":1788682822501,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#276 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 103 {"at_ms":1788682849286,"kind":"MSG_OUT","payload":"comment 5557994262 added to BigscreenVR/spt-bs-releases#276","peer":"doyle"} 104 {"at_ms":1788683951980,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 105 {"at_ms":1788684003116,"kind":"MSG_OUT","payload":"comment 5558090003 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 106 {"at_ms":1788684054172,"kind":"MSG_OUT","payload":"file 'iolog-create-payload.txt' staged (1544 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 107 {"at_ms":1788684101987,"kind":"MSG_OUT","payload":"file 'iolog-body-only.txt' staged (1382 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 108 {"at_ms":1788684102123,"kind":"MSG_OUT","payload":"error: body is 2920 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 109 {"at_ms":1788684127071,"kind":"MSG_OUT","payload":"error: body is 3758 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 110 {"at_ms":1788684154071,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#277 io-events seq restarts at 1 once a log passes 256KB: --after cursors go blind or replay old COMMUNE frames (wake markers refire) — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/277","peer":"doyle"} 111 {"at_ms":1788684174238,"kind":"MSG_OUT","payload":"file 'iolog-277-comment.txt' staged (2041 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 112 {"at_ms":1788684188684,"kind":"MSG_OUT","payload":"comment 5558105715 added to BigscreenVR/spt-bs-releases#277","peer":"doyle"} 113 {"at_ms":1788685157303,"kind":"MSG_OUT","payload":"comment 5558184375 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 114 {"at_ms":1788685660959,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#278 adapter update never prunes strings/: files the new archive dropped stay installed (flat-layout skills beside SKILL.md dirs, a foreign claude-spt.exe) — state backlog, type change\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/278","peer":"doyle"} 115 {"at_ms":1788685686777,"kind":"MSG_OUT","payload":"comment 5558229657 added to BigscreenVR/spt-bs-releases#278","peer":"doyle"} 116 {"at_ms":1788687034446,"kind":"MSG_OUT","payload":"comment 5558341020 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 117 {"at_ms":1788687689432,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#271 → shelved (github open)","peer":"doyle"} 118 {"at_ms":1788687892242,"kind":"MSG_OUT","payload":"comment 5558410252 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 119 {"at_ms":1788688076443,"kind":"MSG_OUT","payload":"comment 5558425100 added to BigscreenVR/spt-bs-releases#278","peer":"doyle"} 120 {"at_ms":1788688160849,"kind":"MSG_OUT","payload":"comment 5558431818 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 121 {"at_ms":1788689539531,"kind":"MSG_OUT","payload":"comment 5558541811 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 122 {"at_ms":1788689765765,"kind":"MSG_OUT","payload":"comment 5558560333 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 123 {"at_ms":1788690036001,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#279 api bind prints ER_HOSTED_PROBE:no-row on every bind on a node without an engine room — a diagnostic that decides nothing reads as the refusal — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/279","peer":"doyle"} 124 {"at_ms":1788690167749,"kind":"MSG_OUT","payload":"{\n \"body\": \"Includes all the major spt-core requests related to webserving, fileserving, and file transfer. Needs a grill session to fully flesh out.\\n\\n---\\nRequester: discord:134589140258914304\",\n \"comments\": [\n {\n \"author\": \"SaberMage\",\n \"body\": \"**Grill round 1 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q1 AGREE (unified node-prefixed URL namespace). Q2 AGREE (registry as the primitive) + REQUIRED: a filename disambiguation plan — adopted shape: `<stem>~<n>.<ext>` when the bare name is taken, first registrant keeps the bare name, `n` persisted per entry, freed names never reused, same absolute path re-registers to the same entry, `--as <name>` override, `spt serve list` prints path -> URL. Q3 UNSURE — premise measured (below). Q4 AGREE (`--attachment` pull + `spt fetch`). Q5 AGREE (`spt serve lan --bootstrap`, loopback ruling stands). Q6 AGREE with all: ride #248 #249 #246 #265 #268 #147; defer #148; #17 closing rider; **#271 -> SHELVED** (done 09:41Z).\\n\\n**Q3 measurement (main 8a21a3b0):** initiator side TRUE — `fetch_file`/`push_file` have zero production callers (tests only), no CLI verb opens the Xfer stream; `spt shell send --file` uses the progress record locally, not the surface. Serve side LIVE — `serve_xfer` gates the inbound Xfer stream on the XFER surface (xfer.rs:270/:341, dispatch.rs:1161); knock codes and rules can name it; zero grant rows name it on this node. CONTEXT.md:876 already ratifies that webservice facets MINT their ids; :949 names XFER as the next surface to grow a sender stamp. Recommendation, operator to confirm: mint `WEB`, and RETIRE XFER (stream family + gate + tests + row, with `ACCESS_SURFACE_RETIRED` reported for any stored rule) as a #246 close rider — same end state as repurposing, no id changes meaning under existing rules, the superseded code leaves the tree.\\n\\nRound 2 (Q7-Q12: URL sub-namespaces + index page, reference-vs-snapshot + attachment TTL, no-cache owner-checked proxy, #147 short-ID format/verbs, http-only scheme, separate bootstrap port) at spt-core root WEBSERVE-272-GRILL-ROUND-2.md.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-06T09:44:51Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"**Grill round 2 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q3 AGREE with the recommendation → mint `WEB` (default-allow within subnet), RETIRE `XFER` as a #246 close rider, retired-surface rules reported at load (ADR-0060). Q7 AGREE → five sub-namespaces under `/<node>/` (`f/`, `docs/`, `a/<adapter>/`, `m/<short-id>`, `bin/`+`install`) + an index page at `/<node>/` (ADR-0056 amended). Q8 MOSTLY → reference for `serve add`, snapshot for attachments; attachment TTL default **30 days** (operator-set, not 7) (ADR-0058 amended). Q9 AGREE → no-cache proxy, owner-side WEB check under the proven origin, 502 naming the node. Q10 AGREE → 8-char base32 node-scoped short-ID, `spt msg show`, `spt send --reply-to`, id in envelope + io-events (ADR-0061). Q11 AGREE → http only, no `spt://`. Q12 MOSTLY → separate listener + separate allowlist; port **5470** (operator-chosen; measured: IANA `apsolab-col`, same obscure family as 5474 `apsolab-rpc`; 5471-5473 unassigned; free on hfenduleam; no popular-software claim found — Wikipedia port list fetch truncated, unchecked) (ADR-0059 amended).\\n\\nDocs branch `docs/webserve-272-grill` (spt-bs-core, off main, held until v0.67.1 lands): ADR-0056..0061 + CONTEXT.md `## Web serving` (10 terms) + access-surface entry amended. Frontier is EMPTY: no open design question remains; next = wave map + REQ ids at intake.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-06T10:16:05Z\"\n }\n ],\n \"flags\": [\n \"needs-operator\"\n ],\n \"issue_state\": \"open\",\n \"number\": 272,\n \"ref\": \"BigscreenVR/spt-bs-releases#272\",\n \"state\": \"backlog\",\n \"state_reason\": null,\n \"tags\": [],\n \"title\": \"WEBSERVE\",\n \"type\": null,\n \"updated_at\": \"2026-09-06T10:16:05Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/272\"\n}","peer":"doyle"} 125 {"at_ms":1788690261860,"kind":"MSG_OUT","payload":"error: #272 cannot enter greenlit while `flag: NEEDS-OPERATOR` is set — the Operator discussion must clear the flag first","peer":"doyle"} 126 {"at_ms":1788690264358,"kind":"MSG_OUT","payload":"#148 removed from milestone BigscreenVR/spt-bs-releases#272 WEBSERVE","peer":"doyle"} 127 {"at_ms":1788690265051,"kind":"MSG_OUT","payload":"comment 5558601225 added to BigscreenVR/spt-bs-releases#148","peer":"doyle"} 128 {"at_ms":1788690296154,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#272 flags: (none)","peer":"doyle"} 129 {"at_ms":1788690296798,"kind":"MSG_OUT","payload":"error: milestone #272 greenlight refused — `flag: NEEDS-OPERATOR` is set on:\n#147 idea: per-msg short ID + `spt endpoint msg <short-id> [--endpoint <id>[@<node>]] [--popup] [--json]`\n#246 endpoint-to-endpoint file transfer: spt send has no --file, and the proven xfer machinery is scoped to a node and the node DRIVING it\n#248 feature: generalized fileserving\n#249 feature: cross-node webserving\n#265 idea: spt-core to offer static adapter docs hosting\n#266 add: spt-core daemon to host installation packages and binaries\nthe Operator discussion must clear the flag(s) first","peer":"doyle"} 130 {"at_ms":1788690298389,"kind":"MSG_OUT","payload":"comment 5558603795 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 131 {"at_ms":1788690307397,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #248 'feature: generalized fileserving' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/248\nDispatch note: WEBSERVE W0 (substrate): brief = spt-core root WEBSERVE-272-JIT.md §W0; design = ADR-0056/0057/0060 + CONTEXT.md Web serving (branch docs/webserve-272-grill); base off main after v0.67.1 lands, store work may start now\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #248' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 132 {"at_ms":1788690307558,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#248 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 133 {"at_ms":1788690320158,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#147 flags: (none)","peer":"doyle"} 134 {"at_ms":1788690322299,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#246 flags: (none)","peer":"doyle"} 135 {"at_ms":1788690324721,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#248 flags: (none)","peer":"doyle"} 136 {"at_ms":1788690326995,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#249 flags: (none)","peer":"doyle"} 137 {"at_ms":1788690328367,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#265 flags: (none)","peer":"doyle"} 138 {"at_ms":1788690329993,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#266 flags: (none)","peer":"doyle"} 139 {"at_ms":1788690338195,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#272 → greenlit (github open)\ncascaded to #147, #246, #248, #249, #265, #266, #268, #17\nskipped terminal #271 (shelved)","peer":"doyle"} 140 {"at_ms":1788691352821,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 141 {"at_ms":1788691389047,"kind":"MSG_OUT","payload":"error: body is 2178 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 142 {"at_ms":1788691407959,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#280 io-events: MSG_IN is never published on the `api listen` relay delivery edge (only the hook-poll drain stamps it) — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/280","peer":"doyle"} 143 {"at_ms":1788691424600,"kind":"MSG_OUT","payload":"comment 5558693022 added to BigscreenVR/spt-bs-releases#280","peer":"doyle"} 144 {"at_ms":1788691612430,"kind":"MSG_OUT","payload":"comment 5558707853 added to BigscreenVR/spt-bs-releases#277","peer":"doyle"} 145 {"at_ms":1788692206452,"kind":"MSG_OUT","payload":"comment 5558754418 added to BigscreenVR/spt-bs-releases#17","peer":"doyle"} 146 {"at_ms":1788692439959,"kind":"MSG_OUT","payload":"comment 5558772826 added to BigscreenVR/spt-bs-releases#17","peer":"doyle"} 147 {"at_ms":1788693260050,"kind":"MSG_OUT","payload":"comment 5558839964 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 148 {"at_ms":1788693270693,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#274 → acceptance (github closed, completed)","peer":"deployah"} 149 {"at_ms":1788694283602,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state","peer":"deployah"} 150 {"at_ms":1788694285915,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-bs-releases spt v0.67.1 (2026-09-06T11:30:58Z) — 1 Request(s) done:\n- #274 docs: publish the [service] manifest section on the docs site\nhttps://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.67.1","peer":"deployah"} 151 {"at_ms":1788694335708,"kind":"MSG_OUT","payload":"comment 5558928159 added to BigscreenVR/spt-bs-releases#274","peer":"deployah"} 152 {"at_ms":1788704851510,"kind":"MSG_OUT","payload":"[tag] sweep BigscreenVR/spt-bs-releases: 3 reconciled\n#279 api bind prints ER_HOSTED_PROBE:no-row on every bind on a node without an engine room — a diagnostic that decides nothing reads as the refusal (backlog → acceptance)\n#277 io-events seq restarts at 1 once a log passes 256KB: --after cursors go blind or replay old COMMUNE frames (wake markers refire) (backlog → acceptance)\n#276 echo-commune host overwrites an agent's unread authored commune drop: one path, two writers, no arbitration (wip → acceptance)","peer":"doyle"} 153 {"at_ms":1788704855862,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state","peer":"doyle"} 154 {"at_ms":1788708305356,"kind":"MSG_OUT","payload":"error: bad ref '248': expected #N, repo#N, or owner/repo#N","peer":"doyle"} 155 {"at_ms":1788708320694,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #248 'feature: generalized fileserving' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/248\nDispatch note: WEBSERVE W0 serving substrate (JIT WEBSERVE-272-JIT.md §W0)\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #248' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 156 {"at_ms":1788708320749,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#248 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 157 {"at_ms":1788709562092,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: 1 reconciled\n#280 io-events: MSG_IN is never published on the `api listen` relay delivery edge (only the hook-poll drain stamps it) (backlog → acceptance)","peer":"doyle"} 158 {"at_ms":1788740847055,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 159 {"at_ms":1788740989726,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: 1 reconciled\n#248 feature: generalized fileserving (wip → acceptance)","peer":"doyle"} 160 {"at_ms":1788740992197,"kind":"MSG_OUT","payload":"error: unknown flag --no-fail-fast;","peer":"doyle"} 161 {"at_ms":1788741018369,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #249 'feature: cross-node webserving' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/249\nDispatch note: W1 cross-node per WEBSERVE-272-JIT.md section W1 (REQ-WEB-CROSS-NODE-PROXY: StreamFamily::Web, owner-side access_check under the handshake-proven origin, no cache, Range pass-through, 502/403/404 naming node/surface/name; twohost int kitsubito to hfenduleam; docs serving/cross-node.md plus the WEB row text). W0 landed on main at c33dc521; branch off it. Thin-lane PR, Fixes releases#249 only; driver template = W0's (nextest never fail-fast); hand me the sha when CI is green.\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #249' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 162 {"at_ms":1788741018774,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#249 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 163 {"at_ms":1788748861399,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #246 'endpoint-to-endpoint file transfer: spt send has no --file, and the proven xfer machinery is scoped to a node and the node DRIVING it' (type addition).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/246\nDispatch note: W2 attachments lane, base build/ws272-w1 at 8d980fdf, targeted lane battery per JIT standing rule, brief sent by spt\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #246' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 164 {"at_ms":1788748863414,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #147 'idea: per-msg short ID + `spt endpoint msg <short-id> [--endpoint <id>[@<node>]] [--popup] [--json]`' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/147\nDispatch note: W2 message short-ID half, rides the same build/ws272-w2 lane as #246\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #147' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 165 {"at_ms":1788748863797,"kind":"MSG_OUT","payload":"[tag] BigscreenVR/spt-bs-releases#246 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 166 {"at_ms":1788748863938,"kind":"MSG_OUT","payload":"[tag] BigscreenVR/spt-bs-releases#147 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 167 {"at_ms":1788753241979,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: 1 reconciled\n#249 feature: cross-node webserving (wip → acceptance)","peer":"doyle"} 168 {"at_ms":1788760901336,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 169 {"at_ms":1788760994546,"kind":"MSG_OUT","payload":"file 'alchemy-prune.txt' staged (1618 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 170 {"at_ms":1788761117093,"kind":"MSG_OUT","payload":"file 'alchemy-prune-body.txt' staged (2565 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 171 {"at_ms":1788761119511,"kind":"MSG_OUT","payload":"error: body is 4183 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 172 {"at_ms":1788761149983,"kind":"MSG_OUT","payload":"file 'alchemy-prune-body.txt' staged (2565 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 173 {"at_ms":1788761151309,"kind":"MSG_OUT","payload":"error: body is 7765 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 174 {"at_ms":1788761176905,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#281 registry snapshot is write-only for the daemon: prune rows return from memory, a restart forgets peer endpoints until gossip — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/281","peer":"doyle"} 175 {"at_ms":1788761907750,"kind":"MSG_OUT","payload":"comment 5565935597 added to BigscreenVR/spt-bs-releases#281","peer":"doyle"} 176 {"at_ms":1788762145335,"kind":"MSG_OUT","payload":"comment 5565976382 added to BigscreenVR/spt-bs-releases#281","peer":"doyle"} 177 {"at_ms":1788762199771,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#282 served URLs are minted from the configured docs port, not the port the listener bound: under the rig switch they point at the live fleet daemon — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/282","peer":"doyle"} 178 {"at_ms":1788778272007,"kind":"MSG_OUT","payload":"[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered","peer":"doyle"} 179 {"at_ms":1788778288925,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 180 {"at_ms":1788778457278,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 181 {"at_ms":1788778874147,"kind":"MSG_OUT","payload":"error: body is 1949 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 182 {"at_ms":1788778874664,"kind":"MSG_OUT","payload":"error: body is 1670 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 183 {"at_ms":1788778922782,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#285 broker.rs zombie reap kills a REMEMBERED pid without reading its image — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/285","peer":"doyle"} 184 {"at_ms":1788778923617,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#286 Daemon stderr grows ~100 MB/day from brain-conn open/close churn — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/286","peer":"doyle"} 185 {"at_ms":1788778945465,"kind":"MSG_OUT","payload":"comment 5569639068 added to BigscreenVR/spt-bs-releases#285","peer":"doyle"} 186 {"at_ms":1788778946762,"kind":"MSG_OUT","payload":"comment 5569639359 added to BigscreenVR/spt-bs-releases#286","peer":"doyle"} 187 {"at_ms":1788782451313,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #265 'idea: spt-core to offer static adapter docs hosting' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/265\nDispatch note: W3 facets lane per WEBSERVE-272-JIT.md W3 section (todlando; hertz takes the drift-gate riders). Start off origin/main in .worktrees/ws272-w3 with its own pool claim; the F17 fixup witness and push on build/ws272-w2 take priority the moment the firewall rule reads present. #266 rides the REFINED 10:14Z ruling (applied signed set, per-triple sha-anchored, all three triples); #265 rides the measured docs_dir ruling; #268 unit half is hertz's.\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #265' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 188 {"at_ms":1788782452695,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#265 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 189 {"at_ms":1788782455608,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #268 'add: pack the changelog into the local docs' (type addition).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/268\nDispatch note: W3 facets lane per WEBSERVE-272-JIT.md W3 section (todlando; hertz takes the drift-gate riders). Start off origin/main in .worktrees/ws272-w3 with its own pool claim; the F17 fixup witness and push on build/ws272-w2 take priority the moment the firewall rule reads present. #266 rides the REFINED 10:14Z ruling (applied signed set, per-triple sha-anchored, all three triples); #265 rides the measured docs_dir ruling; #268 unit half is hertz's.\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #268' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 190 {"at_ms":1788782455875,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#268 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 191 {"at_ms":1788782458013,"kind":"MSG_OUT","payload":"DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #266 'add: spt-core daemon to host installation packages and binaries' (type idea).\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/266\nDispatch note: W3 facets lane per WEBSERVE-272-JIT.md W3 section (todlando; hertz takes the drift-gate riders). Start off origin/main in .worktrees/ws272-w3 with its own pool claim; the F17 fixup witness and push on build/ws272-w2 take priority the moment the firewall rule reads present. #266 rides the REFINED 10:14Z ruling (applied signed set, per-triple sha-anchored, all three triples); #265 rides the measured docs_dir ruling; #268 unit half is hertz's.\nYou are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #266' so merge-close flows back to the Hub. Comment progress on the issue.","peer":"todlando"} 192 {"at_ms":1788782458077,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#266 → dispatched to todlando (github open)\npush to todlando: accepted","peer":"doyle"} 193 {"at_ms":1788821504538,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 194 {"at_ms":1788821520465,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 195 {"at_ms":1788821611115,"kind":"MSG_OUT","payload":"comment 5576396269 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 196 {"at_ms":1788853875184,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#246 → acceptance (github closed, completed)","peer":"doyle"} 197 {"at_ms":1788853876880,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#147 → acceptance (github closed, completed)","peer":"doyle"} 198 {"at_ms":1788853878318,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#17 → acceptance (github closed, completed)","peer":"doyle"} 199 {"at_ms":1788854680658,"kind":"MSG_OUT","payload":"comment 5581493290 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 200 {"at_ms":1788863420077,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#287 type: BUGFIX","peer":"doyle"} 201 {"at_ms":1788864029286,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-progress-tool#81 hints: an agent is told create does not exist — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-progress-tool/issues/81","peer":"flynn"} 202 {"at_ms":1788864100421,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#288 `spt shell cmd <instance> <unknown-op>` names the cmd capability set as THE shell's vocabulary, hiding every send-payload verb — state backlog, type change\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/288","peer":"doyle"} 203 {"at_ms":1788864351876,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-progress-tool: 1 reconciled\n#81 hints: an agent is told create does not exist (backlog → acceptance)","peer":"flynn"} 204 {"at_ms":1788864422782,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-progress-tool alchemy v0.25.0 (2026-09-08T10:45:56Z) — 1 Request(s) done:\n- #81 hints: an agent is told create does not exist\nhttps://github.com/BigscreenVR/spt-progress-tool/releases/tag/v0.25.0","peer":"flynn"} 205 {"at_ms":1788864432580,"kind":"MSG_OUT","payload":"daemon: running (pid 56024, v0.25.0)","peer":"flynn"} 206 {"at_ms":1788864437637,"kind":"MSG_OUT","payload":"comment 5583945280 added to BigscreenVR/spt-progress-tool#81","peer":"flynn"} 207 {"at_ms":1788876749776,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: 3 reconciled\n#268 add: pack the changelog into the local docs (wip → acceptance)\n#266 add: spt-core daemon to host installation packages and binaries (wip → acceptance)\n#265 idea: spt-core to offer static adapter docs hosting (wip → acceptance)","peer":"doyle"} 208 {"at_ms":1788876862140,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\ncreate and comment are send-only (they carry free text); every other verb runs as a `shell cmd`\nop with named args — core's `unknown op` refusal lists those ops only. composite tails ride as\none quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"deployah"} 209 {"at_ms":1788876923971,"kind":"MSG_OUT","payload":"{\n \"body\": \"Includes all the major spt-core requests related to webserving, fileserving, and file transfer. Needs a grill session to fully flesh out.\\n\\n---\\nRequester: discord:134589140258914304\",\n \"comments\": [\n {\n \"author\": \"SaberMage\",\n \"body\": \"**Grill round 1 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q1 AGREE (unified node-prefixed URL namespace). Q2 AGREE (registry as the primitive) + REQUIRED: a filename disambiguation plan — adopted shape: `<stem>~<n>.<ext>` when the bare name is taken, first registrant keeps the bare name, `n` persisted per entry, freed names never reused, same absolute path re-registers to the same entry, `--as <name>` override, `spt serve list` prints path -> URL. Q3 UNSURE — premise measured (below). Q4 AGREE (`--attachment` pull + `spt fetch`). Q5 AGREE (`spt serve lan --bootstrap`, loopback ruling stands). Q6 AGREE with all: ride #248 #249 #246 #265 #268 #147; defer #148; #17 closing rider; **#271 -> SHELVED** (done 09:41Z).\\n\\n**Q3 measurement (main 8a21a3b0):** initiator side TRUE — `fetch_file`/`push_file` have zero production callers (tests only), no CLI verb opens the Xfer stream; `spt shell send --file` uses the progress record locally, not the surface. Serve side LIVE — `serve_xfer` gates the inbound Xfer stream on the XFER surface (xfer.rs:270/:341, dispatch.rs:1161); knock codes and rules can name it; zero grant rows name it on this node. CONTEXT.md:876 already ratifies that webservice facets MINT their ids; :949 names XFER as the next surface to grow a sender stamp. Recommendation, operator to confirm: mint `WEB`, and RETIRE XFER (stream family + gate + tests + row, with `ACCESS_SURFACE_RETIRED` reported for any stored rule) as a #246 close rider — same end state as repurposing, no id changes meaning under existing rules, the superseded code leaves the tree.\\n\\nRound 2 (Q7-Q12: URL sub-namespaces + index page, reference-vs-snapshot + attachment TTL, no-cache owner-checked proxy, #147 short-ID format/verbs, http-only scheme, separate bootstrap port) at spt-core root WEBSERVE-272-GRILL-ROUND-2.md.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-06T09:44:51Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"**Grill round 2 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q3 AGREE with the recommendation → mint `WEB` (default-allow within subnet), RETIRE `XFER` as a #246 close rider, retired-surface rules reported at load (ADR-0060). Q7 AGREE → five sub-namespaces under `/<node>/` (`f/`, `docs/`, `a/<adapter>/`, `m/<short-id>`, `bin/`+`install`) + an index page at `/<node>/` (ADR-0056 amended). Q8 MOSTLY → reference for `serve add`, snapshot for attachments; attachment TTL default **30 days** (operator-set, not 7) (ADR-0058 amended). Q9 AGREE → no-cache proxy, owner-side WEB check under the proven origin, 502 naming the node. Q10 AGREE → 8-char base32 node-scoped short-ID, `spt msg show`, `spt send --reply-to`, id in envelope + io-events (ADR-0061). Q11 AGREE → http only, no `spt://`. Q12 MOSTLY → separate listener + separate allowlist; port **5470** (operator-chosen; measured: IANA `apsolab-col`, same obscure family as 5474 `apsolab-rpc`; 5471-5473 unassigned; free on hfenduleam; no popular-software claim found — Wikipedia port list fetch truncated, unchecked) (ADR-0059 amended).\\n\\nDocs branch `docs/webserve-272-grill` (spt-bs-core, off main, held until v0.67.1 lands): ADR-0056..0061 + CONTEXT.md `## Web serving` (10 terms) + access-surface entry amended. Frontier is EMPTY: no open design question remains; next = wave map + REQ ids at intake.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-06T10:16:05Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"`flag: NEEDS-OPERATOR` cleared by **doyle** — recorded as the Operator discussion having happened.\",\n \"created_at\": \"2026-09-06T10:24:55Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"**INTAKE (doyle, 2026-09-06 ~10:30Z) — operator greenlit in chat after the two-round grill-with-docs.** Wave map at spt-core root `WEBSERVE-272-JIT.md` (version v0.68.0):\\n- W0 substrate (todlando): #248 + local half of #249 — REQ-WEB-URL-NODE-PREFIX, REQ-WEB-SERVING-REGISTRY, REQ-WEB-ACCESS-SURFACE (WEB row minted, gate site in W1)\\n- W1 cross-node (todlando): #249 — REQ-WEB-CROSS-NODE-PROXY (Iroh Web stream family, owner-side WEB check, no-cache)\\n- W2 attachments + identity (todlando): #246 + #147, #17 flips as the closing rider — REQ-WEB-ATTACHMENT-PULL, REQ-WEB-FETCH-VERB, REQ-MSG-SHORT-ID\\n- W3 facets (todlando, hertz on drift-gate riders): #265 (MEASURE FIRST: where adapter docs live), #268, #266 — REQ-WEB-ADAPTER-DOCS-FACET, REQ-DOCS-CHANGELOG-PAGE, REQ-WEB-LAN-BOOTSTRAP-LISTENER (5470)\\n- Close riders: XFER retirement (REQ-XFER-RETIRED, ADR-0060), IR-76 driver pre-flight\\n- #148 detached (deferred, BACKLOG, reason on #148); #271 shelved.\\nAll lanes base off main AFTER v0.67.1 lands; todlando queue = #276 PR -> #277 -> W0 (W0 store work may start now). Design record: ADR-0056..0061 + CONTEXT.md Web serving on spt-bs-core branch docs/webserve-272-grill @a87bd42a.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-06T10:24:57Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"doyle 22:53Z — W2 gate status + an OPERATOR DECISION needed (needs-operator cannot be set on a WIP milestone, so this comment is the flag).\\n\\nDISK on hfenduleam: 15 GB free of 1863 GB. Measured by du (13:42-22:48Z): Users 894 GB (Documents 354 — spt-core pools 190; Downloads 242; Videos 121; AppData 112), Program Files (x86) 629 GB. Cargo pools are ~190 GB (ws272-w2 98, ws272-w3 82, hertz-f19-rig 7, w3-drift 1); the root spt-core/target (10 GB, merged lane) was reaped 13:39Z. The rest is personal data / games, not mine to touch. A test-profile pool weighs 90-112 GB steady state, so the box cannot hold two live lanes plus a golden-style sweep at this free level. Decision needed: free ~150 GB (Downloads/Videos/x86), or rule that lanes on this box run one pool at a time with the other reaped. Until then every build here is HELD except the W2 re-gate under a disk-floor guard.\\n\\nW2 gate: F17 (dispatcher arm) landed at 6e075f7e; F19 (rig one-way seed: roster + audience row) fixed by hertz at bccfaee8 on fix/f19-rig-audience-row (test-only, strict ff). Linux one-box pair at bccfaee8 WITNESSED (owner registered, helper cell 65 s PASS, 5/5 both roles). Windows battery at bccfaee8 launching now; on green: ff build/ws272-w2 to bccfaee8, land, ACCEPTANCE #246/#147/#17. Riders: 65 s helper round trip cross-OS (hertz, IR rider), cross-box helper witness on the operator's firewall rule (IR-83).\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-07T22:53:30Z\"\n },\n {\n \"author\": \"SaberMage\",\n \"body\": \"doyle 08:05Z — W2 LANDED + FIELD PASS.\\n\\nLanded: main = build/ws272-w2 = bccfaee8 (fast-forward, tested sha == merged sha), PR spt-bs-core#199 merged, verdict comment there. Gate: both one-box helper witnesses green (Windows 66.2 s, Linux 65.1 s), libs 1162/1162, three e2e witnesses, mutation D reds exactly the classify cell and the pair. #246 / #147 / #17 -> ACCEPTANCE.\\n\\nField §3 on the staged rig pair, both daemons swapped to the bccfaee8 binaries (rig A hfenduleam, rig B kitsubito): all five rows PASS — attachment delivered with node-prefixed URL + byte count and fetched back sha-equal on B; snapshot unchanged after edit and after delete of the source; ttl 1s entry 404 after the pulse with A's SERVE_REAP line; two same-basename sends mint report.md / report~1.md; a nonexistent path is refused by name (rc 1) with nothing delivered.\\n\\nRiders carried: ~65 s helper round trip on both OSes (hertz), cross-box helper witness on the operator's firewall rule (IR-83), rig docs-port vs config-port (releases#282, seen again: the delivered URL names 5474 while an advisory-ports rig listens elsewhere).\\n\\nDisk after the operator's cleanup: 49 GB free on hfenduleam. Next: W3 gate on todlando's rebased tip, hertz thin PR.\\n\\n*\\\\-doyle@HFENDULEAM*\",\n \"created_at\": \"2026-09-08T08:04:40Z\"\n }\n ],\n \"flags\": [],\n \"issue_state\": \"open\",\n \"number\": 272,\n \"ref\": \"BigscreenVR/spt-bs-releases#272\",\n \"state\": \"greenlit\",\n \"state_reason\": null,\n \"tags\": [],\n \"title\": \"WEBSERVE\",\n \"type\": null,\n \"updated_at\": \"2026-09-08T08:04:40Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/272\"\n}","peer":"deployah"} 210 {"at_ms":1788876962654,"kind":"MSG_OUT","payload":"[\n {\n \"flags\": [],\n \"number\": 265,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"idea: spt-core to offer static adapter docs hosting\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-08T14:12:29Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/265\"\n },\n {\n \"flags\": [],\n \"number\": 266,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"add: spt-core daemon to host installation packages and binaries\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-08T14:12:28Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/266\"\n },\n {\n \"flags\": [],\n \"number\": 268,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"add: pack the changelog into the local docs\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-08T14:12:26Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/268\"\n },\n {\n \"flags\": [],\n \"number\": 288,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"`spt shell cmd <instance> <unknown-op>` names the cmd capability set as THE shell's vocabulary, hiding every send-payload verb\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-08T10:41:40Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/288\"\n },\n {\n \"flags\": [],\n \"number\": 287,\n \"state\": null,\n \"tags\": [],\n \"title\": \"A daemon restart (no machine reboot) strands every persistent shell: the boot-restore discriminant reads the MACHINE boot instant\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-08T10:36:56Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/287\"\n },\n {\n \"flags\": [],\n \"number\": 17,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"now-signal category: FILE_ACCESS_HELPER (remote-node filepath guidance)\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-08T07:51:17Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/17\"\n },\n {\n \"flags\": [],\n \"number\": 147,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"idea: per-msg short ID + `spt endpoint msg <short-id> [--endpoint <id>[@<node>]] [--popup] [--json]`\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-08T07:51:16Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/147\"\n },\n {\n \"flags\": [],\n \"number\": 246,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"endpoint-to-endpoint file transfer: spt send has no --file, and the proven xfer machinery is scoped to a node and the node DRIVING it\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-08T07:51:13Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/246\"\n },\n {\n \"flags\": [],\n \"number\": 286,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"Daemon stderr grows ~100 MB/day from brain-conn open/close churn\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-07T11:02:26Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/286\"\n },\n {\n \"flags\": [],\n \"number\": 285,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"broker.rs zombie reap kills a REMEMBERED pid without reading its image\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-07T11:02:25Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/285\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 284,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: migrate core-relevant [hints] from `claude-spt`\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-07T06:38:25Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/284\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 283,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: project-local monics\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-07T06:38:19Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/283\"\n },\n {\n \"flags\": [],\n \"number\": 282,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"served URLs are minted from the configured docs port, not the port the listener bound: under the rig switch they point at the live fleet daemon\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-07T06:23:19Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/282\"\n },\n {\n \"flags\": [],\n \"number\": 281,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"registry snapshot is write-only for the daemon: prune rows return from memory, a restart forgets peer endpoints until gossip\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-07T06:22:24Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/281\"\n },\n {\n \"flags\": [],\n \"number\": 249,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"feature: cross-node webserving\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-07T03:54:01Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/249\"\n },\n {\n \"flags\": [],\n \"number\": 248,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"feature: generalized fileserving\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-07T00:29:48Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/248\"\n },\n {\n \"flags\": [],\n \"number\": 280,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"io-events: MSG_IN is never published on the `api listen` relay delivery edge (only the hook-poll drain stamps it)\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-06T15:46:01Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/280\"\n },\n {\n \"flags\": [],\n \"number\": 276,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"echo-commune host overwrites an agent's unread authored commune drop: one path, two writers, no arbitration\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-06T14:27:30Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/276\"\n },\n {\n \"flags\": [],\n \"number\": 277,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"io-events seq restarts at 1 once a log passes 256KB: --after cursors go blind or replay old COMMUNE frames (wake markers refire)\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-06T14:27:29Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/277\"\n },\n {\n \"flags\": [],\n \"number\": 279,\n \"state\": \"acceptance\",\n \"tags\": [],\n \"title\": \"api bind prints ER_HOSTED_PROBE:no-row on every bind on a node without an engine room — a diagnostic that decides nothing reads as the refusal\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-06T14:27:28Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/279\"\n },\n {\n \"flags\": [],\n \"number\": 274,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"docs: publish the [service] manifest section on the docs site\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-06T11:32:15Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/274\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 148,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: track endpoint outgoing messages\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-06T10:24:24Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/148\"\n },\n {\n \"flags\": [],\n \"number\": 278,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"adapter update never prunes strings/: files the new archive dropped stay installed (flat-layout skills beside SKILL.md dirs, a foreign claude-spt.exe)\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-06T09:47:56Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/278\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 271,\n \"state\": \"shelved\",\n \"tags\": [],\n \"title\": \"idea: shell-serving cross-node http/s\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-06T09:41:28Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/271\"\n },\n {\n \"flags\": [],\n \"number\": 275,\n \"state\": null,\n \"tags\": [],\n \"title\": \"add: a ResidentService has no authenticated read path to its own adapter's endpoints\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-06T05:41:01Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/275\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 273,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"fix: full session brief fires on session *resume*\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-06T04:34:59Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/273\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 255,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: PTY mouse events passthru\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-05T03:09:36Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/255\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 270,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: any session attach sets `SPT_ENDPOINT_LAST` env var\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-05T03:01:57Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/270\"\n },\n {\n \"flags\": [],\n \"number\": 269,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"change: `spt adapter list`\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-05T03:01:41Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/269\"\n },\n {\n \"flags\": [],\n \"number\": 267,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"fix: `spt daemon refresh` stalls session PTYs\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-05T02:52:46Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/267\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 264,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"add: `spt adapter add <adapter-name> --via-subnet|-vs`\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-05T02:47:39Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/264\"\n },\n {\n \"flags\": [],\n \"number\": 263,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"fix: `[echo_mirror]` is happening too frequently\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-09-05T02:39:00Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/263\"\n },\n {\n \"flags\": [],\n \"number\": 262,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: new endpoint picker flow --> offers placeholder name\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-05T02:12:55Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/262\"\n },\n {\n \"flags\": [],\n \"number\": 261,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"improve: `spt endpoint run` picker updates state live\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-05T02:08:08Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/261\"\n },\n {\n \"flags\": [],\n \"number\": 260,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"add: `Suspend now` to bottom of endpoint options\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-05T02:02:05Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/260\"\n },\n {\n \"flags\": [],\n \"number\": 259,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"add: in the endpoint picker, show adapters' version\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-09-05T02:00:41Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/259\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 258,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: options splash for controlled endpoints upon `suspended`\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-05T01:41:28Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/258\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 257,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: manifest-declared `lite` suspension mode\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-09-05T01:41:22Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/257\"\n },\n {\n \"flags\": [],\n \"number\": 256,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"change: semantics consistency for `spt send`\",\n \"type\": \"change\",\n \"updated_at\": \"2026-09-05T01:08:14Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/256\"\n },\n {\n \"flags\": [],\n \"number\": 11,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"major idea: `spt api now-signal [--user-input-json <msg-json>] [--agent-output-json <msgs-json>]`\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T09:28:12Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/11\"\n },\n {\n \"flags\": [],\n \"number\": 14,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"idea: **endpoints** extension of the `[[hints]]` injection CLI for endpoint names\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T09:28:11Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/14\"\n },\n {\n \"flags\": [],\n \"number\": 18,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"now-signal: SEAL_BRIEF — agent education payload on sealed messages\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-08-30T09:28:10Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/18\"\n },\n {\n \"flags\": [],\n \"number\": 44,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"add: attachment (controllers/viewers) state change channel for shells\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-08-30T09:28:08Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/44\"\n },\n {\n \"flags\": [],\n \"number\": 45,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"idea: endpoint alerts when attachments change\",\n \"type\": \"feature\",\n \"updated_at\": \"2026-08-30T09:28:07Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/45\"\n },\n {\n \"flags\": [],\n \"number\": 113,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"change: bring echo commune cadence in line with legacy SPT\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T09:28:06Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/113\"\n },\n {\n \"flags\": [],\n \"number\": 133,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"add: shell adapter [hints]\",\n \"type\": \"feature\",\n \"updated_at\": \"2026-08-30T09:28:05Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/133\"\n },\n {\n \"flags\": [],\n \"number\": 245,\n \"state\": \"done\",\n \"tags\": [],\n \"title\": \"now-signal category: UPDATES\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-08-30T09:28:04Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/245\"\n },\n {\n \"flags\": [],\n \"number\": 16,\n \"state\": \"eval\",\n \"tags\": [],\n \"title\": \"now-signal category: PROJECTS (previous projects + activity dates + project-context fetch guidance)\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T05:59:52Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/16\"\n },\n {\n \"flags\": [],\n \"number\": 254,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"spt-shells deprecation gate is inert on 2 of 3 session-start paths: cmd_bind and cmd_boundary resolve no manifest, so a compliance-declaring adapter still gets the legacy row\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-08-30T05:47:41Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/254\"\n },\n {\n \"flags\": [],\n \"number\": 253,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"docs: MANIFEST.md never documents [[hints]] at all\",\n \"type\": \"addition\",\n \"updated_at\": \"2026-08-30T05:28:10Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/253\"\n },\n {\n \"flags\": [\n \"needs-operator\"\n ],\n \"number\": 252,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"idea: endpoint picker primarily spawns terminal windows\",\n \"type\": \"idea\",\n \"updated_at\": \"2026-08-30T04:00:25Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/252\"\n },\n {\n \"flags\": [],\n \"number\": 251,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"fix: `spt rc --view` has no way to detach\",\n \"type\": \"bugfix\",\n \"updated_at\": \"2026-08-30T03:58:24Z\",\n \"url\": \"https://github.com/BigscreenVR/spt-bs-releases/issues/251\"\n },\n {\n \"flags\": [],\n \"number\": 250,\n \"state\": \"backlog\",\n \"tags\": [],\n \"title\": \"fix: e","truncated":true,"peer":"deployah"} 211 {"at_ms":1788878081429,"kind":"MSG_OUT","payload":"file 'send-payload.txt' staged (4241 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"deployah"} 212 {"at_ms":1788878114262,"kind":"MSG_OUT","payload":"comment 5586834724 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 213 {"at_ms":1788878114556,"kind":"MSG_OUT","payload":"file 'NEVER-EXECUTED-CELLS-272.md' staged (49674 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"deployah"} 214 {"at_ms":1788878258755,"kind":"MSG_OUT","payload":"comment 5586872072 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 215 {"at_ms":1788883384643,"kind":"MSG_OUT","payload":"file 'alchemy-request-wan.txt' staged (1475 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 216 {"at_ms":1788883421278,"kind":"MSG_OUT","payload":"comment 5588134766 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 217 {"at_ms":1788883486238,"kind":"MSG_OUT","payload":"file 'alchemy-request-wan-body.txt' staged (2000 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 218 {"at_ms":1788883500506,"kind":"MSG_OUT","payload":"error: body is 3475 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 219 {"at_ms":1788883585836,"kind":"MSG_OUT","payload":"file 'alchemy-create-short.txt' staged (1175 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"doyle"} 220 {"at_ms":1788883627382,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 221 {"at_ms":1788883665893,"kind":"MSG_OUT","payload":"error: body is 4651 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it","peer":"doyle"} 222 {"at_ms":1788883713838,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#289 WAN request reply read has no deadline: a peer that accepts and never replies hangs the sender — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/289","peer":"doyle"} 223 {"at_ms":1788885030119,"kind":"MSG_OUT","payload":"error: milestone needs a subcommand: create <title> | add|remove <mref> <ref>[,<ref>…]","peer":"deployah"} 224 {"at_ms":1788885072901,"kind":"MSG_OUT","payload":"error: bad ref '272': expected #N, repo#N, or owner/repo#N","peer":"deployah"} 225 {"at_ms":1788885090488,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#272 WEBSERVE\nstate: greenlit · type: ?\ngithub: open · updated 2026-09-08T16:03:40Z\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/272\n\nIncludes all the major spt-core requests related to webserving, fileserving, and file transfer. Needs a grill session to fully flesh out.\n\n---\nRequester: discord:134589140258914304\n\ncomments (9):\n- SaberMage (2026-09-06T09:44:51Z): **Grill round 1 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q1 AGREE (unified node-prefixed URL namespace). Q2 AGREE (registry as the primitive) + REQUIRED: a filename disambiguation plan — adopted shape: `<stem>~<n>.<ext>` when the bare name is taken, first registrant keeps the bare name, `n` persisted per entry, freed names never reused, same absolute path re-registers to the same entry, `--as <name>` override, `spt serve list` prints path -> URL. Q3 UNSURE — premise measured (below). Q4 AGREE (`--attachment` pull + `spt fetch`). Q5 AGREE (`spt serve lan --bootstrap`, loopback ruling stands). Q6 AGREE with all: ride #248 #249 #246 #265 #268 #147; defer #148; #17 closing rider; **#271 -> SHELVED** (done 09:41Z).\n\n**Q3 measurement (main 8a21a3b0):** initiator side TRUE — `fetch_file`/`push_file` have zero production callers (tests only), no CLI verb opens the Xfer stream; `spt shell send --file` uses the progress record locally, not the surface. Serve side LIVE — `serve_xfer` gates the inbound Xfer stream on the XFER surface (xfer.rs:270/:341, dispatch.rs:1161); knock codes and rules can name it; zero grant rows name it on this node. CONTEXT.md:876 already ratifies that webservice facets MINT their ids; :949 names XFER as the next surface to grow a sender stamp. Recommendation, operator to confirm: mint `WEB`, and RETIRE XFER (stream family + gate + tests + row, with `ACCESS_SURFACE_RETIRED` reported for any stored rule) as a #246 close rider — same end state as repurposing, no id changes meaning under existing rules, the superseded code leaves the tree.\n\nRound 2 (Q7-Q12: URL sub-namespaces + index page, reference-vs-snapshot + attachment TTL, no-cache owner-checked proxy, #147 short-ID format/verbs, http-only scheme, separate bootstrap port) at spt-core root WEBSERVE-272-GRILL-ROUND-2.md.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-06T10:16:05Z): **Grill round 2 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q3 AGREE with the recommendation → mint `WEB` (default-allow within subnet), RETIRE `XFER` as a #246 close rider, retired-surface rules reported at load (ADR-0060). Q7 AGREE → five sub-namespaces under `/<node>/` (`f/`, `docs/`, `a/<adapter>/`, `m/<short-id>`, `bin/`+`install`) + an index page at `/<node>/` (ADR-0056 amended). Q8 MOSTLY → reference for `serve add`, snapshot for attachments; attachment TTL default **30 days** (operator-set, not 7) (ADR-0058 amended). Q9 AGREE → no-cache proxy, owner-side WEB check under the proven origin, 502 naming the node. Q10 AGREE → 8-char base32 node-scoped short-ID, `spt msg show`, `spt send --reply-to`, id in envelope + io-events (ADR-0061). Q11 AGREE → http only, no `spt://`. Q12 MOSTLY → separate listener + separate allowlist; port **5470** (operator-chosen; measured: IANA `apsolab-col`, same obscure family as 5474 `apsolab-rpc`; 5471-5473 unassigned; free on hfenduleam; no popular-software claim found — Wikipedia port list fetch truncated, unchecked) (ADR-0059 amended).\n\nDocs branch `docs/webserve-272-grill` (spt-bs-core, off main, held until v0.67.1 lands): ADR-0056..0061 + CONTEXT.md `## Web serving` (10 terms) + access-surface entry amended. Frontier is EMPTY: no open design question remains; next = wave map + REQ ids at intake.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-06T10:24:55Z): `flag: NEEDS-OPERATOR` cleared by **doyle** — recorded as the Operator discussion having happened.\n- SaberMage (2026-09-06T10:24:57Z): **INTAKE (doyle, 2026-09-06 ~10:30Z) — operator greenlit in chat after the two-round grill-with-docs.** Wave map at spt-core root `WEBSERVE-272-JIT.md` (version v0.68.0):\n- W0 substrate (todlando): #248 + local half of #249 — REQ-WEB-URL-NODE-PREFIX, REQ-WEB-SERVING-REGISTRY, REQ-WEB-ACCESS-SURFACE (WEB row minted, gate site in W1)\n- W1 cross-node (todlando): #249 — REQ-WEB-CROSS-NODE-PROXY (Iroh Web stream family, owner-side WEB check, no-cache)\n- W2 attachments + identity (todlando): #246 + #147, #17 flips as the closing rider — REQ-WEB-ATTACHMENT-PULL, REQ-WEB-FETCH-VERB, REQ-MSG-SHORT-ID\n- W3 facets (todlando, hertz on drift-gate riders): #265 (MEASURE FIRST: where adapter docs live), #268, #266 — REQ-WEB-ADAPTER-DOCS-FACET, REQ-DOCS-CHANGELOG-PAGE, REQ-WEB-LAN-BOOTSTRAP-LISTENER (5470)\n- Close riders: XFER retirement (REQ-XFER-RETIRED, ADR-0060), IR-76 driver pre-flight\n- #148 detached (deferred, BACKLOG, reason on #148); #271 shelved.\nAll lanes base off main AFTER v0.67.1 lands; todlando queue = #276 PR -> #277 -> W0 (W0 store work may start now). Design record: ADR-0056..0061 + CONTEXT.md Web serving on spt-bs-core branch docs/webserve-272-grill @a87bd42a.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-07T22:53:30Z): doyle 22:53Z — W2 gate status + an OPERATOR DECISION needed (needs-operator cannot be set on a WIP milestone, so this comment is the flag).\n\nDISK on hfenduleam: 15 GB free of 1863 GB. Measured by du (13:42-22:48Z): Users 894 GB (Documents 354 — spt-core pools 190; Downloads 242; Videos 121; AppData 112), Program Files (x86) 629 GB. Cargo pools are ~190 GB (ws272-w2 98, ws272-w3 82, hertz-f19-rig 7, w3-drift 1); the root spt-core/target (10 GB, merged lane) was reaped 13:39Z. The rest is personal data / games, not mine to touch. A test-profile pool weighs 90-112 GB steady state, so the box cannot hold two live lanes plus a golden-style sweep at this free level. Decision needed: free ~150 GB (Downloads/Videos/x86), or rule that lanes on this box run one pool at a time with the other reaped. Until then every build here is HELD except the W2 re-gate under a disk-floor guard.\n\nW2 gate: F17 (dispatcher arm) landed at 6e075f7e; F19 (rig one-way seed: roster + audience row) fixed by hertz at bccfaee8 on fix/f19-rig-audience-row (test-only, strict ff). Linux one-box pair at bccfaee8 WITNESSED (owner registered, helper cell 65 s PASS, 5/5 both roles). Windows battery at bccfaee8 launching now; on green: ff build/ws272-w2 to bccfaee8, land, ACCEPTANCE #246/#147/#17. Riders: 65 s helper round trip cross-OS (hertz, IR rider), cross-box helper witness on the operator's firewall rule (IR-83).\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-08T08:04:40Z): doyle 08:05Z — W2 LANDED + FIELD PASS.\n\nLanded: main = build/ws272-w2 = bccfaee8 (fast-forward, tested sha == merged sha), PR spt-bs-core#199 merged, verdict comment there. Gate: both one-box helper witnesses green (Windows 66.2 s, Linux 65.1 s), libs 1162/1162, three e2e witnesses, mutation D reds exactly the classify cell and the pair. #246 / #147 / #17 -> ACCEPTANCE.\n\nField §3 on the staged rig pair, both daemons swapped to the bccfaee8 binaries (rig A hfenduleam, rig B kitsubito): all five rows PASS — attachment delivered with node-prefixed URL + byte count and fetched back sha-equal on B; snapshot unchanged after edit and after delete of the source; ttl 1s entry 404 after the pulse with A's SERVE_REAP line; two same-basename sends mint report.md / report~1.md; a nonexistent path is refused by name (rc 1) with nothing delivered.\n\nRiders carried: ~65 s helper round trip on both OSes (hertz), cross-box helper witness on the operator's firewall rule (IR-83), rig docs-port vs config-port (releases#282, seen again: the delivered URL names 5474 while an advisory-ports rig listens elsewhere).\n\nDisk after the operator's cleanup: 49 GB free on hfenduleam. Next: W3 gate on todlando's rebased tip, hertz thin PR.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-08T14:35:13Z): **GOLDEN-HEAD INTAKE (deployah, 2026-09-08) — #272 WEBSERVE.** Assembled head `fd296557`, shaped head `2f422990` (the sha the golden ref carries and the tag will point at).\n\n**1. Greenlit-form parity: PASS — checked against the greenlight SNAPSHOT, not a reconstruction.** Baseline = this issue's INTAKE comment of 2026-09-06T10:24:57Z: ride #248 #249 #246 #265 #268 #147 #266, #17 as the closing rider, #148 detached to BACKLOG, #271 SHELVED. Live board at intake: all eight riders present at `state: ACCEPTANCE`; #148 still BACKLOG, #271 still SHELVED — both greenlight-time rulings, not drops from the greenlit set, so neither needs a drop discharge. **Zero requests dropped, zero requests added.**\n\nThe riders the gater named are NOT added requests and need no discharge, recorded here so the reading is on the record rather than in chat: XFER retirement was ruled AT greenlight (round-2 comment, operator AGREE; the intake comment carries it as a #246 close rider) and rides at `21c14703` + `fd296557`; the IR-76 driver pre-flight was likewise a greenlight close rider and rides at `8d7b8289` + `7c435564`; hertz's two W3 drift-gate riders are test/CI material inside W3, not Requests.\n\n**2. Release shape: the head was NOT release-shaped; the driver shaped it before the golden ref (IR-54).** Measured at `fd296557`, not assumed: `Cargo.toml` first version line read `version = \"0.67.1\"` and `CHANGELOG.md`'s first section heading read `## [Unreleased]`. Version material authored on top: 0.68.0, Cargo.lock refreshed workspace-only (14 first-party line pairs by diff, zero third-party pins touched), `## [0.68.0]` section, regenerated docs, `xtask check` OK. Bump level justified by observable behavior, not by wave count: `/` now redirects to a node-prefixed index, docs gain a canonical `/<node>/docs/` with the bare paths kept as aliases, every non-empty send carries new envelope material, and an access surface is retired.\n\n**3. Changelog audited against the COMMIT RANGE, mechanically (IR-28) — and the audit found four gaps the milestone narrative would not have.** `git log v0.67.1..fd296557` (57 commits, 21 in the feat/fix class) was matched row by row against the notes. Four bugfixes ride this range from outside milestone #272 and had no changelog line: **#277** (message/activity positions restarting once a log passes 256 KB), **#276** (the automatic summary overwriting an agent's own unread saved context), **#279** (an engine-room probe line printed on a machine with no engine room), **#280** (relay-delivered messages missing from incoming history — already covered). Each now has a user-facing line. The remaining unmatched rows are intra-wave fixes to code that first ships in this release, and are accounted for as such.\n\n**4. Counter and compatibility, established at the explicit sha before the run.** Next release counter = **104**, decoded from v0.67.1's published signed metadata (`version: 103`, `product_version: 0.67.1`), not recalled. Update-set compatibility constants unchanged at the candidate, proven by diff: `BROKER_RESOURCE_ABI = 1` and `brain_ipc_version: 1` both equal the published envelope's values, and `crates/spt-daemon/src/release.rs` changes by exactly one line in the range (a helper's visibility), leaving `SUPPORTED_PLATFORMS`, `KNOWN_TARGET_TRIPLES`, `BUILTIN_RELEASE_KEYS` and `DEFAULT_CHANNEL` untouched.\n\n**5. Never-executed cells: the hand-off arrived without the list, was bounced rather than filled here, and the artifact was then delivered and verified.** Branch `never-executed-272` @ `0a122453`; the file's sha256 matches the gater's stated hash byte-for-byte. **172 test cells added since the last golden (`04e32c8c`, v0.67.1); every one of them has its FIRST CI EXECUTION at this golden run** — 112 have ridden a thin GitHub job, 60 have executed only in local gate batteries and rigs, and none of the 172 has ever run in a golden workflow. Triage consequence, stated before the run rather than after a red: a failure on any of these is structural-until-shown-otherwise, mechanism first, no rate argument and no same-sha rerun.\n\nGolden CI runs on the shaped sha next; the run's id will be pinned by full sha at push time.\n\n*-deployah@HFENDULEAM*\n\nAttachments:\n- [send-payload.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788878081085909700-send-payload.txt)\n\n*\\-deployah@HFENDULEAM*\n- SaberMage (2026-09-08T14:37:38Z): **Precision on the never-executed denominator (deployah, correcting my own line above), with the artifact attached.**\n\nMy intake comment's headline said the 172 added cells have their \"FIRST CI EXECUTION\" at this golden. Read strictly that is wrong for 112 of them, and the same paragraph's own breakdown is the accurate statement. The exact shape:\n\n- **172/172** are at their first execution in a **GOLDEN** run — none of them has ever run in the golden workflow.\n- **112** of the 172 have already executed once in a GitHub job: the W2 PR's thin-CI Windows unit job of 2026-09-07 (preserved as `gate-w2-e3bd53d4/win-unit-101664801162.log`, cited per cell in the attached file).\n- **60** have executed only in local gate batteries and rigs and have **never run in any GitHub job**. Those are the ones listed by name at the end of the attached file.\n\nThe triage rule is unchanged and applies to all 172: a red on any of them is structural-until-shown-otherwise, mechanism first — a denominator of one is not a rate either, so \"it passed once in thin CI\" is not a flake argument.\n\nAttached: `NEVER-EXECUTED-CELLS-272.md`, the gater's hand-off artifact (branch `never-executed-272` @ `0a122453`, sha256 `e5e1f3074875080d16095531c6f46c74edaf9864fcdae0cc1c318424f320ade3`, verified here byte-for-byte), so the list outlives the branch.\n\n*-deployah@HFENDULEAM*\n\nAttachments:\n- [NEVER-EXECUTED-CELLS-272.md](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788878111010742000-NEVER-EXECUTED-CELLS-272.md)\n\n*\\-deployah@HFENDULEAM*\n- SaberMage (2026-09-08T16:03:40Z): **GOLDEN r1 VERDICT: RED — RESPIN (deployah, 2026-09-08).** Run `34239258523` at shaped head `2f4229908ad1bf990b7413b2f218f622b59a20fa` (assembled head `fd296557` + version material only, zero `.rs`). `status=completed`, `conclusion=failure`, 9/9 jobs terminal: traceability, changes, both n1-gates and notify green; both `test` legs and both `twohost` legs red. **`2f422990` is dead as a candidate and the tag will not point at it.**\n\n**TWO mechanisms, both named at source, neither closed by a rerun.**\n\n**1. The delivered envelope stamps `type=\"msg\"` twice.** `crates/spt-msg/src/emit.rs` `splice_typed_msg` (new in W2 `92715374`) rebuilds a delivered envelope from `parsed.attrs` while `compose_typed_event` writes `type` itself, and `parse_attrs` keeps `type` in that list. W2's own unit cell passes because `attr` returns the FIRST match and nothing counts occurrences. Reds: `poll_envelope_e2e::api_poll_emits_whole_self_delimiting_events`, `quickstart_e2e::published_messaging_quickstart_runs_as_written`, `io_events_undriven_kinds_e2e::relay_backlog_and_live_deliveries_stamp_once_even_after_hook_poll` (Windows), plus `gateway_e2e::gateway_binds_and_is_the_user_backed_origin` as a **repin** rather than the same fix — the spool holds the pre-composed envelope; the doubling is at delivery. OS-independent, confirmed on both boxes.\n\n**2. Four role-A web cells share ONE node identity across four ports.** Measured in A's log: one process (pid 52964) running the cells as threads, broker udp 7480/7481/7482/7483 on one key, and only cell 3 owning a dispatch loop. B dialled that key, landed on a live same-key sibling with no dispatch loop, and got an accept with no reply — so `two_host_web_helper_role_a` sat its 900 s on A and `two_host_web_role_b` sat 1260 s on B waiting to be admitted. **One transaction, two timeouts, one per box.** This is the second face of a mechanism hertz had already measured and fixed on a quieter rig, where it appeared as a 63 s stall rather than a hang.\n\n**What is NOT the cause, each ruled out by measurement or source rather than argument, and recorded because each had a live advocate:** the 15:26:15Z–15:31:02Z build-contention window (the failing batch began 15:36:06Z, five minutes after the last user-shell process left the box); rendezvous identity churn (the *passing* ladder step shows the same ~30 s turnover cadence); a re-stamp on arrival (th","truncated":true,"peer":"deployah"} 226 {"at_ms":1788885127714,"kind":"MSG_OUT","payload":"#289 [backlog/bugfix] WAN request reply read has no deadline: a peer that accepts and never replies hangs the sender (updated 2026-09-08T16:08:33Z)\n#288 [backlog/change] `spt shell cmd <instance> <unknown-op>` names the cmd capability set as THE shell's vocabulary, hiding every send-payload verb (updated 2026-09-08T10:41:40Z)\n#287 [?/bugfix] A daemon restart (no machine reboot) strands every persistent shell: the boot-restore discriminant reads the MACHINE boot instant (updated 2026-09-08T10:36:56Z)\n#286 [backlog/bugfix] Daemon stderr grows ~100 MB/day from brain-conn open/close churn (updated 2026-09-07T11:02:26Z)\n#285 [backlog/bugfix] broker.rs zombie reap kills a REMEMBERED pid without reading its image (updated 2026-09-07T11:02:25Z)\n#284 [backlog/idea] idea: migrate core-relevant [hints] from `claude-spt` (updated 2026-09-07T06:38:25Z)\n#283 [backlog/idea] idea: project-local monics (updated 2026-09-07T06:38:19Z)\n#282 [backlog/bugfix] served URLs are minted from the configured docs port, not the port the listener bound: under the rig switch they point at the live fleet daemon (updated 2026-09-07T06:23:19Z)\n#281 [backlog/bugfix] registry snapshot is write-only for the daemon: prune rows return from memory, a restart forgets peer endpoints until gossip (updated 2026-09-07T06:22:24Z)\n#148 [backlog/idea] idea: track endpoint outgoing messages (updated 2026-09-06T10:24:24Z)\n#278 [backlog/change] adapter update never prunes strings/: files the new archive dropped stay installed (flat-layout skills beside SKILL.md dirs, a foreign claude-spt.exe) (updated 2026-09-06T09:47:56Z)\n#275 [?/addition] add: a ResidentService has no authenticated read path to its own adapter's endpoints (updated 2026-09-06T05:41:01Z)\n#273 [backlog/change] fix: full session brief fires on session *resume* (updated 2026-09-06T04:34:59Z)\n#255 [backlog/idea] idea: PTY mouse events passthru (updated 2026-09-05T03:09:36Z)\n#270 [backlog/idea] idea: any session attach sets `SPT_ENDPOINT_LAST` env var (updated 2026-09-05T03:01:57Z)\n#269 [backlog/change] change: `spt adapter list` (updated 2026-09-05T03:01:41Z)\n#267 [backlog/bugfix] fix: `spt daemon refresh` stalls session PTYs (updated 2026-09-05T02:52:46Z)\n#264 [backlog/idea] add: `spt adapter add <adapter-name> --via-subnet|-vs` (updated 2026-09-05T02:47:39Z)\n#263 [backlog/bugfix] fix: `[echo_mirror]` is happening too frequently (updated 2026-09-05T02:39:00Z)\n#262 [backlog/addition] idea: new endpoint picker flow --> offers placeholder name (updated 2026-09-05T02:12:55Z)\n#261 [backlog/change] improve: `spt endpoint run` picker updates state live (updated 2026-09-05T02:08:08Z)\n#260 [backlog/addition] add: `Suspend now` to bottom of endpoint options (updated 2026-09-05T02:02:05Z)\n#259 [backlog/addition] add: in the endpoint picker, show adapters' version (updated 2026-09-05T02:00:41Z)\n#258 [backlog/idea] idea: options splash for controlled endpoints upon `suspended` (updated 2026-09-05T01:41:28Z)\n#257 [backlog/idea] idea: manifest-declared `lite` suspension mode (updated 2026-09-05T01:41:22Z)\n#256 [backlog/change] change: semantics consistency for `spt send` (updated 2026-09-05T01:08:14Z)\n#16 [eval/idea] now-signal category: PROJECTS (previous projects + activity dates + project-context fetch guidance) (updated 2026-08-30T05:59:52Z)\n#254 [backlog/bugfix] spt-shells deprecation gate is inert on 2 of 3 session-start paths: cmd_bind and cmd_boundary resolve no manifest, so a compliance-declaring adapter still gets the legacy row (updated 2026-08-30T05:47:41Z)\n#253 [backlog/addition] docs: MANIFEST.md never documents [[hints]] at all (updated 2026-08-30T05:28:10Z)\n#252 [backlog/idea] idea: endpoint picker primarily spawns terminal windows (updated 2026-08-30T04:00:25Z)\n#251 [backlog/bugfix] fix: `spt rc --view` has no way to detach (updated 2026-08-30T03:58:24Z)\n#250 [backlog/bugfix] fix: enrolled seal authentication on windows starts minimized (updated 2026-08-30T03:57:46Z)\n#247 [backlog/addition] EDGE_TRANSITIONS: endpoint-level subnet-join transitions with origin node (z joined <subnet> from <node>) — the data source does not exist (updated 2026-08-30T02:38:34Z)\n#243 [backlog/bugfix] Residual machine-parsed emitter population: census truncation left 338 shipping token-shaped eprintln! sites unconverted (cli.rs post-line-3164 + stragglers) (updated 2026-08-30T02:09:23Z)\n#244 [backlog/change] Move current_exe_hash() off the daemon ready path — a ~10s synchronous hash per Linux boot sits inside the ONLINE window (ADR-0018 Q7 behaviour change) (updated 2026-08-30T02:01:56Z)\n#232 [backlog/idea] idea: \"retry ID\" for failed seals (updated 2026-08-28T00:15:07Z)\n#231 [backlog/addition] Hello ceremony modal is generic: no purpose text, fallback icon (CredentialUIBroker) (updated 2026-08-26T04:10:00Z)\n#230 [backlog/addition] Attach-viewer version skew after update is invisible — stale viewers replay retired bugs (updated 2026-08-26T03:57:00Z)\n#227 [backlog/change] notify rows carry a PROVEN sender so a tier-1 subject rule can match on notify (updated 2026-08-25T12:58:55Z)\n#214 [backlog/change] Should `spt daemon status` surface the inbound-blocked warning that subnet status already shows? (updated 2026-08-22T04:35:11Z)\n#207 [backlog/addition] add: no operator verb closes an endpoint's posture — the only close is a side effect of the positional allow, which conflates close-with-admit (updated 2026-08-21T11:01:54Z)\n#194 [backlog/change] Cross-process dispatcher exclusion: two dispatcher processes on one home each serve the same streams (updated 2026-08-19T04:42:35Z)\n#195 [eval/change] Widening gate refuses semantically subsumed node grants — keys on tuple shape, not subsumption (updated 2026-08-19T04:26:00Z)\n#189 [eval/bugfix] twohost rig: B-side pump drops its only peer conn (brain IPC reply-read starve) and re-dials never heal (updated 2026-08-19T04:25:57Z)\n#191 [eval/bugfix] daemon autostart binds a home already hosted by a live daemon - split-brain control reap across the two (updated 2026-08-18T20:03:59Z)\n#192 [eval/change] daemon-spawned children are unobservable: every ruled loud print dies in Stdio::null() (updated 2026-08-18T19:00:27Z)\n#174 [backlog/bugfix] QUIC endpoint does not recover from a NIC/interface bounce; all peer dials wedge at quic-connect until binder restart (updated 2026-08-17T20:44:29Z)\n#162 [backlog/addition] add: session argument on `endpoint resume` — specific-session resume returns to the CLI (updated 2026-08-07T01:39:19Z)\n#123 [wip/bugfix] resume_no_control_steal_e2e: one session's controller froze post-resume at golden scale — first-sighting race, hunt it (updated 2026-08-05T20:08:44Z)\n#158 [backlog/addition] Perch-GC automation: daemon-fired sweep of ruled residue population (updated 2026-08-04T23:26:51Z)\n#156 [backlog/change] Access-subsystem published surface: blind-consumer audit against the chain code (updated 2026-08-04T22:13:07Z)\n#152 [backlog/addition] spt shell unlink — explicit stop-half surface for shell links (updated 2026-08-04T21:35:51Z)\n#151 [eval/bugfix] wait_bounded leaves the awaited process tree running on bound expiry (needs tree-kill-on-timeout) (updated 2026-08-04T20:45:48Z)\n#131 [eval/bugfix] Windows supervised services leave visible console husks — mechanism UNKNOWN, first diagnosis falsified (updated 2026-08-04T10:27:15Z)\n#149 [backlog/bugfix] diagnose and triage: knock code redemption issues (updated 2026-08-04T09:01:55Z)\n#146 [backlog/change] change: oversized inbound deliveries force an adapter-side disk spill — address the size pressure at the delivery seam (updated 2026-08-04T01:19:03Z)\n#143 [backlog/bugfix] Bare-pid liveness probes: 9 production sites unsound to pid recycle, and two activated hazard REQs read covered with the named arm undefended (updated 2026-08-03T23:41:41Z)\n#140 [backlog/bugfix] bare-pid liveness probes rest on a \"rare during steady-state\" premise measured false: pid reused in ~30s, same boot (updated 2026-08-03T16:07:26Z)\n#139 [backlog/change] bind conflict check probes a Binder pid that has already exited — what guards an spt-hosted perch from bind-over? (updated 2026-08-03T14:26:33Z)\n#138 [backlog/bugfix] dead-owner re-pin and establish_perch re-bind leave the prior session empowerment standing (releases#117 closes only the boundary edge) (updated 2026-08-03T13:19:31Z)\n#136 [backlog/change] endpoint list --json: psyche_host_error never skips while its two sibling fault fields do (updated 2026-08-03T12:33:05Z)\n#135 [backlog/idea] idea: window-focus-edge surfacing (updated 2026-08-03T11:57:33Z)\n#120 [backlog/addition] harden the authenticated kill: corroborate the pair test with the target's image path (unifies KH 7.58's rig rule with the product gate) (updated 2026-08-02T17:09:08Z)\n#94 [eval/bugfix] api poll exits 1 silently when a transient daemon-probe miss triggers autostart under an elevated context (updated 2026-08-01T23:14:19Z)\n#93 [wip/bugfix] servicehost swap test asserts process identity by pid inequality — unsound under Windows pid reuse (updated 2026-08-01T23:14:17Z)\n#81 [backlog/bugfix] one shell send carrying text + --file delivers the text frame first, stranding the file (updated 2026-08-01T09:55:03Z)\n#62 [eval/change] change: should the extractor force (or loudly refuse) a non-executable declared entry binary? (updated 2026-08-01T01:50:05Z)\n#64 [backlog/change] change: surface an active release-keys.json trust-anchor override in status output (updated 2026-08-01T01:35:57Z)\n#60 [backlog/addition] add: dial-path attribution at the connect seam (relay-vs-direct, un-flattened errors) (updated 2026-07-31T21:08:53Z)\n#42 [eval/bugfix] relay path produces no connections: canary-vs-config mismatch + dial-via-relay ineffective (RCA lane) (updated 2026-07-31T21:07:32Z)\n#52 [eval/change] Audit atomic.rs's RECONSTRUCTIBLE-state doc list — the epoch counter was on it and was not reconstructible (updated 2026-07-31T09:31:41Z)\n#55 [backlog/bugfix] Audit remaining daemon.pid readers — breadcrumb is not an identity oracle (7.58 read-side) (updated 2026-07-31T08:19:06Z)\n#54 [backlog/change] Linux stable-port knob + firewall rule write (L1 half of #43, deferred by ruling) (updated 2026-07-31T07:42:53Z)\n#51 [backlog/idea] add: shell cmd to support piping stdout from shell binary (updated 2026-07-31T05:44:06Z)\n#49 [eval/bugfix] all spt rc connections freeze across `spt daemon refresh` / staged self-update restart (long-standing; prior fixes unsuccessful) (updated 2026-07-31T05:33:23Z)\n#47 [wip/bugfix] thin-lane unit(Windows) red at golden-green shas: in-process test-isolation class under cargo test threading (updated 2026-07-31T05:06:23Z)\n#46 [wip/bugfix] tree-kill/pid-reuse unsound reapers: port authenticated-reap to the 12 remaining taskkill /F sites (updated 2026-07-31T04:14:44Z)\n#32 [wip/bugfix] worker_lifecycle_e2e Windows Phase A — intermittent, mechanism WEAKENED, guard UNEXERCISED (updated 2026-07-31T03:56:45Z)\n#34 [backlog/idea] idea: split spt-core into submodules (updated 2026-07-31T01:19:08Z)\n#30 [backlog/bugfix] peer pump dials wedge at quic-connect and misreport a LOCAL submit stall as \"peer unresponsive\" (updated 2026-07-30T02:29:39Z)\n#26 [backlog/bugfix] peer pump stale-op_id stream-open retry loop never self-heals after broker restart (updated 2026-07-29T21:43:18Z)\n#28 [backlog/idea] change: make the SPT picker GUI access-rules-aware (updated 2026-07-29T15:45:01Z)\n#25 [backlog/bugfix] new spt-hosted session bringup wedged after daemon/broker cold restart (harness-hosted unaffected) (updated 2026-07-29T11:18:49Z)\n#2 [eval/change] Upgrading a shared-exe service must not require a node-wide stand-down of every instance (updated 2026-07-28T02:17:48Z)\n#4 [backlog/addition] add: \"seamless update contract\" for adapters (updated 2026-07-28T02:16:32Z)","peer":"deployah"} 227 {"at_ms":1788885166082,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#289 WAN request reply read has no deadline: a peer that accepts and never replies hangs the sender\nstate: backlog · type: bugfix\ngithub: open · updated 2026-09-08T16:08:33Z\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/289\n\nrequest_wan (crates/spt-daemon/src/wan.rs 283 to 312 at fd296557) loops on brain.read_event with no deadline after sending a WanMessage; NoReply is minted only on stream EOF or an unknown reply token. Golden run 34239258523 twohost-b: the far daemon accepted the QUIC stream and never replied, so role B sat 21 minutes (15:36:10Z to 15:56:58Z) against a 900 s rig deadline and returned only when the peer process died. Pre-existing since ec360f16 (2026-06-30), present at v0.67.1; not a #272 regression. Fix: a bounded reply read returning its OWN outcome (never folded into NoReply, which already covers two causes the source cannot separate), plus a cell with a fake peer that accepts and never replies asserting the call returns within budget and names the outcome; a daemon accepting a WAN stream it will never read should log it. Owner todlando, next lane after the v0.68.0 respin. Detail in the attached files.\n\nAttachments:\n- [alchemy-request-wan.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788883383365356700-alchemy-request-wan.txt)\n- [alchemy-request-wan-body.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788883485720868700-alchemy-request-wan-body.txt)\n- [alchemy-create-short.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788883581490383800-alchemy-create-short.txt)\n\n---\nRequester: doyle","peer":"deployah"} 228 {"at_ms":1788891649770,"kind":"MSG_OUT","payload":"comment 5589826954 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 229 {"at_ms":1788902100187,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 230 {"at_ms":1788902153117,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 231 {"at_ms":1788902237797,"kind":"MSG_OUT","payload":"comment 5591991978 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 232 {"at_ms":1788911275222,"kind":"MSG_OUT","payload":"comment 5593524445 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 233 {"at_ms":1788912364494,"kind":"MSG_OUT","payload":"error: bad ref '272': expected #N, repo#N, or owner/repo#N","peer":"deployah"} 234 {"at_ms":1788912405715,"kind":"MSG_OUT","payload":"BigscreenVR/spt-bs-releases#272 WEBSERVE\nstate: greenlit · type: ?\ngithub: open · updated 2026-09-08T23:47:54Z\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/272\n\nIncludes all the major spt-core requests related to webserving, fileserving, and file transfer. Needs a grill session to fully flesh out.\n\n---\nRequester: discord:134589140258914304\n\ncomments (12):\n- SaberMage (2026-09-06T09:44:51Z): **Grill round 1 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q1 AGREE (unified node-prefixed URL namespace). Q2 AGREE (registry as the primitive) + REQUIRED: a filename disambiguation plan — adopted shape: `<stem>~<n>.<ext>` when the bare name is taken, first registrant keeps the bare name, `n` persisted per entry, freed names never reused, same absolute path re-registers to the same entry, `--as <name>` override, `spt serve list` prints path -> URL. Q3 UNSURE — premise measured (below). Q4 AGREE (`--attachment` pull + `spt fetch`). Q5 AGREE (`spt serve lan --bootstrap`, loopback ruling stands). Q6 AGREE with all: ride #248 #249 #246 #265 #268 #147; defer #148; #17 closing rider; **#271 -> SHELVED** (done 09:41Z).\n\n**Q3 measurement (main 8a21a3b0):** initiator side TRUE — `fetch_file`/`push_file` have zero production callers (tests only), no CLI verb opens the Xfer stream; `spt shell send --file` uses the progress record locally, not the surface. Serve side LIVE — `serve_xfer` gates the inbound Xfer stream on the XFER surface (xfer.rs:270/:341, dispatch.rs:1161); knock codes and rules can name it; zero grant rows name it on this node. CONTEXT.md:876 already ratifies that webservice facets MINT their ids; :949 names XFER as the next surface to grow a sender stamp. Recommendation, operator to confirm: mint `WEB`, and RETIRE XFER (stream family + gate + tests + row, with `ACCESS_SURFACE_RETIRED` reported for any stored rule) as a #246 close rider — same end state as repurposing, no id changes meaning under existing rules, the superseded code leaves the tree.\n\nRound 2 (Q7-Q12: URL sub-namespaces + index page, reference-vs-snapshot + attachment TTL, no-cache owner-checked proxy, #147 short-ID format/verbs, http-only scheme, separate bootstrap port) at spt-core root WEBSERVE-272-GRILL-ROUND-2.md.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-06T10:16:05Z): **Grill round 2 — operator rulings (2026-09-06, in chat, recorded by doyle):** Q3 AGREE with the recommendation → mint `WEB` (default-allow within subnet), RETIRE `XFER` as a #246 close rider, retired-surface rules reported at load (ADR-0060). Q7 AGREE → five sub-namespaces under `/<node>/` (`f/`, `docs/`, `a/<adapter>/`, `m/<short-id>`, `bin/`+`install`) + an index page at `/<node>/` (ADR-0056 amended). Q8 MOSTLY → reference for `serve add`, snapshot for attachments; attachment TTL default **30 days** (operator-set, not 7) (ADR-0058 amended). Q9 AGREE → no-cache proxy, owner-side WEB check under the proven origin, 502 naming the node. Q10 AGREE → 8-char base32 node-scoped short-ID, `spt msg show`, `spt send --reply-to`, id in envelope + io-events (ADR-0061). Q11 AGREE → http only, no `spt://`. Q12 MOSTLY → separate listener + separate allowlist; port **5470** (operator-chosen; measured: IANA `apsolab-col`, same obscure family as 5474 `apsolab-rpc`; 5471-5473 unassigned; free on hfenduleam; no popular-software claim found — Wikipedia port list fetch truncated, unchecked) (ADR-0059 amended).\n\nDocs branch `docs/webserve-272-grill` (spt-bs-core, off main, held until v0.67.1 lands): ADR-0056..0061 + CONTEXT.md `## Web serving` (10 terms) + access-surface entry amended. Frontier is EMPTY: no open design question remains; next = wave map + REQ ids at intake.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-06T10:24:55Z): `flag: NEEDS-OPERATOR` cleared by **doyle** — recorded as the Operator discussion having happened.\n- SaberMage (2026-09-06T10:24:57Z): **INTAKE (doyle, 2026-09-06 ~10:30Z) — operator greenlit in chat after the two-round grill-with-docs.** Wave map at spt-core root `WEBSERVE-272-JIT.md` (version v0.68.0):\n- W0 substrate (todlando): #248 + local half of #249 — REQ-WEB-URL-NODE-PREFIX, REQ-WEB-SERVING-REGISTRY, REQ-WEB-ACCESS-SURFACE (WEB row minted, gate site in W1)\n- W1 cross-node (todlando): #249 — REQ-WEB-CROSS-NODE-PROXY (Iroh Web stream family, owner-side WEB check, no-cache)\n- W2 attachments + identity (todlando): #246 + #147, #17 flips as the closing rider — REQ-WEB-ATTACHMENT-PULL, REQ-WEB-FETCH-VERB, REQ-MSG-SHORT-ID\n- W3 facets (todlando, hertz on drift-gate riders): #265 (MEASURE FIRST: where adapter docs live), #268, #266 — REQ-WEB-ADAPTER-DOCS-FACET, REQ-DOCS-CHANGELOG-PAGE, REQ-WEB-LAN-BOOTSTRAP-LISTENER (5470)\n- Close riders: XFER retirement (REQ-XFER-RETIRED, ADR-0060), IR-76 driver pre-flight\n- #148 detached (deferred, BACKLOG, reason on #148); #271 shelved.\nAll lanes base off main AFTER v0.67.1 lands; todlando queue = #276 PR -> #277 -> W0 (W0 store work may start now). Design record: ADR-0056..0061 + CONTEXT.md Web serving on spt-bs-core branch docs/webserve-272-grill @a87bd42a.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-07T22:53:30Z): doyle 22:53Z — W2 gate status + an OPERATOR DECISION needed (needs-operator cannot be set on a WIP milestone, so this comment is the flag).\n\nDISK on hfenduleam: 15 GB free of 1863 GB. Measured by du (13:42-22:48Z): Users 894 GB (Documents 354 — spt-core pools 190; Downloads 242; Videos 121; AppData 112), Program Files (x86) 629 GB. Cargo pools are ~190 GB (ws272-w2 98, ws272-w3 82, hertz-f19-rig 7, w3-drift 1); the root spt-core/target (10 GB, merged lane) was reaped 13:39Z. The rest is personal data / games, not mine to touch. A test-profile pool weighs 90-112 GB steady state, so the box cannot hold two live lanes plus a golden-style sweep at this free level. Decision needed: free ~150 GB (Downloads/Videos/x86), or rule that lanes on this box run one pool at a time with the other reaped. Until then every build here is HELD except the W2 re-gate under a disk-floor guard.\n\nW2 gate: F17 (dispatcher arm) landed at 6e075f7e; F19 (rig one-way seed: roster + audience row) fixed by hertz at bccfaee8 on fix/f19-rig-audience-row (test-only, strict ff). Linux one-box pair at bccfaee8 WITNESSED (owner registered, helper cell 65 s PASS, 5/5 both roles). Windows battery at bccfaee8 launching now; on green: ff build/ws272-w2 to bccfaee8, land, ACCEPTANCE #246/#147/#17. Riders: 65 s helper round trip cross-OS (hertz, IR rider), cross-box helper witness on the operator's firewall rule (IR-83).\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-08T08:04:40Z): doyle 08:05Z — W2 LANDED + FIELD PASS.\n\nLanded: main = build/ws272-w2 = bccfaee8 (fast-forward, tested sha == merged sha), PR spt-bs-core#199 merged, verdict comment there. Gate: both one-box helper witnesses green (Windows 66.2 s, Linux 65.1 s), libs 1162/1162, three e2e witnesses, mutation D reds exactly the classify cell and the pair. #246 / #147 / #17 -> ACCEPTANCE.\n\nField §3 on the staged rig pair, both daemons swapped to the bccfaee8 binaries (rig A hfenduleam, rig B kitsubito): all five rows PASS — attachment delivered with node-prefixed URL + byte count and fetched back sha-equal on B; snapshot unchanged after edit and after delete of the source; ttl 1s entry 404 after the pulse with A's SERVE_REAP line; two same-basename sends mint report.md / report~1.md; a nonexistent path is refused by name (rc 1) with nothing delivered.\n\nRiders carried: ~65 s helper round trip on both OSes (hertz), cross-box helper witness on the operator's firewall rule (IR-83), rig docs-port vs config-port (releases#282, seen again: the delivered URL names 5474 while an advisory-ports rig listens elsewhere).\n\nDisk after the operator's cleanup: 49 GB free on hfenduleam. Next: W3 gate on todlando's rebased tip, hertz thin PR.\n\n*\\-doyle@HFENDULEAM*\n- SaberMage (2026-09-08T14:35:13Z): **GOLDEN-HEAD INTAKE (deployah, 2026-09-08) — #272 WEBSERVE.** Assembled head `fd296557`, shaped head `2f422990` (the sha the golden ref carries and the tag will point at).\n\n**1. Greenlit-form parity: PASS — checked against the greenlight SNAPSHOT, not a reconstruction.** Baseline = this issue's INTAKE comment of 2026-09-06T10:24:57Z: ride #248 #249 #246 #265 #268 #147 #266, #17 as the closing rider, #148 detached to BACKLOG, #271 SHELVED. Live board at intake: all eight riders present at `state: ACCEPTANCE`; #148 still BACKLOG, #271 still SHELVED — both greenlight-time rulings, not drops from the greenlit set, so neither needs a drop discharge. **Zero requests dropped, zero requests added.**\n\nThe riders the gater named are NOT added requests and need no discharge, recorded here so the reading is on the record rather than in chat: XFER retirement was ruled AT greenlight (round-2 comment, operator AGREE; the intake comment carries it as a #246 close rider) and rides at `21c14703` + `fd296557`; the IR-76 driver pre-flight was likewise a greenlight close rider and rides at `8d7b8289` + `7c435564`; hertz's two W3 drift-gate riders are test/CI material inside W3, not Requests.\n\n**2. Release shape: the head was NOT release-shaped; the driver shaped it before the golden ref (IR-54).** Measured at `fd296557`, not assumed: `Cargo.toml` first version line read `version = \"0.67.1\"` and `CHANGELOG.md`'s first section heading read `## [Unreleased]`. Version material authored on top: 0.68.0, Cargo.lock refreshed workspace-only (14 first-party line pairs by diff, zero third-party pins touched), `## [0.68.0]` section, regenerated docs, `xtask check` OK. Bump level justified by observable behavior, not by wave count: `/` now redirects to a node-prefixed index, docs gain a canonical `/<node>/docs/` with the bare paths kept as aliases, every non-empty send carries new envelope material, and an access surface is retired.\n\n**3. Changelog audited against the COMMIT RANGE, mechanically (IR-28) — and the audit found four gaps the milestone narrative would not have.** `git log v0.67.1..fd296557` (57 commits, 21 in the feat/fix class) was matched row by row against the notes. Four bugfixes ride this range from outside milestone #272 and had no changelog line: **#277** (message/activity positions restarting once a log passes 256 KB), **#276** (the automatic summary overwriting an agent's own unread saved context), **#279** (an engine-room probe line printed on a machine with no engine room), **#280** (relay-delivered messages missing from incoming history — already covered). Each now has a user-facing line. The remaining unmatched rows are intra-wave fixes to code that first ships in this release, and are accounted for as such.\n\n**4. Counter and compatibility, established at the explicit sha before the run.** Next release counter = **104**, decoded from v0.67.1's published signed metadata (`version: 103`, `product_version: 0.67.1`), not recalled. Update-set compatibility constants unchanged at the candidate, proven by diff: `BROKER_RESOURCE_ABI = 1` and `brain_ipc_version: 1` both equal the published envelope's values, and `crates/spt-daemon/src/release.rs` changes by exactly one line in the range (a helper's visibility), leaving `SUPPORTED_PLATFORMS`, `KNOWN_TARGET_TRIPLES`, `BUILTIN_RELEASE_KEYS` and `DEFAULT_CHANNEL` untouched.\n\n**5. Never-executed cells: the hand-off arrived without the list, was bounced rather than filled here, and the artifact was then delivered and verified.** Branch `never-executed-272` @ `0a122453`; the file's sha256 matches the gater's stated hash byte-for-byte. **172 test cells added since the last golden (`04e32c8c`, v0.67.1); every one of them has its FIRST CI EXECUTION at this golden run** — 112 have ridden a thin GitHub job, 60 have executed only in local gate batteries and rigs, and none of the 172 has ever run in a golden workflow. Triage consequence, stated before the run rather than after a red: a failure on any of these is structural-until-shown-otherwise, mechanism first, no rate argument and no same-sha rerun.\n\nGolden CI runs on the shaped sha next; the run's id will be pinned by full sha at push time.\n\n*-deployah@HFENDULEAM*\n\nAttachments:\n- [send-payload.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788878081085909700-send-payload.txt)\n\n*\\-deployah@HFENDULEAM*\n- SaberMage (2026-09-08T14:37:38Z): **Precision on the never-executed denominator (deployah, correcting my own line above), with the artifact attached.**\n\nMy intake comment's headline said the 172 added cells have their \"FIRST CI EXECUTION\" at this golden. Read strictly that is wrong for 112 of them, and the same paragraph's own breakdown is the accurate statement. The exact shape:\n\n- **172/172** are at their first execution in a **GOLDEN** run — none of them has ever run in the golden workflow.\n- **112** of the 172 have already executed once in a GitHub job: the W2 PR's thin-CI Windows unit job of 2026-09-07 (preserved as `gate-w2-e3bd53d4/win-unit-101664801162.log`, cited per cell in the attached file).\n- **60** have executed only in local gate batteries and rigs and have **never run in any GitHub job**. Those are the ones listed by name at the end of the attached file.\n\nThe triage rule is unchanged and applies to all 172: a red on any of them is structural-until-shown-otherwise, mechanism first — a denominator of one is not a rate either, so \"it passed once in thin CI\" is not a flake argument.\n\nAttached: `NEVER-EXECUTED-CELLS-272.md`, the gater's hand-off artifact (branch `never-executed-272` @ `0a122453`, sha256 `e5e1f3074875080d16095531c6f46c74edaf9864fcdae0cc1c318424f320ade3`, verified here byte-for-byte), so the list outlives the branch.\n\n*-deployah@HFENDULEAM*\n\nAttachments:\n- [NEVER-EXECUTED-CELLS-272.md](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1788878111010742000-NEVER-EXECUTED-CELLS-272.md)\n\n*\\-deployah@HFENDULEAM*\n- SaberMage (2026-09-08T16:03:40Z): **GOLDEN r1 VERDICT: RED — RESPIN (deployah, 2026-09-08).** Run `34239258523` at shaped head `2f4229908ad1bf990b7413b2f218f622b59a20fa` (assembled head `fd296557` + version material only, zero `.rs`). `status=completed`, `conclusion=failure`, 9/9 jobs terminal: traceability, changes, both n1-gates and notify green; both `test` legs and both `twohost` legs red. **`2f422990` is dead as a candidate and the tag will not point at it.**\n\n**TWO mechanisms, both named at source, neither closed by a rerun.**\n\n**1. The delivered envelope stamps `type=\"msg\"` twice.** `crates/spt-msg/src/emit.rs` `splice_typed_msg` (new in W2 `92715374`) rebuilds a delivered envelope from `parsed.attrs` while `compose_typed_event` writes `type` itself, and `parse_attrs` keeps `type` in that list. W2's own unit cell passes because `attr` returns the FIRST match and nothing counts occurrences. Reds: `poll_envelope_e2e::api_poll_emits_whole_self_delimiting_events`, `quickstart_e2e::published_messaging_quickstart_runs_as_written`, `io_events_undriven_kinds_e2e::relay_backlog_and_live_deliveries_stamp_once_even_after_hook_poll` (Windows), plus `gateway_e2e::gateway_binds_and_is_the_user_backed_origin` as a **repin** rather than the same fix — the spool holds the pre-composed envelope; the doubling is at delivery. OS-independent, confirmed on both boxes.\n\n**2. Four role-A web cells share ONE node identity across four ports.** Measured in A's log: one process (pid 52964) running the cells as threads, broker udp 7480/7481/7482/7483 on one key, and only cell 3 owning a dispatch loop. B dialled that key, landed on a live same-key sibling with no dispatch loop, and got an accept with no reply — so `two_host_web_helper_role_a` sat its 900 s on A and `two_host_web_role_b` sat 1260 s on B waiting to be admitted. **One transaction, two timeouts, one per box.** This is the second face of a mechanism hertz had already measured and fixed on a quieter rig, where it appeared as a 63 s stall rather than a hang.\n\n**What is NOT the cause, each ruled out by measurement or source rather than argument, and recorded because each had a live advocate:** the 15:26:15Z–15:31:02Z build-contention window (the failing batch began 15:36:06Z, five minutes after the last user-shell process left the box); rendezvous identity churn (the *passing* ladder step shows the same ~30 s turnover cadence); a re-stamp on arrival (t","truncated":true,"peer":"deployah"} 235 {"at_ms":1788912516309,"kind":"MSG_OUT","payload":"comment 5593691274 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 236 {"at_ms":1788912598038,"kind":"MSG_OUT","payload":"error: bad ref '272': expected #N, repo#N, or owner/repo#N","peer":"doyle"} 237 {"at_ms":1788912638413,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\nthe same verbs run as `shell cmd` ops with named args; composite tails ride as one quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 238 {"at_ms":1788912832392,"kind":"MSG_OUT","payload":"[tag] Bagged Requests in BigscreenVR/spt-pacer-tool — none, as of 2026-09-09T00:12:32Z (the daemon's last cycle; not live)","peer":"perri"} 239 {"at_ms":1788914004998,"kind":"MSG_OUT","payload":"Bagged Requests in BigscreenVR/spt-progress-tool\n4 bagged, as of 2026-09-09T00:33:17Z (the daemon's last cycle; not live)\nall bagged by Reavo End\nall in Backlog\n #13 idea: per-repo living files - issues lists for agent searches — https://github.com/BigscreenVR/spt-progress-tool/issues/13\n #77 a commit SUBJECT naming a Request re-ships it in a later release roundup — https://github.com/BigscreenVR/spt-progress-tool/issues/77\n #78 Hub release cards bucket DONE requests by strict publish-window while the release verb honors grace — a post-publish close cascade attributes the whole milestone to the NEXT release's card — https://github.com/BigscreenVR/spt-progress-tool/issues/78\n #80 tag scanner scans on io frames (USER_INPUT / AGENT_OUTPUT close) instead of waiting for the tick — https://github.com/BigscreenVR/spt-progress-tool/issues/80","peer":"flynn"} 240 {"at_ms":1788914005322,"kind":"MSG_OUT","payload":"{\n \"as_of\": \"2026-09-09T00:33:17Z\",\n \"as_of_ms\": 1788913997787,\n \"bagged\": [\n {\n \"alchemists\": [\n {\n \"id\": 134589140258914304,\n \"name\": \"Reavo End\"\n }\n ],\n \"issue_url\": \"https://github.com/BigscreenVR/spt-progress-tool/issues/13\",\n \"number\": 13,\n \"state\": \"Backlog\",\n \"title\": \"idea: per-repo living files - issues lists for agent searches\"\n },\n {\n \"alchemists\": [\n {\n \"id\": 134589140258914304,\n \"name\": \"Reavo End\"\n }\n ],\n \"issue_url\": \"https://github.com/BigscreenVR/spt-progress-tool/issues/77\",\n \"number\": 77,\n \"state\": \"Backlog\",\n \"title\": \"a commit SUBJECT naming a Request re-ships it in a later release roundup\"\n },\n {\n \"alchemists\": [\n {\n \"id\": 134589140258914304,\n \"name\": \"Reavo End\"\n }\n ],\n \"issue_url\": \"https://github.com/BigscreenVR/spt-progress-tool/issues/78\",\n \"number\": 78,\n \"state\": \"Backlog\",\n \"title\": \"Hub release cards bucket DONE requests by strict publish-window while the release verb honors grace — a post-publish close cascade attributes the whole milestone to the NEXT release's card\"\n },\n {\n \"alchemists\": [\n {\n \"id\": 134589140258914304,\n \"name\": \"Reavo End\"\n }\n ],\n \"issue_url\": \"https://github.com/BigscreenVR/spt-progress-tool/issues/80\",\n \"number\": 80,\n \"state\": \"Backlog\",\n \"title\": \"tag scanner scans on io frames (USER_INPUT / AGENT_OUTPUT close) instead of waiting for the tick\"\n }\n ],\n \"live\": false,\n \"project\": \"BigscreenVR/spt-progress-tool\"\n}","peer":"flynn"} 241 {"at_ms":1788914198510,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-progress-tool#82 W49 — the release that claims twice, the tag that waits for a tick, the list nobody can grep — state backlog\nhttps://github.com/BigscreenVR/spt-progress-tool/issues/82","peer":"flynn"} 242 {"at_ms":1788914241591,"kind":"MSG_OUT","payload":"#13, #77, #78, #80 added to milestone BigscreenVR/spt-progress-tool#82 W49 — the release that claims twice, the tag that waits for a tick, the list nobody can grep","peer":"flynn"} 243 {"at_ms":1788916760824,"kind":"MSG_OUT","payload":"comment 5594294643 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 244 {"at_ms":1788918382487,"kind":"MSG_OUT","payload":"file 'req-boardfiles-v2.txt' staged (820 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"flynn"} 245 {"at_ms":1788918434478,"kind":"MSG_OUT","payload":"file 'req-boardfiles-v2-body.txt' staged (736 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)","peer":"flynn"} 246 {"at_ms":1788918451182,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-progress-tool#83 Board Files v2: serve them through the adapter-hosted webservice — state backlog, type idea\nhttps://github.com/BigscreenVR/spt-progress-tool/issues/83","peer":"flynn"} 247 {"at_ms":1788922010456,"kind":"MSG_OUT","payload":"comment 5594998021 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 248 {"at_ms":1788923317682,"kind":"MSG_OUT","payload":"comment 5595165611 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 249 {"at_ms":1788923512977,"kind":"MSG_OUT","payload":"comment 5595190268 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 250 {"at_ms":1788923842986,"kind":"MSG_OUT","payload":"comment 5595232807 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 251 {"at_ms":1788923857569,"kind":"MSG_OUT","payload":"BigscreenVR/spt-progress-tool#13 flags: (none)","peer":"flynn"} 252 {"at_ms":1788923920224,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-progress-tool#82 → greenlit (github open)\ncascaded to #13, #77, #78, #80","peer":"flynn"} 253 {"at_ms":1788925812591,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-progress-tool: 4 reconciled\n#80 tag scanner scans on io frames (USER_INPUT / AGENT_OUTPUT close) instead of waiting for the tick (greenlit → acceptance)\n#78 Hub release cards bucket DONE requests by strict publish-window while the release verb honors grace — a post-publish close cascade attributes the whole milestone to the NEXT release's card (greenlit → acceptance)\n#77 a commit SUBJECT naming a Request re-ships it in a later release roundup (greenlit → acceptance)\n#13 idea: per-repo living files - issues lists for agent searches (greenlit → acceptance)","peer":"flynn"} 254 {"at_ms":1788925818731,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-progress-tool#82 → acceptance (github closed, completed)\ncascaded to #13, #77, #78, #80","peer":"flynn"} 255 {"at_ms":1788925894742,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-progress-tool alchemy v0.26.0 (2026-09-09T03:50:35Z) — 5 Request(s) done:\n- #82 W50 — the release that claims twice, the tag that waits for a tick, the list nobody can grep\n- #80 tag scanner scans on io frames (USER_INPUT / AGENT_OUTPUT close) instead of waiting for the tick\n- #78 Hub release cards bucket DONE requests by strict publish-window while the release verb honors grace — a post-publish close cascade attributes the whole milestone to the NEXT release's card\n- #77 a commit SUBJECT naming a Request re-ships it in a later release roundup\n- #13 idea: per-repo living files - issues lists for agent searches\nhttps://github.com/BigscreenVR/spt-progress-tool/releases/tag/v0.26.0","peer":"flynn"} 256 {"at_ms":1788926003069,"kind":"MSG_OUT","payload":"board: the Hub Daemon has not written Board Files for BigscreenVR/spt-progress-tool on this node yet — it writes them each reconcile cycle. Check `daemon status`; if the daemon is down, that is the answer.","peer":"flynn"} 257 {"at_ms":1788926137852,"kind":"MSG_OUT","payload":"Board Files for BigscreenVR/spt-progress-tool\nas of 2026-09-09T03:52:22Z (the daemon's last cycle that changed them; not live)\n Backlog 6 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\backlog.md\n Eval 2 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\eval.md\n Greenlit 4 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\greenlit.md\n WIP 0 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\wip.md\n Acceptance 0 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\acceptance.md\n Done 58 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\done.md\n Cut 3 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\cut.md\n Shelved 0 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\shelved.md\n Milestones 9 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-progress-tool\\milestones.md","peer":"flynn"} 258 {"at_ms":1788926907005,"kind":"MSG_OUT","payload":"error: **golden is a single-line verb — unexpected extra lines","peer":"doyle"} 259 {"at_ms":1788926979564,"kind":"MSG_OUT","payload":"error: bad ref '272': expected #N, repo#N, or owner/repo#N","peer":"doyle"} 260 {"at_ms":1788927008415,"kind":"MSG_OUT","payload":"comment 5595649306 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 261 {"at_ms":1788936332840,"kind":"MSG_OUT","payload":"error: unknown flag --","peer":"doyle"} 262 {"at_ms":1788936370967,"kind":"MSG_OUT","payload":"error: comment takes 1 positional arg (got 'Golden') — the body goes on line 2 and below","peer":"doyle"} 263 {"at_ms":1788936400736,"kind":"MSG_OUT","payload":"comment 5597367744 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 264 {"at_ms":1788936677443,"kind":"MSG_OUT","payload":"comment 5597450740 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 265 {"at_ms":1788937967527,"kind":"MSG_OUT","payload":"comment 5597763072 added to BigscreenVR/spt-bs-releases#272","peer":"doyle"} 266 {"at_ms":1788943406608,"kind":"MSG_OUT","payload":"error: bad ref '272': expected #N, repo#N, or owner/repo#N","peer":"deployah"} 267 {"at_ms":1788943456939,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#272 → acceptance (github closed, completed)\ncascaded to #147, #246, #248, #249, #265, #266, #268, #17\nskipped terminal #271 (shelved)","peer":"deployah"} 268 {"at_ms":1788946652643,"kind":"MSG_OUT","payload":"comment 5599716000 added to BigscreenVR/spt-bs-releases#272","peer":"deployah"} 269 {"at_ms":1788946725728,"kind":"MSG_OUT","payload":"sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state","peer":"doyle"} 270 {"at_ms":1788946769249,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-bs-releases spt v0.68.0 (2026-09-09T09:36:41Z) — 13 Request(s) done:\n- #280 io-events: MSG_IN is never published on the `api listen` relay delivery edge (only the hook-poll drain stamps it)\n- #279 api bind prints ER_HOSTED_PROBE:no-row on every bind on a node without an engine room — a diagnostic that decides nothing reads as the refusal\n- #277 io-events seq restarts at 1 once a log passes 256KB: --after cursors go blind or replay old COMMUNE frames (wake markers refire)\n- #276 echo-commune host overwrites an agent's unread authored commune drop: one path, two writers, no arbitration\n- #272 WEBSERVE\n- #268 add: pack the changelog into the local docs\n- #266 add: spt-core daemon to host installation packages and binaries\n- #265 idea: spt-core to offer static adapter docs hosting\n- #249 feature: cross-node webserving\n- #248 feature: generalized fileserving\n- #246 endpoint-to-endpoint file transfer: spt send has no --file, and the proven xfer machinery is scoped to a node and the node DRIVING it\n- #147 idea: per-msg short ID + `spt endpoint msg <short-id> [--endpoint <id>[@<node>]] [--popup] [--json]`\n- #17 now-signal category: FILE_ACCESS_HELPER (remote-node filepath guidance)\nhttps://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.68.0","peer":"doyle"} 271 {"at_ms":1788947382639,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#290 The Served path emits no dispatch_event, so a serve cannot be attributed to a dispatcher generation. — state backlog, type addition\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/290","peer":"doyle"} 272 {"at_ms":1788947384945,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#291 Two dispatcher generations can both serve one inbound REST stream at B (overlap window). — state backlog, type addition\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/291","peer":"doyle"} 273 {"at_ms":1788947386845,"kind":"MSG_OUT","payload":"comment 5599903727 added to BigscreenVR/spt-bs-releases#289","peer":"doyle"} 274 {"at_ms":1788951318253,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"AA4KJFGD\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"deployah","msg_id":"AA4KJFGD"} 275 {"at_ms":1788955282785,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MWI5WMAB\">error: body is 1795 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it</EVENT>","peer":"doyle","msg_id":"MWI5WMAB"} 276 {"at_ms":1788955349983,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YEAH2L2N\">minted BigscreenVR/spt-bs-releases#292 A brain-only self-update leaves the resident network layer routing the OLD serve/docs surface: spt docs url 404s and serve control times out, and only one of the two says restart — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/292</EVENT>","peer":"doyle","msg_id":"YEAH2L2N"} 277 {"at_ms":1788955383931,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"33GC4B2U\">comment 5601511510 added to BigscreenVR/spt-bs-releases#292</EVENT>","peer":"doyle","msg_id":"33GC4B2U"} 278 {"at_ms":1788993671532,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3NGTHQHN\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"3NGTHQHN"} 279 {"at_ms":1788993715550,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3LJSCIP4\">comment 5609727245 added to BigscreenVR/spt-bs-releases#292</EVENT>","peer":"doyle","msg_id":"3LJSCIP4"} 280 {"at_ms":1788995664692,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EWEWARI6\">milestone BigscreenVR/spt-bs-releases#294 v0.69.0 — cross-node communication after the v0.68.0 flip (bugfix) — state backlog<br>https://github.com/BigscreenVR/spt-bs-releases/issues/294</EVENT>","peer":"doyle","msg_id":"EWEWARI6"} 281 {"at_ms":1788995748141,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PCMQV7QQ\">comment 5610035178 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"doyle","msg_id":"PCMQV7QQ"} 282 {"at_ms":1788995783395,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ZQWRBTTM\">#293, #289, #292, #287, #281, #285, #286 added to milestone BigscreenVR/spt-bs-releases#294 v0.69.0 — cross-node communication after the v0.68.0 flip (bugfix)</EVENT>","peer":"doyle","msg_id":"ZQWRBTTM"} 283 {"at_ms":1788995867312,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"7BBF3KAC\">milestone BigscreenVR/spt-bs-releases#294 → greenlit (github open)<br>cascaded to #293, #289, #292, #287, #281, #285, #286</EVENT>","peer":"doyle","msg_id":"7BBF3KAC"} 284 {"at_ms":1788995980173,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2G2HCHKM\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"deployah","msg_id":"2G2HCHKM"} 285 {"at_ms":1788996145966,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6LLY5SKT\">minted BigscreenVR/spt-bs-releases#295 `spt node status` / `spt daemon status` name a daemon pid that does not exist (stale daemon.pid after a restart) — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/295</EVENT>","peer":"doyle","msg_id":"6LLY5SKT"} 286 {"at_ms":1788996210707,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"BHYZUPMI\">#295 added to milestone BigscreenVR/spt-bs-releases#294 v0.69.0 — cross-node communication after the v0.68.0 flip (bugfix)<br>state synced: #295 backlog → greenlit</EVENT>","peer":"doyle","msg_id":"BHYZUPMI"} 287 {"at_ms":1788996211437,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"J5EJHH42\">comment 5610127841 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"doyle","msg_id":"J5EJHH42"} 288 {"at_ms":1788997569397,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"KEEE75F4\">comment 5610354880 added to BigscreenVR/spt-bs-releases#293</EVENT>","peer":"doyle","msg_id":"KEEE75F4"} 289 {"at_ms":1788997891294,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"BU7BSE2B\">comment 5610406214 added to BigscreenVR/spt-bs-releases#289</EVENT>","peer":"doyle","msg_id":"BU7BSE2B"} 290 {"at_ms":1789001202934,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MLUHMH6A\">minted BigscreenVR/spt-bs-releases#296 Checkpoint/recharge re-emits an endpoint's assistant history and re-dispatches its shortform peer tags with fresh msg-ids — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/296</EVENT>","peer":"doyle","msg_id":"MLUHMH6A"} 291 {"at_ms":1789001370176,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DZRCKATX\">comment 5610965063 added to BigscreenVR/spt-bs-releases#296</EVENT>","peer":"doyle","msg_id":"DZRCKATX"} 292 {"at_ms":1789001421326,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3CJIF2VO\">comment 5610973363 added to BigscreenVR/spt-bs-releases#296</EVENT>","peer":"doyle","msg_id":"3CJIF2VO"} 293 {"at_ms":1789021043589,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"73KGLWMJ\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"deployah","msg_id":"73KGLWMJ"} 294 {"at_ms":1789021388385,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OM5LEMHP\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"OM5LEMHP"} 295 {"at_ms":1789021494734,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"U4AZFS6A\">comment 5614144564 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"doyle","msg_id":"U4AZFS6A"} 296 {"at_ms":1789021922837,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"CHA6MFGU\">comment 5614211868 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"doyle","msg_id":"CHA6MFGU"} 297 {"at_ms":1789028148062,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"I725UYUB\">comment 5615394861 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"deployah","msg_id":"I725UYUB"} 298 {"at_ms":1789036744077,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YZHPSTNO\">comment 5617301039 added to BigscreenVR/spt-bs-releases#294</EVENT>","peer":"deployah","msg_id":"YZHPSTNO"} 299 {"at_ms":1789088561503,"kind":"MSG_OUT","payload":"[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered","peer":"doyle"} 300 {"at_ms":1789088571787,"kind":"MSG_OUT","payload":"milestone BigscreenVR/spt-bs-releases#294 → acceptance (github closed, completed)\ncascaded to #293, #289, #292, #287, #281, #285, #286, #295","peer":"deployah"} 301 {"at_ms":1789090853851,"kind":"MSG_OUT","payload":"[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered","peer":"deployah"} 302 {"at_ms":1789093591565,"kind":"MSG_OUT","payload":"release BigscreenVR/spt-bs-releases spt v0.69.0 (2026-09-11T02:25:37Z) — 9 Request(s) done:\n- #295 `spt node status` / `spt daemon status` name a daemon pid that does not exist (stale daemon.pid after a restart)\n- #294 v0.69.0 — cross-node communication after the v0.68.0 flip (bugfix)\n- #293 fix: cross-node communication is broken after v0.68.0\n- #292 A brain-only self-update leaves the resident network layer routing the OLD serve/docs surface: spt docs url 404s and serve control times out, and only one of the two says restart\n- #289 WAN request reply read has no deadline: a peer that accepts and never replies hangs the sender\n- #287 A daemon restart (no machine reboot) strands every persistent shell: the boot-restore discriminant reads the MACHINE boot instant\n- #286 Daemon stderr grows ~100 MB/day from brain-conn open/close churn\n- #285 broker.rs zombie reap kills a REMEMBERED pid without reading its image\n- #281 registry snapshot is write-only for the daemon: prune rows return from memory, a restart forgets peer endpoints until gossip\nhttps://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.69.0","peer":"deployah"} 303 {"at_ms":1789095800473,"kind":"MSG_OUT","payload":"minted BigscreenVR/spt-bs-releases#297 Windows serve lan --bootstrap leaves TCP listener inaccessible over Tailscale — state backlog, type bugfix\nhttps://github.com/BigscreenVR/spt-bs-releases/issues/297","peer":"doyle"} 304 {"at_ms":1789096618653,"kind":"MSG_OUT","payload":"error: unknown flag --bootstrap","peer":"doyle"} 305 {"at_ms":1789096631870,"kind":"MSG_OUT","payload":"alchemy — the Requests shell (GitHub Issues is the system of record)\n\npayload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.\ncreate and comment are send-only (they carry free text); every other verb runs as a `shell cmd`\nop with named args — core's `unknown op` refusal lists those ops only. composite tails ride as\none quoted string.\n\nverbs:\ncreate --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]\n title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester\n footer. An idea always mints flagged needs-operator.\ncomment #N\n body from line 2 on, appended to the referenced Request.\nview <ref> [--json]\n full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).\nlist [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]\n default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.\nstate #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved>\n any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR\n is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal\n children skipped; done never cascades). Every transition syncs GitHub open/closed +\n close reason (ADR-0004).\nmilestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]\n mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.\n add syncs a fresh joiner to the later of its own and the milestone's state,\n capped at WIP; terminal children stay put, needs-operator holds at greenlit.\nbags [--json]\n the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next\n Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.\n Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not\n hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.\nboard [--json]\n where the Hub Daemon's Board Files for the bound repo are: one Markdown file per\n State plus milestones.md, titles and facets only, rewritten only when truth changed —\n absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub\n Project on this node or the daemon has not written yet; as-of stamped, not live.\nlink #N blocks|blocked-by <ref>\n same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint\n (cross-repo dependencies are never written — ADR-0003).\ntype #N <bugfix|change|addition|feature|idea>\n FILLS a missing Type; never changes one. A Request that already carries a Type is\n refused, naming it — Type is set at mint and never changed, and the refusal is what\n holds that. For a Request hand-filed on GitHub, where the mint that guarantees a\n Type never ran. Filling idea also sets needs-operator, exactly as minting one does.\ntag #N +add -remove bare-adds\n unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.\nflag #N +needs-operator -needs-routing\n the flag: namespace tag refuses; same token grammar, this vocabulary only.\n needs-operator may be SET only in backlog/eval, and CLEARED in any state —\n clearing a stale flag is the repair. A clear records who claims the\n Operator discussion happened.\ndispatch #N <endpoint> [note]\n hands the Request to an agent: flips state: WIP, records an audit comment,\n and pushes the endpoint a durable message instructing 'fixes #N'.\nwatch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]\n registers a State-change stream (cross-repo refs legal). Default fires on every\n change, one-shot; --states narrows (and reports immediately when a named State is\n already reached/passed/unreachable); --persistent survives fires; --for seats the\n Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.\nunwatch <ref> [--for <endpoint>]\n cancels your Watches on the Request (or the named owner's, with --for).\nsweep\n reconcile merge-closes: closed-as-completed Requests still in an open-loop state\n (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.\nrelease <tag>\n promote acceptance Requests closed before the release's publish time to state: DONE\n and answer with the roundup.\nbind-repo <owner/repo>\n confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).\ndaemon [status]\n report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs\n to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);\n inspect with: spt adapter service status alchemy.\ndaemon project \"list | add | remove [owner/repo]\"\n the Hub's Project registry: add puts a repo on the Discord board (channel, State\n threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO\n repo: it registers THIS instance's bound repo, and a supplied one is refused (repo\n is never a verb argument). remove defaults to the bound repo but accepts an explicit\n ref, because a repo you can no longer bind must still be un-registerable; it\n un-registers only, and the channel and its history stay.\ndaemon setup \"[--token T] [--project owner/repo ...] [--guild N]\"\n agent-driven Discord onboarding: replies with portal instructions to relay to the\n user, validates + stores the bot token, hands back the invite link, auto-detects\n the server, and writes daemon.toml; the supervisor brings the daemon up on its next\n reconcile. Stateless — re-run anytime.\nhelp\nprocess-guide [lifecycle|operator-agent|operator-discord|shell]\n the doctrine: how the Hub is meant to be used across the Request/Milestone\n lifecycle. Bare = index of the four sections; a section token expands it.\n\nfiles: `spt shell send --file <path>` stages the file for your next create/comment.\n a create reads its TEXT as the request body (after any inline body); add --attach\n on line 1 to upload + link it as an attachment instead. a comment, or a file that\n is not text, always attaches — and the answer names a non-text reroute.\nwrite verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.\nevery write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —\nthe ack is where you learn which repo this instance is bound to.\n--json on read verbs (view, list) renders the response as machine-readable JSON.","peer":"doyle"} 306 {"at_ms":1789096641571,"kind":"MSG_OUT","payload":"comment 5628923449 added to BigscreenVR/spt-bs-releases#297","peer":"doyle"} 307 {"at_ms":1789101545148,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3WOLGJYO\">error: body is 2016 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it</EVENT>","peer":"doyle","msg_id":"3WOLGJYO"} 308 {"at_ms":1789101565838,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"NIGP54KQ\">minted BigscreenVR/spt-bs-releases#299 Diagnose endpoint list --show-all recurring ~10s stalls with complete unchanged output — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/299</EVENT>","peer":"doyle","msg_id":"NIGP54KQ"} 309 {"at_ms":1789101576023,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"L4MR2V7D\">comment 5629569142 added to BigscreenVR/spt-bs-releases#299</EVENT>","peer":"doyle","msg_id":"L4MR2V7D"} 310 {"at_ms":1789101955390,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UZIXDO22\">minted BigscreenVR/spt-bs-releases#300 Remote spt rc input bypasses FILE_ACCESS_HELPER auto-serving promised by #17 — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/300</EVENT>","peer":"doyle","msg_id":"UZIXDO22"} 311 {"at_ms":1789101981369,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RBP6FVJE\">comment 5629618668 added to BigscreenVR/spt-bs-releases#17</EVENT>","peer":"doyle","msg_id":"RBP6FVJE"} 312 {"at_ms":1789103657108,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HHXFKSAW\">comment 5629825293 added to BigscreenVR/spt-bs-releases#300</EVENT>","peer":"doyle","msg_id":"HHXFKSAW"} 313 {"at_ms":1789105524314,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OINMF7UA\">minted BigscreenVR/spt-bs-releases#303 Remote rc falsely refuses a live broker-hosted endpoint after hosting authority is lost — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/303</EVENT>","peer":"doyle","msg_id":"OINMF7UA"} 314 {"at_ms":1789105568793,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TMRJYUYK\">comment 5630071313 added to BigscreenVR/spt-bs-releases#303</EVENT>","peer":"doyle","msg_id":"TMRJYUYK"} 315 {"at_ms":1789105887737,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"N2YVOFJD\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"N2YVOFJD"} 316 {"at_ms":1789105936261,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6TCDIKDH\">comment 5630118040 added to BigscreenVR/spt-bs-releases#303</EVENT>","peer":"doyle","msg_id":"6TCDIKDH"} 317 {"at_ms":1789105951644,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2QTAQF6I\">BigscreenVR/spt-bs-releases#303 → cut (github closed, not_planned)</EVENT>","peer":"doyle","msg_id":"2QTAQF6I"} 318 {"at_ms":1789106986985,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QNTFIQSQ\">{<br> "as_of": "2026-09-11T06:08:45Z",<br> "as_of_ms": 1789106925112,<br> "bagged": [<br> {<br> "alchemists": [<br> {<br> "id": 134589140258914304,<br> "name": "Reavo End"<br> }<br> ],<br> "issue_url": "https://github.com/BigscreenVR/spt-bs-releases/issues/297",<br> "number": 297,<br> "state": "Backlog",<br> "title": "Windows serve lan --bootstrap leaves TCP listener inaccessible over Tailscale"<br> },<br> {<br> "alchemists": [<br> {<br> "id": 134589140258914304,<br> "name": "Reavo End"<br> }<br> ],<br> "issue_url": "https://github.com/BigscreenVR/spt-bs-releases/issues/299",<br> "number": 299,<br> "state": "Backlog",<br> "title": "Diagnose endpoint list --show-all recurring ~10s stalls with complete unchanged output"<br> },<br> {<br> "alchemists": [<br> {<br> "id": 134589140258914304,<br> "name": "Reavo End"<br> }<br> ],<br> "issue_url": "https://github.com/BigscreenVR/spt-bs-releases/issues/300",<br> "number": 300,<br> "state": "Backlog",<br> "title": "Remote spt rc input bypasses FILE_ACCESS_HELPER auto-serving promised by #17"<br> },<br> {<br> "alchemists": [<br> {<br> "id": 134589140258914304,<br> "name": "Reavo End"<br> }<br> ],<br> "issue_url": "https://github.com/BigscreenVR/spt-bs-releases/issues/301",<br> "number": 301,<br> "state": "Backlog",<br> "title": "fix: `localhost:5474/<node-name>/` shows \\"Served Resources\\""<br> },<br> {<br> "alchemists": [<br> {<br> "id": 134589140258914304,<br> "name": "Reavo End"<br> }<br> ],<br> "issue_url": "https://github.com/BigscreenVR/spt-bs-releases/issues/302",<br> "number": 302,<br> "state": "Backlog",<br> "title": "diagnose + fix: rc sessions frequently hitch"<br> }<br> ],<br> "live": false,<br> "project": "BigscreenVR/spt-bs-releases"<br>}</EVENT>","peer":"doyle","msg_id":"QNTFIQSQ"} 319 {"at_ms":1789106987041,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DNRL2MLQ\">{<br> "as_of": "2026-09-11T05:58:35Z",<br> "files": [<br> {<br> "as_of": "2026-09-11T05:58:35Z",<br> "count": 70,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\backlog.md",<br> "state": "Backlog"<br> },<br> {<br> "as_of": "2026-09-09T14:38:55Z",<br> "count": 26,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\eval.md",<br> "state": "Eval"<br> },<br> {<br> "as_of": "2026-09-11T01:04:42Z",<br> "count": 0,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\greenlit.md",<br> "state": "Greenlit"<br> },<br> {<br> "as_of": "2026-09-09T14:38:55Z",<br> "count": 5,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\wip.md",<br> "state": "WIP"<br> },<br> {<br> "as_of": "2026-09-11T02:28:09Z",<br> "count": 0,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\acceptance.md",<br> "state": "Acceptance"<br> },<br> {<br> "as_of": "2026-09-11T04:47:57Z",<br> "count": 170,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\done.md",<br> "state": "Done"<br> },<br> {<br> "as_of": "2026-09-11T05:52:53Z",<br> "count": 5,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\cut.md",<br> "state": "Cut"<br> },<br> {<br> "as_of": "2026-09-09T14:38:55Z",<br> "count": 1,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\shelved.md",<br> "state": "Shelved"<br> },<br> {<br> "as_of": "2026-09-11T02:28:09Z",<br> "count": 24,<br> "path": "C:\\\\Users\\\\decid\\\\.alchemy\\\\board\\\\BigscreenVR\\\\spt-bs-releases\\\\milestones.md",<br> "state": "Milestones"<br> }<br> ],<br> "live": false,<br> "project": "BigscreenVR/spt-bs-releases"<br>}</EVENT>","peer":"doyle","msg_id":"DNRL2MLQ"} 320 {"at_ms":1789107008960,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HQ5SFSPJ\">milestone BigscreenVR/spt-bs-releases#304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness — state backlog<br>https://github.com/BigscreenVR/spt-bs-releases/issues/304</EVENT>","peer":"doyle","msg_id":"HQ5SFSPJ"} 321 {"at_ms":1789107013699,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XIIJSGNQ\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"doyle","msg_id":"XIIJSGNQ"} 322 {"at_ms":1789107049348,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RQEIVLLN\">#297, #299, #300, #301, #302 added to milestone BigscreenVR/spt-bs-releases#304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness</EVENT>","peer":"doyle","msg_id":"RQEIVLLN"} 323 {"at_ms":1789107085013,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"U2T7ERLQ\">#251, #282, #288, #230, #49, #267 added to milestone BigscreenVR/spt-bs-releases#304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness</EVENT>","peer":"doyle","msg_id":"U2T7ERLQ"} 324 {"at_ms":1789107096893,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DI4GDDOT\">comment 5630275229 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"DI4GDDOT"} 325 {"at_ms":1789107410692,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VQVGX3EP\">comment 5630320712 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"VQVGX3EP"} 326 {"at_ms":1789108876884,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LMWH2S63\">comment 5630537015 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"LMWH2S63"} 327 {"at_ms":1789110340276,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RHMV6WGF\">comment 5630770542 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"RHMV6WGF"} 328 {"at_ms":1789110492784,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YDLZDK7K\">milestone BigscreenVR/spt-bs-releases#304 → greenlit (github open)<br>cascaded to #297, #299, #300, #301, #302, #251, #282, #288, #230, #49, #267</EVENT>","peer":"doyle","msg_id":"YDLZDK7K"} 329 {"at_ms":1789110647700,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"IW4TXNPY\">milestone BigscreenVR/spt-bs-releases#304 → wip (github open)<br>cascaded to #297, #299, #300, #301, #302, #251, #282, #288, #230, #49, #267</EVENT>","peer":"doyle","msg_id":"IW4TXNPY"} 330 {"at_ms":1789110664540,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EJ5FSYRQ\">comment 5630825969 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"EJ5FSYRQ"} 331 {"at_ms":1789115687262,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3BWSTC6T\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"doyle","msg_id":"3BWSTC6T"} 332 {"at_ms":1789115759617,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"F6QGT5AQ\">error: unknown milestone subcommand 'status' — create, add, or remove</EVENT>","peer":"doyle","msg_id":"F6QGT5AQ"} 333 {"at_ms":1789115829757,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UV7CGQSR\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"deployah","msg_id":"UV7CGQSR"} 334 {"at_ms":1789116083901,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OZ2JG2FR\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"OZ2JG2FR"} 335 {"at_ms":1789116252075,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ORFF5SK7\">file 'doyle-300-comment.txt' staged (1587 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"ORFF5SK7"} 336 {"at_ms":1789116297559,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WJPUC7I3\">comment 5631830252 added to BigscreenVR/spt-bs-releases#300</EVENT>","peer":"doyle","msg_id":"WJPUC7I3"} 337 {"at_ms":1789118401073,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2XPVVSDG\">comment 5632316084 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"2XPVVSDG"} 338 {"at_ms":1789121577247,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HJOKHEGS\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"HJOKHEGS"} 339 {"at_ms":1789121621738,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UDM7H5PK\">file 'board-304.txt' staged (3173 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"UDM7H5PK"} 340 {"at_ms":1789121638736,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"BWDSFZG3\">comment 5632935059 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"BWDSFZG3"} 341 {"at_ms":1789125448275,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6LQQROSE\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"6LQQROSE"} 342 {"at_ms":1789125454963,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2CP2NZRW\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"2CP2NZRW"} 343 {"at_ms":1789125583824,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O52JNONC\">comment 5633659233 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"O52JNONC"} 344 {"at_ms":1789126620969,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FJDQT4YC\">comment 5633848219 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"FJDQT4YC"} 345 {"at_ms":1789173719797,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"U3K5IB77\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"liam","msg_id":"U3K5IB77"} 346 {"at_ms":1789192091579,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"I4Z4QQQ2\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"doyle","msg_id":"I4Z4QQQ2"} 347 {"at_ms":1789273553697,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"U3DNOPZD\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"doyle","msg_id":"U3DNOPZD"} 348 {"at_ms":1789295264703,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JXZP2773\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"perri","msg_id":"JXZP2773"} 349 {"at_ms":1789295914886,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MIEW3DY5\">minted BigscreenVR/spt-bs-releases#306 Publish unlisted-peer presence from heartbeats/peer pump so endpoint list reads recent cached presence instead of dialling — state backlog, type addition<br>https://github.com/BigscreenVR/spt-bs-releases/issues/306</EVENT>","peer":"doyle","msg_id":"MIEW3DY5"} 350 {"at_ms":1789301869155,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"F5BKZ4V6\">comment 5653212174 added to BigscreenVR/spt-bs-releases#300</EVENT>","peer":"doyle","msg_id":"F5BKZ4V6"} 351 {"at_ms":1789363447326,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ECWQDDV2\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"ECWQDDV2"} 352 {"at_ms":1789363487977,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JEWYTGRC\">Board Files for BigscreenVR/spt-bs-releases<br>as of 2026-09-13T12:19:56Z (the daemon's last cycle that changed them; not live)<br> Backlog 62 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\backlog.md<br> Eval 25 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\eval.md<br> Greenlit 0 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\greenlit.md<br> WIP 16 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\wip.md<br> Acceptance 0 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\acceptance.md<br> Done 170 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\done.md<br> Cut 5 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\cut.md<br> Shelved 1 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\shelved.md<br> Milestones 25 C:\\Users\\decid\\.alchemy\\board\\BigscreenVR\\spt-bs-releases\\milestones.md</EVENT>","peer":"doyle","msg_id":"JEWYTGRC"} 353 {"at_ms":1789363489277,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"IIV62N7X\">{<br> "body": "---\\nRequester: doyle",<br> "comments": [<br> {<br> "author": "SaberMage",<br> "body": "Intake, not implementation greenlight. Operator bag retained in full: #297 #299 #300 #301 #302. Added adjacent requests: #251 safe RC viewer detach; #282 bound-port URL correctness and isolated serving acceptance; #288 accurate shell-cmd discovery; #230 visible stale-viewer version state; #49 and #267 refresh/update RC freeze reports, grouped for one RCA without assuming duplicate causes. #49 retains its prior joint-ship ruling with #42 until operator explicitly changes it. Excluded #296: comments establish omp-spt-owned replay remedy and field acceptance, not core work; #303 remains CUT and adapter-owned. No broad networking cleanup or new RC diagnostic product added implicitly. Complete infra-register sweep is running read-only; ripe riders will be recorded separately. Grill precedes final wave plan/REQ activation and implementation. Product changes go to todlando, test/CI rework to hertz, golden heads to deployah.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T06:11:34Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "Full intake infra audit complete: IR-1–54 and IR-55–97, all 97 entries accounted for including headingless IR-31. No implementation dispatched. Final rider composition and design documentation remain pending operator grill; Q1 node-root docs routing, Q2 scoped bootstrap firewall lifecycle, Q3 #49/#42 prior joint-release coupling, Q4 stale-viewer notice versus reconnection. Driver/capacity prerequisites and narrowly seam-triggered riders identified; already-built implementations must not be redispatched. Milestone remains intake/BACKLOG, not GREENLIT. Delivery, golden handoff and publish are explicitly blocked on the grill confirmation, not abandoned or completed.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T06:16:48Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "Operator grill rulings, 2026-09-11: Q1 accepted redirect /<node>/ to /<node>/docs/, retiring browser registry index; amend ADR-0056. Q2 automatic bootstrap firewall reconciliation with installation-equivalent network scope (all profiles/no remote-address restriction), actual TCP bootstrap port and executable; request Windows UAC when not elevated, Linux equivalent where available. Supersedes earlier LAN/tailnet-only and no-prompt recommendations. Docs remain loopback-only; no tailnet-policy edits. Q3 explicitly supersedes #49 joint-release coupling to #42: #49/#267 remain in this milestone; #42 stays outside absent demonstrated dependency. Q4 non-forced stale-view visibility accepted, delivered through a NEW now-signal kind. Viewer/client versus broker refresh language must distinguish the processes; restarting RC alone does not update broker code. Remaining frontier: elevation refusal behavior, exact signal scope/lifetime and infra capacity choice. Not final implementation greenlight.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T06:41:14Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "Operator accepted Q7 and Q8. ATTACH_CLIENT_STALE is governed by release-maintained minimum recommended viewer version, platform/attach-role applicability and concrete degraded-function reason; version mismatch alone and unknown version do not trigger. No forced detach. Bootstrap stop removes only owned TCP admission; listener stops even if cleanup elevation is denied, with residual-rule guidance. Q5 remains: bootstrap starts despite failed firewall repair when other startup checks pass; rerun may retry authorization. All eight product design questions answered. Final shared-understanding confirmation requested before implementation dispatch. Journal: docs/REMOTE-FRICTION-GRILL.md.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T07:05:37Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "Operator confirmed REMOTE-FRICTION and greenlit execution. All 11 members preserved in .spt/preserved/remote-friction-304/greenlit-members.json. Execution plan: docs/REMOTE-FRICTION-PLAN.md; ruled design: docs/REMOTE-FRICTION-GRILL.md. Product W1-W3 dispatched to todlando; W0 infra and regressions dispatched to hertz; doyle owns capacity/integration and deployah independent golden execution. Both owners are online; delivery confirmed, lane acknowledgements pending. Source work may start; builds require measured pool allocation and quiet/isolation preflight. Todlando is classifying his completed 293-brain target for capacity reclamation; no unowned deletion authorized. Documentation traceability check: 902/902 complete, zero findings (not milestone behavior proof). Golden candidate must include release shape and every greenlit member; no silent drops.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T07:11:01Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "W1 evidence state, 2026-09-11 09:20Z (doyle). Both lanes built into exclusive claimed pools under measured allocations; every execution one attempt, own admission sample, own census; no retries anywhere.\\n\\nhertz test lane at 96325c9b (test/304-remote-friction): spt-daemon lib 21/21 GREEN at a17dbfbd (14 webserve, shellchan vocab, six hermetic #297 bootstrap_firewall cases); docs_server_e2e GREEN at 96325c9b, REQ-WEB-URL-BOUND-PORT int EVIDENCED for the first time (earlier red was hertz's fixture binding the wrong server, withdrawn); spt bins rc detach: 3 pass, viewer_byte_detach RED and UNCLASSIFIED with the cause narrowed to a measured fact (FIN + terminal retire on the local loopback row delivers no EOF to the paired peer row's subscriber), one case not run under fail-fast. Two hertz diagnoses were withdrawn on their own discriminators before any fix landed.\\n\\ntodlando product lane at 58b95354 (feat/304-remote-friction-product): W1 #301/#282/#288/#251, #297, IR-92, #230 (doc/impl/unit green), #299 (doc/impl), #300 substrate (REQ-USER-INPUT-PATH-PROPOSAL doc/impl/unit; authorization arm unruled and inert by name). Three pure decision/IO splits landed at 3ddaae6d (windows::decide, port_from_status, may_fall_back) so hertz can author hermetic tests. REQ-ATTACH-CLIENT-STALE int MEASURED RED, classified TEST-SIDE for one path and OPEN for the other after three discriminator probes; fixed run pending. #297 int stage deactivated to W2 field acceptance on #297 (no two-machine rig yet).\\n\\nCross-lane traceability reds resolve at assembly, not per lane. Infra: IR-96 pool released (27.7 GB observed), IR-88 amended, IR-97 exclusive-execution windows applied and one crossed START recorded, IR-98 and IR-99 minted. #300 design fork awaits the operator (comment 5631830252 on #300).\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T09:19:58Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "**W1 evidence cycle, 2026-09-11 10:13Z (doyle) — runs landed, not predictions.**\\n\\nhertz window 2 @ `61bfd85c` (09:59:30Z–10:01:24Z, 114 s):\\n- producer 2 (`spt --bins` rc detach, 5 cases): **GREEN 5/5**. The three-sha `viewer_byte_detach` red is closed: a spectator subscription on a served stream is structurally impossible (one subscriber seat, healthy prior displaced, `nethost.rs:546-562`); the wire observer was deleted and the absence is asserted by consequence (`1fa4858e`).\\n- producer 3 (`webserve_e2e`, 5 cases): 4/5. Red = stale assertion at `:266` (`GET /llms.txt/` expected 200; a node root with an empty remainder is the #301 arm and now 302s). Test-only fix `4ec34d1c`, unrun.\\n- producer 4 (`attach_link_push_e2e`): **labelled hole** — measured nothing; the cross-package `mock-session` fixture was never built (cargo guarantees a package's own bins to its own tests only). Prebuild producer added for window 3.\\n- producer 5 (`webserve_cross_node_e2e`): **RED, PRODUCT.** A cross-node node-root 302 relays the OWNER's namespace: the owner rewrites the path under its own prefix (`webproxy.rs:161`), mints `Location` from its local node (`webserve.rs:778-781`), and the requester's relay copies headers verbatim with no inverse (`docshost.rs:386-389`). Exposed by #301's redirect, not introduced by it. Ruled: fix at the requester's relay, `REQ-WEB-PROXY-LOCATION-NAMESPACE`, todlando rider; hertz's cell at `:592` is the red-first int evidence and is not repinned.\\n\\n#230 (`REQ-ATTACH-CLIENT-STALE` int): the reused-op-seq replay is closed by measurement (`dfbfd287`). The next run TIMED OUT at 240 s; classified as a rig defect: `wait_for_stream` returns the first non-local stream with no exclusion, so every arm after the first re-served arm 1's retired stream — arms 2-5 had never executed, the row is UNTESTED beyond arm 1, not red. Two product mechanisms (a generation-0 misread and a wall-ms clock collision) were derived from that trace and both withdrawn; the seat-generation guard's equality behaviour is parked as an unmeasured candidate in the register, no REQ. Fix in todlando's window now (START 10:12Z).\\n\\ntraceable-reqs: the lane's 0.4.0 pin exposed two things. Nine code-stage tags quoted in prose in `docs/` (0.4.0 reads a backticked tag as a tag) — brackets elided on main `dd0679dc`. And a checker regression: 0.4.0's git enumeration skipped the `CONTEXT.md` FILE root, so 81 doc stages read as missing while 0.2.0 counted them — fixed upstream as **v0.4.1** (`d9af11d`, red-first), lane pins moved `71caedd4`. 0.4.1 on main + placement table = exit 0, zero findings.\\n\\nRegister: IR-100 third limit (builder census blind to executions), IR-102 (declared dirty file invisible to a committed-blob assignment), IR-103 (retired-object re-entry, three instances in one cell), IR-104 (checker file-root regression).\\n\\nNext on the box, sequential: todlando #230 window → hertz window 3 (fixture, producer 4, producer 3) → docs push → producer-5 product fix + one cross-node window → assembly (compile gate, traceable-reqs 0.4.1, hand to deployah). `twohost_web.rs` stays a labelled hole for the #297 two-machine leg.\\n\\nAttachments:\\n- [board-304.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1789121621310839700-board-304.txt)\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T10:13:58Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "**NEEDS-OPERATOR (by comment; the flag label refuses in WIP). Two rulings requested before any golden runs. doyle, 2026-09-11 11:20Z.**\\n\\n**Status.** W1 is integrated and gated: origin/main 6a7dd6b7 + test/304-remote-friction (carrying feat/304-remote-friction-product 3e7eaf67) = integration head d0a74461 (cargo check --workspace --all-targets exit 0; checker 0.4.1 closing to zero). Measured green: the #230 attach advisory cell (REQ-ATTACH-CLIENT-STALE int, five arms), the #301 node-root redirect repins, hertz producers 1-5, and the rider REQ-WEB-PROXY-LOCATION-NAMESPACE (a relayed 3xx Location now names the requester's label; cross-node e2e green). deployah's intake pre-check (receipts under .spt/preserved/deployah-304-intake-20260911/) holds it as an INTEGRATION head, NOT a golden candidate: 6 of 11 greenlit members (#297 #299 #300 #302 #49 #267) and the W2/W3 acceptance of #282/#288/#230 are not fulfilled on it, and this record carries no per-wave ruling.\\n\\n**Q1. Release shape.** Default under ADR-0050 is milestone-batch: no golden until all 11 members are fulfilled on one head; W1 stays integrated and W2/W3 build on top. A W1-only golden is the rejected alternative. If you want waves to ship separately for #304, say so here; otherwise no action is needed and we proceed to W2 with no golden requested.\\n\\n**Q2. W2 tailnet policy risk (#297 two-machine leg).** #297's acceptance requires a second machine (kitsubito) to GET /install over the bootstrap port on HFENDULEAM. twohost_web previously measured the tailnet ACL as ASYMMETRIC (member to tagged resource allowed, reverse denied), and kitsubito to Windows TCP is the historically denied direction. W-0 preflight (throwaway listener plus one curl, no code) runs first; if it reads BLOCKED-BY-ACL the leg is blocked on a tailnet-policy ruling that W2's mandate forbids the builders to change. Pre-authorising a scoped ACL change for the rig port, or ruling that the witness may run from another member device, would unblock it without a second round-trip.\\n\\n**Also on record.** W2 fork ruled (i): #297 closes the TCP admission axis in a new two-box binary; twohost_web's QUIC/UDP hole stays labelled as-is (a TCP green must not stand in for it). ADR-0058 Amendment 1 draft remains parked on the #300 fork.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T11:19:41Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "**Q2 DOWNGRADED by measurement (doyle, 11:38Z).** W-0 reachability preflight (todlando, 11:31-11:36Z, read-only, no product change) answered BLOCKED-BY-HOST-FIREWALL, not BLOCKED-BY-ACL:\\n- kitsubito to HFENDULEAM TCP 5470 (the live bootstrap listener) and TCP 54701 (throwaway): connect timeout, no handshake.\\n- kitsubito UDP 7470, inside the existing port+remote-scoped rule (7460-7499, RemoteIP kitsubito/32): datagram ARRIVED. UDP 9470, outside that range, same binary, same second: DROPPED.\\nSo the tailnet path is up and there is no blanket ACL deny toward this node. Admission is decided by the port+remote-scoped host rule; the program-scoped rules that name the exact binaries (\\"spt-core daemon\\", \\"Python\\") admitted nothing on this path, and the product's own \\"spt lan-bootstrap 5470\\" rule is scoped RemoteIP 192.168.1.0/24, so it cannot match a tailnet peer. That is #297's report reproduced from a second machine, and it measures ADR-0059 Amendment 2's central claim (port+remote scope works; program scope does not) before a line of product exists. Limit: an additional ACL denial on TCP is not excluded; W-1/W-2 settle it as a by-product when the product creates its port-scoped TCP rule. No operator action needed on Q2 unless W-2 reads BLOCKED-BY-ACL after that rule exists. Q1 (release shape) still open. W2 proceeds as the next wave under the milestone-batch default; no golden requested.\\n\\n*\\\\-doyle@HFENDULEAM*",<br> "created_at": "2026-09-11T11:37:00Z"<br> },<br> {<br> "author": "SaberMage",<br> "body": "**W2 STOP LINE — duplicate implementation of the #297 admission surface, gater's own IR-106 instance (doyle, 2026-09-11 12:08Z).**\\n\\n**Finding, verified at the blobs.** The W1 product lane `feat/304-remote-friction-product` @3e7eaf67 (inside integration head 0c05e722) already implements #297's TCP admission under `REQ-WEB-LAN-BOOTSTRAP-FIREWALL`: `crates/spt-daemon/src/bootstrap_firewall.rs` + `windows.rs` + `linux.rs`, call sites in lanhost/servehost/serveverb/cli, a docs-site section, ADR-0059 \\"Amendment 2\\" (d71df7aa, 07:33Z). Its Windows effector is a NetSecurity script that verifies \\"the bootstrap executable, TCP port and unrestricted scope\\" — program-scoped, all profiles, no remote restriction. At 0c05e722 it carries six unit cells (hertz 7b098cc2), all guard-level; nothing at any sha tests the rule scope. Its int stage was deactivated by me (no two-machine rig; red at 7b098cc2), obligation parked on W2 field acceptance.\\n\\nThe W2 lane `build/304-w2-bootstrap-tcp` @fe427497 (todlando, W-1 ENDed 12:06Z, arms measured: E4 mutation red at the bound-port assertion, 5/5 exact-name green, 981==981 unfiltered at that sha) implements the SAME surface a second time in `firewall.rs`: netsh, port+remote scoped (CGNAT on every profile, LocalSu","truncated":true,"peer":"doyle","msg_id":"IIV62N7X"} 354 {"at_ms":1789363489753,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"AGRF4LHY\">{<br> "body": "Operator-filed 2026-07-31 (via doyle).\\n\\nEvery active `spt rc` connection freezes whenever the daemon brain restarts under it: `spt daemon refresh` reproduces it directly, and `spt update` with a staged spt-core update (any equivalent brain-swap action) reproduces it the same way.\\n\\nThis is a LONG-STANDING bug with a failed-fix history — it has been attemptedly fixed before, more than once, and none of the attempts held. Treat every prior \\"fixed\\" claim in the history as refuted by field evidence; the RCA must explain why the prior attempts failed, not just propose another patch.\\n\\nContext the RCA should weigh (non-binding): the broker/brain split exists precisely to keep endpoints (including rc viewports) alive across a brain swap (seamless self-update architecture); rc reconnect obligations and no-endpoint-terminates-during-update obligations both exist in the registry and have shipped evidence, yet the field behavior persists — so either the contract is satisfied in test but unsound in the field path, or a different layer (viewport pump, attach lease, broker handoff) is the real owner.\\n\\nOperator sequencing ruling (2026-07-31): this Request is NOT in the current greenlit batch. It goes to a joint RCA-first lane alongside #42 (relay path RCA) AFTER the current EVAL batch (#40 #41 #43 #48) ships; fixes for both ship together from that RCA. RCA-first discipline applies (agreement-never-promotes-to-proven).\\n\\nAttachments:\\n- [mint-rc-freeze.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1785475938589153900-mint-rc-freeze.txt)\\n\\n---\\nRequester: doyle",<br> "comments": [],<br> "flags": [],<br> "issue_state": "open",<br> "number": 49,<br> "ref": "BigscreenVR/spt-bs-releases#49",<br> "state": "wip",<br> "state_reason": null,<br> "tags": [],<br> "title": "all spt rc connections freeze across `spt daemon refresh` / staged self-update restart (long-standing; prior fixes unsuccessful)",<br> "type": "bugfix",<br> "updated_at": "2026-09-11T07:10:43Z",<br> "url": "https://github.com/BigscreenVR/spt-bs-releases/issues/49"<br>}</EVENT>","peer":"doyle","msg_id":"AGRF4LHY"} 355 {"at_ms":1789363490723,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"M3TZKV4B\">{<br> "body": "also happens after `spt update`\\n\\nall PTYs recover ok **after** an intentional detach + followup `spt rc`/`spt go` back to the same endpoint session\\n\\n---\\nRequester: discord:reavo.",<br> "comments": [],<br> "flags": [],<br> "issue_state": "open",<br> "number": 267,<br> "ref": "BigscreenVR/spt-bs-releases#267",<br> "state": "wip",<br> "state_reason": null,<br> "tags": [],<br> "title": "fix: `spt daemon refresh` stalls session PTYs",<br> "type": "bugfix",<br> "updated_at": "2026-09-11T07:10:44Z",<br> "url": "https://github.com/BigscreenVR/spt-bs-releases/issues/267"<br>}</EVENT>","peer":"doyle","msg_id":"M3TZKV4B"} 356 {"at_ms":1789363491198,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"652RKBKW\">{<br> "body": "pty stream + input freezes every 10-20 seconds. the freeze lasts roughly 5-10 seconds, with all inputs enqueueing during the freeze. the whole input queue drains when it ends\\n\\ntested: enlyzeam-->gravity-nvidia-temp, enlyzeam local sessions, gravity-nvidia-temp local sessions all running spt-core v0.69.0\\n\\n---\\nRequester: discord:reavo.",<br> "comments": [],<br> "flags": [],<br> "issue_state": "open",<br> "number": 302,<br> "ref": "BigscreenVR/spt-bs-releases#302",<br> "state": "wip",<br> "state_reason": null,<br> "tags": [],<br> "title": "diagnose + fix: rc sessions frequently hitch",<br> "type": "bugfix",<br> "updated_at": "2026-09-11T07:10:38Z",<br> "url": "https://github.com/BigscreenVR/spt-bs-releases/issues/302"<br>}</EVENT>","peer":"doyle","msg_id":"652RKBKW"} 357 {"at_ms":1789363558821,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LLTDZKTN\">milestone BigscreenVR/spt-bs-releases#307 REFRESH-FREEZE & RC-HITCH remedies (fast-follow of #304) — state backlog<br>https://github.com/BigscreenVR/spt-bs-releases/issues/307</EVENT>","peer":"doyle","msg_id":"LLTDZKTN"} 358 {"at_ms":1789363594706,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JFULIFJV\">#49, #267, #302 removed from milestone BigscreenVR/spt-bs-releases#304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness</EVENT>","peer":"doyle","msg_id":"JFULIFJV"} 359 {"at_ms":1789363615911,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O5DALJVE\">#49, #267, #302 added to milestone BigscreenVR/spt-bs-releases#307 REFRESH-FREEZE & RC-HITCH remedies (fast-follow of #304)</EVENT>","peer":"doyle","msg_id":"O5DALJVE"} 360 {"at_ms":1789363640311,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PDITFE6Y\">BigscreenVR/spt-bs-releases#49 → backlog (github open)</EVENT>","peer":"doyle","msg_id":"PDITFE6Y"} 361 {"at_ms":1789363641637,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JMEDUEMG\">BigscreenVR/spt-bs-releases#267 → backlog (github open)</EVENT>","peer":"doyle","msg_id":"JMEDUEMG"} 362 {"at_ms":1789363643810,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VJXAK4RQ\">BigscreenVR/spt-bs-releases#302 → backlog (github open)</EVENT>","peer":"doyle","msg_id":"VJXAK4RQ"} 363 {"at_ms":1789363655325,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QDUR634U\">file 'comment-304.txt' staged (1300 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"QDUR634U"} 364 {"at_ms":1789363691367,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MKBW66R5\">BigscreenVR/spt-bs-releases#304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness<br>state: wip · type: ?<br>github: open · updated 2026-09-12T22:03:54Z<br>https://github.com/BigscreenVR/spt-bs-releases/issues/304<br><br>---<br>Requester: doyle<br><br>comments (46):<br>- SaberMage (2026-09-11T06:11:34Z): Intake, not implementation greenlight. Operator bag retained in full: #297 #299 #300 #301 #302. Added adjacent requests: #251 safe RC viewer detach; #282 bound-port URL correctness and isolated serving acceptance; #288 accurate shell-cmd discovery; #230 visible stale-viewer version state; #49 and #267 refresh/update RC freeze reports, grouped for one RCA without assuming duplicate causes. #49 retains its prior joint-ship ruling with #42 until operator explicitly changes it. Excluded #296: comments establish omp-spt-owned replay remedy and field acceptance, not core work; #303 remains CUT and adapter-owned. No broad networking cleanup or new RC diagnostic product added implicitly. Complete infra-register sweep is running read-only; ripe riders will be recorded separately. Grill precedes final wave plan/REQ activation and implementation. Product changes go to todlando, test/CI rework to hertz, golden heads to deployah.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T06:16:48Z): Full intake infra audit complete: IR-1–54 and IR-55–97, all 97 entries accounted for including headingless IR-31. No implementation dispatched. Final rider composition and design documentation remain pending operator grill; Q1 node-root docs routing, Q2 scoped bootstrap firewall lifecycle, Q3 #49/#42 prior joint-release coupling, Q4 stale-viewer notice versus reconnection. Driver/capacity prerequisites and narrowly seam-triggered riders identified; already-built implementations must not be redispatched. Milestone remains intake/BACKLOG, not GREENLIT. Delivery, golden handoff and publish are explicitly blocked on the grill confirmation, not abandoned or completed.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T06:41:14Z): Operator grill rulings, 2026-09-11: Q1 accepted redirect /<node>/ to /<node>/docs/, retiring browser registry index; amend ADR-0056. Q2 automatic bootstrap firewall reconciliation with installation-equivalent network scope (all profiles/no remote-address restriction), actual TCP bootstrap port and executable; request Windows UAC when not elevated, Linux equivalent where available. Supersedes earlier LAN/tailnet-only and no-prompt recommendations. Docs remain loopback-only; no tailnet-policy edits. Q3 explicitly supersedes #49 joint-release coupling to #42: #49/#267 remain in this milestone; #42 stays outside absent demonstrated dependency. Q4 non-forced stale-view visibility accepted, delivered through a NEW now-signal kind. Viewer/client versus broker refresh language must distinguish the processes; restarting RC alone does not update broker code. Remaining frontier: elevation refusal behavior, exact signal scope/lifetime and infra capacity choice. Not final implementation greenlight.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T07:05:37Z): Operator accepted Q7 and Q8. ATTACH_CLIENT_STALE is governed by release-maintained minimum recommended viewer version, platform/attach-role applicability and concrete degraded-function reason; version mismatch alone and unknown version do not trigger. No forced detach. Bootstrap stop removes only owned TCP admission; listener stops even if cleanup elevation is denied, with residual-rule guidance. Q5 remains: bootstrap starts despite failed firewall repair when other startup checks pass; rerun may retry authorization. All eight product design questions answered. Final shared-understanding confirmation requested before implementation dispatch. Journal: docs/REMOTE-FRICTION-GRILL.md.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T07:11:01Z): Operator confirmed REMOTE-FRICTION and greenlit execution. All 11 members preserved in .spt/preserved/remote-friction-304/greenlit-members.json. Execution plan: docs/REMOTE-FRICTION-PLAN.md; ruled design: docs/REMOTE-FRICTION-GRILL.md. Product W1-W3 dispatched to todlando; W0 infra and regressions dispatched to hertz; doyle owns capacity/integration and deployah independent golden execution. Both owners are online; delivery confirmed, lane acknowledgements pending. Source work may start; builds require measured pool allocation and quiet/isolation preflight. Todlando is classifying his completed 293-brain target for capacity reclamation; no unowned deletion authorized. Documentation traceability check: 902/902 complete, zero findings (not milestone behavior proof). Golden candidate must include release shape and every greenlit member; no silent drops.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T09:19:58Z): W1 evidence state, 2026-09-11 09:20Z (doyle). Both lanes built into exclusive claimed pools under measured allocations; every execution one attempt, own admission sample, own census; no retries anywhere.<br><br>hertz test lane at 96325c9b (test/304-remote-friction): spt-daemon lib 21/21 GREEN at a17dbfbd (14 webserve, shellchan vocab, six hermetic #297 bootstrap_firewall cases); docs_server_e2e GREEN at 96325c9b, REQ-WEB-URL-BOUND-PORT int EVIDENCED for the first time (earlier red was hertz's fixture binding the wrong server, withdrawn); spt bins rc detach: 3 pass, viewer_byte_detach RED and UNCLASSIFIED with the cause narrowed to a measured fact (FIN + terminal retire on the local loopback row delivers no EOF to the paired peer row's subscriber), one case not run under fail-fast. Two hertz diagnoses were withdrawn on their own discriminators before any fix landed.<br><br>todlando product lane at 58b95354 (feat/304-remote-friction-product): W1 #301/#282/#288/#251, #297, IR-92, #230 (doc/impl/unit green), #299 (doc/impl), #300 substrate (REQ-USER-INPUT-PATH-PROPOSAL doc/impl/unit; authorization arm unruled and inert by name). Three pure decision/IO splits landed at 3ddaae6d (windows::decide, port_from_status, may_fall_back) so hertz can author hermetic tests. REQ-ATTACH-CLIENT-STALE int MEASURED RED, classified TEST-SIDE for one path and OPEN for the other after three discriminator probes; fixed run pending. #297 int stage deactivated to W2 field acceptance on #297 (no two-machine rig yet).<br><br>Cross-lane traceability reds resolve at assembly, not per lane. Infra: IR-96 pool released (27.7 GB observed), IR-88 amended, IR-97 exclusive-execution windows applied and one crossed START recorded, IR-98 and IR-99 minted. #300 design fork awaits the operator (comment 5631830252 on #300).<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T10:13:58Z): **W1 evidence cycle, 2026-09-11 10:13Z (doyle) — runs landed, not predictions.**<br><br>hertz window 2 @ `61bfd85c` (09:59:30Z–10:01:24Z, 114 s):<br>- producer 2 (`spt --bins` rc detach, 5 cases): **GREEN 5/5**. The three-sha `viewer_byte_detach` red is closed: a spectator subscription on a served stream is structurally impossible (one subscriber seat, healthy prior displaced, `nethost.rs:546-562`); the wire observer was deleted and the absence is asserted by consequence (`1fa4858e`).<br>- producer 3 (`webserve_e2e`, 5 cases): 4/5. Red = stale assertion at `:266` (`GET /llms.txt/` expected 200; a node root with an empty remainder is the #301 arm and now 302s). Test-only fix `4ec34d1c`, unrun.<br>- producer 4 (`attach_link_push_e2e`): **labelled hole** — measured nothing; the cross-package `mock-session` fixture was never built (cargo guarantees a package's own bins to its own tests only). Prebuild producer added for window 3.<br>- producer 5 (`webserve_cross_node_e2e`): **RED, PRODUCT.** A cross-node node-root 302 relays the OWNER's namespace: the owner rewrites the path under its own prefix (`webproxy.rs:161`), mints `Location` from its local node (`webserve.rs:778-781`), and the requester's relay copies headers verbatim with no inverse (`docshost.rs:386-389`). Exposed by #301's redirect, not introduced by it. Ruled: fix at the requester's relay, `REQ-WEB-PROXY-LOCATION-NAMESPACE`, todlando rider; hertz's cell at `:592` is the red-first int evidence and is not repinned.<br><br>#230 (`REQ-ATTACH-CLIENT-STALE` int): the reused-op-seq replay is closed by measurement (`dfbfd287`). The next run TIMED OUT at 240 s; classified as a rig defect: `wait_for_stream` returns the first non-local stream with no exclusion, so every arm after the first re-served arm 1's retired stream — arms 2-5 had never executed, the row is UNTESTED beyond arm 1, not red. Two product mechanisms (a generation-0 misread and a wall-ms clock collision) were derived from that trace and both withdrawn; the seat-generation guard's equality behaviour is parked as an unmeasured candidate in the register, no REQ. Fix in todlando's window now (START 10:12Z).<br><br>traceable-reqs: the lane's 0.4.0 pin exposed two things. Nine code-stage tags quoted in prose in `docs/` (0.4.0 reads a backticked tag as a tag) — brackets elided on main `dd0679dc`. And a checker regression: 0.4.0's git enumeration skipped the `CONTEXT.md` FILE root, so 81 doc stages read as missing while 0.2.0 counted them — fixed upstream as **v0.4.1** (`d9af11d`, red-first), lane pins moved `71caedd4`. 0.4.1 on main + placement table = exit 0, zero findings.<br><br>Register: IR-100 third limit (builder census blind to executions), IR-102 (declared dirty file invisible to a committed-blob assignment), IR-103 (retired-object re-entry, three instances in one cell), IR-104 (checker file-root regression).<br><br>Next on the box, sequential: todlando #230 window → hertz window 3 (fixture, producer 4, producer 3) → docs push → producer-5 product fix + one cross-node window → assembly (compile gate, traceable-reqs 0.4.1, hand to deployah). `twohost_web.rs` stays a labelled hole for the #297 two-machine leg.<br><br>Attachments:<br>- [board-304.txt](https://github.com/BigscreenVR/spt-bs-releases/releases/download/untagged-3ecc0debcb4b3bffe480/shx-1789121621310839700-board-304.txt)<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T11:19:41Z): **NEEDS-OPERATOR (by comment; the flag label refuses in WIP). Two rulings requested before any golden runs. doyle, 2026-09-11 11:20Z.**<br><br>**Status.** W1 is integrated and gated: origin/main 6a7dd6b7 + test/304-remote-friction (carrying feat/304-remote-friction-product 3e7eaf67) = integration head d0a74461 (cargo check --workspace --all-targets exit 0; checker 0.4.1 closing to zero). Measured green: the #230 attach advisory cell (REQ-ATTACH-CLIENT-STALE int, five arms), the #301 node-root redirect repins, hertz producers 1-5, and the rider REQ-WEB-PROXY-LOCATION-NAMESPACE (a relayed 3xx Location now names the requester's label; cross-node e2e green). deployah's intake pre-check (receipts under .spt/preserved/deployah-304-intake-20260911/) holds it as an INTEGRATION head, NOT a golden candidate: 6 of 11 greenlit members (#297 #299 #300 #302 #49 #267) and the W2/W3 acceptance of #282/#288/#230 are not fulfilled on it, and this record carries no per-wave ruling.<br><br>**Q1. Release shape.** Default under ADR-0050 is milestone-batch: no golden until all 11 members are fulfilled on one head; W1 stays integrated and W2/W3 build on top. A W1-only golden is the rejected alternative. If you want waves to ship separately for #304, say so here; otherwise no action is needed and we proceed to W2 with no golden requested.<br><br>**Q2. W2 tailnet policy risk (#297 two-machine leg).** #297's acceptance requires a second machine (kitsubito) to GET /install over the bootstrap port on HFENDULEAM. twohost_web previously measured the tailnet ACL as ASYMMETRIC (member to tagged resource allowed, reverse denied), and kitsubito to Windows TCP is the historically denied direction. W-0 preflight (throwaway listener plus one curl, no code) runs first; if it reads BLOCKED-BY-ACL the leg is blocked on a tailnet-policy ruling that W2's mandate forbids the builders to change. Pre-authorising a scoped ACL change for the rig port, or ruling that the witness may run from another member device, would unblock it without a second round-trip.<br><br>**Also on record.** W2 fork ruled (i): #297 closes the TCP admission axis in a new two-box binary; twohost_web's QUIC/UDP hole stays labelled as-is (a TCP green must not stand in for it). ADR-0058 Amendment 1 draft remains parked on the #300 fork.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T11:37:00Z): **Q2 DOWNGRADED by measurement (doyle, 11:38Z).** W-0 reachability preflight (todlando, 11:31-11:36Z, read-only, no product change) answered BLOCKED-BY-HOST-FIREWALL, not BLOCKED-BY-ACL:<br>- kitsubito to HFENDULEAM TCP 5470 (the live bootstrap listener) and TCP 54701 (throwaway): connect timeout, no handshake.<br>- kitsubito UDP 7470, inside the existing port+remote-scoped rule (7460-7499, RemoteIP kitsubito/32): datagram ARRIVED. UDP 9470, outside that range, same binary, same second: DROPPED.<br>So the tailnet path is up and there is no blanket ACL deny toward this node. Admission is decided by the port+remote-scoped host rule; the program-scoped rules that name the exact binaries ("spt-core daemon", "Python") admitted nothing on this path, and the product's own "spt lan-bootstrap 5470" rule is scoped RemoteIP 192.168.1.0/24, so it cannot match a tailnet peer. That is #297's report reproduced from a second machine, and it measures ADR-0059 Amendment 2's central claim (port+remote scope works; program scope does not) before a line of product exists. Limit: an additional ACL denial on TCP is not excluded; W-1/W-2 settle it as a by-product when the product creates its port-scoped TCP rule. No operator action needed on Q2 unless W-2 reads BLOCKED-BY-ACL after that rule exists. Q1 (release shape) still open. W2 proceeds as the next wave under the milestone-batch default; no golden requested.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-11T12:07:42Z): **W2 STOP LINE — duplicate implementation of the #297 admission surface, gater's own IR-106 instance (doyle, 2026-09-11 12:08Z).**<br><br>**Finding, verified at the blobs.** The W1 product lane `feat/304-remote-friction-product` @3e7eaf67 (inside integration head 0c05e722) already implements #297's TCP admission under `REQ-WEB-LAN-BOOTSTRAP-FIREWALL`: `crates/spt-daemon/src/bootstrap_firewall.rs` + `windows.rs` + `linux.rs`, call sites in lanhost/servehost/serveverb/cli, a docs-site section, ADR-0059 "Amendment 2" (d71df7aa, 07:33Z). Its Windows effector is a NetSecurity script that verifies "the bootstrap executable, TCP port and unrestricted scope" — program-scoped, all profiles, no remote restriction. At 0c05e722 it carries six unit cells (hertz 7b098cc2), all guard-level; nothing at any sha tests the rule scope. Its int stage was deactivated by me (no two-machine rig; red at 7b098cc2), obligation parked on W2 field acceptance.<br><br>The W2 lane `build/304-w2-bootstrap-tcp` @fe427497 (todlando, W-1 ENDed 12:06Z, arms measured: E4 mutation red at the bound-port assertion, 5/5 exact-name green, 981==981 unfiltered at that sha) implements the SAME surface a second time in `firewall.rs`: netsh, port+remote scoped (CGNAT on every profile, LocalSubnet on Private/Domain), NEVER program-scoped, a second ADR-0059 section also titled "Amendment 2", and four newly minted ids (`REQ-LAN-BOOTSTRAP-*`). The two texts contradict each other on a fact — which rule shape admits TCP over the tailnet on this box — and an assembled head would run both start paths and write two rule sets.<br><br>**How it happened, in my name.** I ruled the W2 fork and let the four ids mint from origin/main's manifest, where the W1 id does not exist; the population that mattered was the milestone's own product lane. Same mechanism as IR-106 (a checked set is not the population), from the gater's chair. todlando found it himself at his W-1 END and did not touch either lane.<br><br>**Ruled now.** (1) No second implementation lands; neither fe427497's product bytes nor 3e7eaf67's untested Windows effector ride unmeasured. (2) W-2a, in flight (todlando, elevated netsh on HFENDULEAM, throwaway rule names, installed listener TCP 5470, fetch from kitsubito)","truncated":true,"peer":"doyle","msg_id":"MKBW66R5"} 365 {"at_ms":1789363730923,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FFIYHEZ5\">comment 5659459346 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"FFIYHEZ5"} 366 {"at_ms":1789363772361,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5ZBTDFLR\">comment 5659464087 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"doyle","msg_id":"5ZBTDFLR"} 367 {"at_ms":1789363909341,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UAUYTF3C\">comment 5659479474 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"UAUYTF3C"} 368 {"at_ms":1789363921467,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TBFKXIFK\">comment 5659480838 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"doyle","msg_id":"TBFKXIFK"} 369 {"at_ms":1789368737108,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GVZTRHKG\">file 'alchemy-297.txt' staged (1867 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"GVZTRHKG"} 370 {"at_ms":1789368737172,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"S7YLSF7E\">file 'alchemy-304.txt' staged (582 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"S7YLSF7E"} 371 {"at_ms":1789368755470,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"7HN66XYS\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"7HN66XYS"} 372 {"at_ms":1789368786970,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LHZOB3XG\">comment 5660163077 added to BigscreenVR/spt-bs-releases#297</EVENT>","peer":"doyle","msg_id":"LHZOB3XG"} 373 {"at_ms":1789368788060,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5B5VH7H3\">comment 5660163223 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"5B5VH7H3"} 374 {"at_ms":1789371776920,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"POQRY7A4\">error: <comment is a single-line verb — unexpected extra lines</EVENT>","peer":"doyle","msg_id":"POQRY7A4"} 375 {"at_ms":1789371776983,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"J2DMGLAF\">error: <comment is a single-line verb — unexpected extra lines</EVENT>","peer":"doyle","msg_id":"J2DMGLAF"} 376 {"at_ms":1789371817707,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4UURG3VX\">error: unknown verb '<comment' — try help</EVENT>","peer":"doyle","msg_id":"4UURG3VX"} 377 {"at_ms":1789371817798,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"A7DRZCSW\">error: unknown verb '<comment' — try help</EVENT>","peer":"doyle","msg_id":"A7DRZCSW"} 378 {"at_ms":1789371839996,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ZQOCCQPD\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"ZQOCCQPD"} 379 {"at_ms":1789371848717,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"SZHSQTIU\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"SZHSQTIU"} 380 {"at_ms":1789371868694,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"X34BHZU3\">comment 5660687507 added to BigscreenVR/spt-bs-releases#297</EVENT>","peer":"doyle","msg_id":"X34BHZU3"} 381 {"at_ms":1789371870536,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ONMNP4OW\">comment 5660687760 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"ONMNP4OW"} 382 {"at_ms":1789385198070,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PF6U62IR\">comment 5663194801 added to BigscreenVR/spt-bs-releases#297</EVENT>","peer":"doyle","msg_id":"PF6U62IR"} 383 {"at_ms":1789385201940,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"NMWYOCYY\">comment 5663195014 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"NMWYOCYY"} 384 {"at_ms":1789390378370,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"22M3FUFL\">comment 5664256150 added to BigscreenVR/spt-bs-releases#297</EVENT>","peer":"doyle","msg_id":"22M3FUFL"} 385 {"at_ms":1789390379435,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WIQ377XP\">comment 5664256397 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"WIQ377XP"} 386 {"at_ms":1789394239737,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3GI6IQXD\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"3GI6IQXD"} 387 {"at_ms":1789394309922,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ZTXHAJ4N\">file 'alchemy-create-registry-race.txt' staged (1654 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"ZTXHAJ4N"} 388 {"at_ms":1789394368285,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VI7X5GAP\">file 'alchemy-create-registry-race-body.txt' staged (1528 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"VI7X5GAP"} 389 {"at_ms":1789394368589,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2L5B7FZ3\">error: body is 3180 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it</EVENT>","peer":"doyle","msg_id":"2L5B7FZ3"} 390 {"at_ms":1789394397814,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GAOISTVY\">error: body is 3944 characters — a create takes at most 1600 (comments have no limit). Mint the Request with the ask itself, then `comment #N` with the detail: the discussion belongs on the Request, not inside it</EVENT>","peer":"doyle","msg_id":"GAOISTVY"} 391 {"at_ms":1789394449812,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"J62NEGJX\">comment 5665188212 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"J62NEGJX"} 392 {"at_ms":1789394453760,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"A57QBOJS\">minted BigscreenVR/spt-bs-releases#308 Serve registry lost-update: broker Attach/List and brain TTL reaper use different REGISTRY_WRITE mutexes — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/308</EVENT>","peer":"doyle","msg_id":"A57QBOJS"} 393 {"at_ms":1789394667376,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"577U3N4N\">comment 5665237597 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"577U3N4N"} 394 {"at_ms":1789394874013,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GWU2VK5Q\">comment 5665285296 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"GWU2VK5Q"} 395 {"at_ms":1789396135459,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"X6PEYF2J\">comment 5665587998 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"X6PEYF2J"} 396 {"at_ms":1789396190177,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OYHDQNEM\">comment 5665600537 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"OYHDQNEM"} 397 {"at_ms":1789398991040,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TQ6W35VF\">minted BigscreenVR/spt-bs-releases#309 Engine-room briefing lost when liveness reconciliation offlines a session that is still bringing up — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/309</EVENT>","peer":"doyle","msg_id":"TQ6W35VF"} 398 {"at_ms":1789399033285,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JP3RLCJS\">comment 5666263268 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"JP3RLCJS"} 399 {"at_ms":1789402683703,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MOUBI4IX\">comment 5667101807 added to BigscreenVR/spt-bs-releases#297</EVENT>","peer":"doyle","msg_id":"MOUBI4IX"} 400 {"at_ms":1789403111492,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O37HDSFJ\">comment 5667201851 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"O37HDSFJ"} 401 {"at_ms":1789454841081,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ED6UQEF2\">comment 5676009820 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"ED6UQEF2"} 402 {"at_ms":1789454867854,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LQSBNVDX\">comment 5676014821 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"LQSBNVDX"} 403 {"at_ms":1789458449100,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XJUNR4QB\">comment 5676665658 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"XJUNR4QB"} 404 {"at_ms":1789458491106,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"47AZR3LN\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"deployah","msg_id":"47AZR3LN"} 405 {"at_ms":1789458584159,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VGLU7DCM\">comment 5676690730 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"VGLU7DCM"} 406 {"at_ms":1789459627215,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GEMRLJXU\">comment 5676892709 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"GEMRLJXU"} 407 {"at_ms":1789459743003,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"7M6VYOWF\">comment 5676915220 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"7M6VYOWF"} 408 {"at_ms":1789460448961,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3UK7O6WL\">comment 5677053111 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"3UK7O6WL"} 409 {"at_ms":1789460516591,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O2SENWXL\">comment 5677066108 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"O2SENWXL"} 410 {"at_ms":1789462284139,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GNWQ62MT\">comment 5677419018 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"GNWQ62MT"} 411 {"at_ms":1789462600336,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"NLHWTNMA\">comment 5677482212 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"NLHWTNMA"} 412 {"at_ms":1789464757547,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5XHUCGEO\">comment 5677935370 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"5XHUCGEO"} 413 {"at_ms":1789466179295,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"P4J74NUR\">comment 5678231496 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"P4J74NUR"} 414 {"at_ms":1789467039282,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"E52M6UHD\">comment 5678415472 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"E52M6UHD"} 415 {"at_ms":1789467669108,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2M5JZAEJ\">comment 5678553909 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"doyle","msg_id":"2M5JZAEJ"} 416 {"at_ms":1789467747265,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"74LCLMJT\">comment 5678576241 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"74LCLMJT"} 417 {"at_ms":1789467801395,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"POYWORQZ\">comment 5678590885 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"POYWORQZ"} 418 {"at_ms":1789472563645,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QAAQIOQJ\">error: unknown flag --help</EVENT>","peer":"deployah","msg_id":"QAAQIOQJ"} 419 {"at_ms":1789472713322,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XQMZV7NR\">milestone BigscreenVR/spt-bs-releases#304 → acceptance (github closed, completed)<br>cascaded to #297, #299, #300, #301, #251, #282, #288, #230</EVENT>","peer":"deployah","msg_id":"XQMZV7NR"} 420 {"at_ms":1789474636784,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"SZVYOUZP\">file 'published-comment.txt' staged (908 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"deployah","msg_id":"SZVYOUZP"} 421 {"at_ms":1789474651748,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RXB4IDEL\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"RXB4IDEL"} 422 {"at_ms":1789474670159,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O73JGKNC\">comment 5680016143 added to BigscreenVR/spt-bs-releases#304</EVENT>","peer":"deployah","msg_id":"O73JGKNC"} 423 {"at_ms":1789474676520,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EMRUFEIW\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"EMRUFEIW"} 424 {"at_ms":1789474702370,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6THDAM64\">sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state</EVENT>","peer":"doyle","msg_id":"6THDAM64"} 425 {"at_ms":1789474768684,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"B763JS3U\">release BigscreenVR/spt-bs-releases spt v0.70.0 (2026-09-15T12:15:53Z) — 9 Request(s) done:<br>- #304 REMOTE-FRICTION — access, serving, roster and terminal responsiveness<br>- #301 fix: `localhost:5474/<node-name>/` shows "Served Resources"<br>- #300 Remote spt rc input bypasses FILE_ACCESS_HELPER auto-serving promised by #17<br>- #299 Diagnose endpoint list --show-all recurring ~10s stalls with complete unchanged output<br>- #297 Windows serve lan --bootstrap leaves TCP listener inaccessible over Tailscale<br>- #288 `spt shell cmd <instance> <unknown-op>` names the cmd capability set as THE shell's vocabulary, hiding every send-payload verb<br>- #282 served URLs are minted from the configured docs port, not the port the listener bound: under the rig switch they point at the live fleet daemon<br>- #251 fix: `spt rc --view` has no way to detach<br>- #230 Attach-viewer version skew after update is invisible — stale viewers replay retired bugs<br>https://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.70.0</EVENT>","peer":"doyle","msg_id":"B763JS3U"} 426 {"at_ms":1789474800528,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LJHAN22Q\">BigscreenVR/spt-bs-releases#308 Serve registry lost-update: broker Attach/List and brain TTL reaper use different REGISTRY_WRITE mutexes<br>state: backlog · type: bugfix<br>github: open · updated 2026-09-14T16:25:10Z<br>https://github.com/BigscreenVR/spt-bs-releases/issues/308<br><br>Found 2026-09-14 by the #304 Windows consumer leg on fix-2 7890ead3: spt::webserve_attachment_e2e (webserve_attachment_e2e.rs:568) lost the FIRST of two attachments from serve list --json while both ATTACHED URLs were produced. hertz RCA from source: broker Attach/List and the brain TTL reaper hold DIFFERENT process-local REGISTRY_WRITE mutexes, so the reaper can publish a stale whole-registry snapshot between two registrations. Pre-existing (6/6 green on prior legs, fix-2 diff disjoint), intermittent, contract loss not count flake. Evidence .spt/preserved/hertz-attachment-NO4JJOEL/rca-source.json. Fix shape: one shared registry write guard. Milestone home per operator ruling (stop-and-referred via lia 2026-09-14). Detail in comments.<br><br>---<br>Requester: doyle<br><br>comments (5):<br>- SaberMage (2026-09-14T14:04:25Z): Detail for the mint (doyle, 2026-09-14 ~14:10Z).<br><br>Found 2026-09-14 by the #304 Windows consumer leg on fix-2 7890ead39bb7f14ed44aaae44b0951f098ffe9ac (parent S2 527cd8e8): spt::webserve_attachment_e2e::an_attachment_is_snapshot_served_fetched_back_and_named_by_its_message red at crates/spt/tests/webserve_attachment_e2e.rs:568 — after two ATTACH calls the `serve list --json` rows carried report.md, report~1.md and beta.md but NOT alpha.md (the FIRST registration), while both ATTACHED URLs were produced and distinct. Leg record: #304 comment 5665188212; receipt .spt/preserved/304-handoff/consumer-windows-7890ead3/attempt1-receipt.txt (B exit 100, 236 passed, 3 failed — this cell plus two inject_control_wedge cells with a DIFFERENT, unclassified mechanism; not this defect).<br><br>RCA (hertz, from source; evidence .spt/preserved/hertz-attachment-NO4JJOEL/rca-source.json): the broker's Attach/List path and the brain's TTL reaper hold DIFFERENT process-local REGISTRY_WRITE mutexes, so the reaper can publish a stale whole-registry snapshot between two registrations and drop the earlier one. Mechanism proven in source; this incident's exact interleaving is inferred. Pre-existing: the cell is 6/6 green on all prior preserved Windows+Linux phase-B legs (49a08a07, S2, full49) and the fix-2 diff does not touch this path. Intermittent; rate being bounded by a 10x cohort on the exact sha (hertz, in flight) — the rate will be appended here when it lands.<br><br>Not fixture noise: the assertion names both entries (ARM11), so this is a contract loss, not the retired expired-entry count flake. Same defect class as the two-locks-one-resource hazard.<br><br>Fix shape (todlando read-only sizing, in flight): one shared registry write guard for Attach/List/reaper, or read-modify-write under a single lock. Milestone home: operator ruling pending (stop-and-referred via lia 2026-09-14 ~13:58Z on the #304 scope question: separate BUGFIX on record vs rider into v0.70.0 vs hold). doyle's recommendation on file: ship #304 on record with this defect named, fix here.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-14T14:07:50Z): Fix sizing (todlando, read-only source review at 7890ead3, 2026-09-14 14:06Z; no edits, no lane opened).<br><br>RCA CONFIRMED from source. One `REGISTRY_WRITE` declaration (crates/spt-daemon/src/servehost.rs:18-20) but two PROCESSES hold independent instances: broker `apply_at` (servehost.rs:171, arms Add/Attach/AddScoped/AddInputReference/Remove/Reconcile + List) and brain `with_registry_write` (servehost.rs:148, called from livehost.rs:1287 by the 5 s reconciliation reaper). crates/spt-store/src/serving.rs `load_at` has no lock; `save_at` serializes the WHOLE registry and atomic-renames it with no compare-and-swap — atomic publication prevents torn JSON, not lost updates. The stale-write path (brain loads R0; broker adds alpha, saves R1; brain saves its stale R0 minus the expired entry, erasing alpha; broker adds beta) reproduces the reported membership exactly. Inferred interleaving, not a captured trace. The overwrite also clobbers next_suffix and name_owners (serving.rs:126-133), so orphaned snapshot bytes and lost name-ownership history (ADR-0057 stale-link identity) are source-derived risks of the same defect.<br><br>A green 10x cohort would NOT refute this gap. ARM11's identity assertion must not be weakened or retried.<br><br>Minimal fix: ONE per-registry CROSS-PROCESS file-lock guard, owned by spt-store (serving.rs; reuse the fs2 sentinel pattern at info.rs:871-886, fs2 0.4 already a dep — no new dependency; sentinel e.g. serve/.registry.lock, derived in one owner). Acquire BEFORE the fresh load, hold through mutation, snapshot side effects/rollback and durable publication. servehost.rs drops the static mutex for the store guard (six arms keep their explicit save/error behaviour); livehost.rs acquires the same guard around reap → unlink → save. Do NOT lock only save_at (snapshot already stale), do NOT lock the registry file itself (atomic rename swaps it), do NOT unlink the sentinel on unlock, do NOT auto-save from a generic wrapper (no-op paths publish nothing). HTTP readers stay lock-free atomic snapshot reads; Docs/LAN bypasses preserved.<br><br>Blast radius: 3 runtime files (serving.rs, servehost.rs, livehost.rs) + 2 e2e files that mutate the registry under a live daemon (webserve_attachment_e2e.rs:676-708, webserve_cross_node_e2e.rs:662-762 — after ARM11, not this incident's cause) + a two-process regression replacing the two-thread test at servehost.rs:703-756 (worker-bin fixture pattern, tests/wtlock_two_process_int.rs) ≈ 8 code/manifest files + traceability/docs/changelog. No JSON schema, CLI, URL, TTL or production dependency change.<br><br>ROLLOUT CONSTRAINT: the lock coordinates only participating binaries — both broker AND brain must run the fixed implementation; an old broker with a new brain remains unsafe. Serialization can delay the brain pulse behind a large attachment save and vice versa; lock failure must stay an error, never proceed unlocked.<br><br>Milestone home: operator ruling pending (stop-and-referred via lia). No edit GO issued.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-14T14:28:54Z): Cohort (hertz, 2026-09-14 14:27Z): 10x `spt::webserve_attachment_e2e::an_attachment_is_snapshot_served_fetched_back_and_named_by_its_message` on exact 7890ead3, S2 rig, SERIALIZED single-cell load, zero SPT env knobs — 9/10 passed, 1/10 red. The red hit the same `webserve_attachment_e2e.rs:568` membership contract with the OPPOSITE survivor (beta.md lost, alpha.md kept) vs the original consumer red (alpha.md lost). Live registration loss reproduced; not the retired expired-entry count flake. Receipt: `.spt/preserved/hertz-attachment-NO4JJOEL/attachment-consumer-cohort-receipt.json`. Rate under full HEAVY parallel load (239 cells, where the original red occurred) is unmeasured; 10% is a floor per leg. Linux: 0 reds in 4 phase-B runs on the same chain (sample, not a negative; mechanism is cross-platform).<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-14T14:29:49Z): Correction to the cohort comment above (deployah precision review): 1/10 is the OBSERVED SAMPLE RATE under serialized single-cell load, not a floor. The failure probability under the golden's full HEAVY parallel load is unmeasured and is not bounded by this sample in either direction. Retry policy if the golden reds on this cell: no automatic rerun on signature match — a retry requires a recorded ruling with the original failure retained, and a later pass does not establish the defect fixed.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-14T16:25:10Z): Status 2026-09-14 16:30Z (doyle): PREP-ONLY DRAFT exists — todlando, branch `fix/308-registry-process-lock`, worktree `.worktrees/308-registry-process-lock`, base 7890ead3, uncommitted, NOT built/tested/trace-checked (no cargo of any kind ran; box was reserved for the #297 field window). Shape as sized: spt-store `serving::lock_registry_at` opens `serve/registry.lock` and takes fs2's exclusive OS lock; broker `apply_at` and the brain TTL reaper both acquire it before their fresh load and hold through publication; process-local `REGISTRY_WRITE` removed; five live-daemon E2E mutations hold the guard in narrow scopes; ARM11 untouched. New coverage drafted: fail-closed unit (`unavailable_registry_lock_cannot_publish_an_add`), two-process integration (`serving_registry_two_process_int.rs`, worker fixture) with three cases incl. abrupt-holder-exit release; obsolete two-thread sleep test removed. REQ-HAZARD-SERVE-REGISTRY-LOST-UPDATE minted; STORAGE.md + KNOWN-HAZARDS 6.14 + public serving docs drafted. 13 files, +548/−199 (tracked +231/−199 over 11 + two new files 317 lines). Rollout constraint stands: both broker and brain must run the guard. Validation and milestone home await the operator's ruling; no build GO issued.<br><br>*\\-doyle@HFENDULEAM*</EVENT>","peer":"doyle","msg_id":"LJHAN22Q"} 427 {"at_ms":1789474802068,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TS2WJWFL\">BigscreenVR/spt-bs-releases#309 Engine-room briefing lost when liveness reconciliation offlines a session that is still bringing up<br>state: backlog · type: bugfix<br>github: open · updated 2026-09-14T15:17:10Z<br>https://github.com/BigscreenVR/spt-bs-releases/issues/309<br><br>Found 2026-09-14 by the #304 Windows arm-6 consumer leg (full HEAVY phase B, golden-shape env) on fix-2 7890ead3: spt::er_briefing_presented_e2e clause 4 (er_briefing_presented_e2e.rs:782) — the new session's briefing row exists but is delivered:false at the superseding attach; 79.8 s vs 38 s pass. hertz RCA from source+log: the presentation worker's 10 s eligibility poll never sees an eligible endpoint because livehost's session poll discards the broker's bringing_up ledger and terminal-normalizes a harness that bound BEFORE the broker published its HostedSession (log: CONTROL_REAP_NO_SESSION -> LIVENESS_RECONCILE_OFFLINE -> SPAWN row_inserted 3366 ms); the 45 s test barrier then expires without retry. Pre-existing PROVEN: all 9 relevant source blobs identical S2 vs 7890ead3; fix-2 touches only bootstrap_firewall. Intermittent, load-exposed; not a test defect. Evidence .spt/preserved/hertz-attachment-NO4JJOEL/er-briefing-arm6-rca.json. Repair direction: coherent live/starting/absent observation at the spawn/reconcile authority boundary, protect false-death mutations (incl. control cleanup); NOT a longer briefing wait. Milestone home per operator ruling (with #308). Detail in comments.<br><br>---<br>Requester: doyle<br><br>comments (1):<br>- SaberMage (2026-09-14T15:17:10Z): Detail for the mint (doyle, 2026-09-14 ~15:25Z). RCA: hertz, read-only source+log, `.spt/preserved/hertz-attachment-NO4JJOEL/er-briefing-arm6-rca.json` sha256 3fc7ea651f626da5e5363a2d145ac8def8d57e0229355b0aa7b3417501de27ad.<br><br>Incident: #304 Windows consumer arm 6 (`consumer-windows-7890ead3/attempt2-phase-b.log`, full HEAVY phase B, golden-shape env, candidate 7890ead39bb7f14ed44aaae44b0951f098ffe9ac), cell 38/239 `spt::er_briefing_presented_e2e::the_engine_room_briefing_is_presented_before_the_first_actionable_turn` FAIL [79.834s], panic at `er_briefing_presented_e2e.rs:782` (REQ-ER-BRIEFING-PRESENTED clause 4). rows=[SpoolAuditRow { id: 2, from: "spt-engine-room", delivered: false, taken_leg: None, ... }] — the row exists, undelivered. Same cell PASS 38.159 s in attempt 1 and green on every prior preserved leg.<br><br>Mechanism (strong inference, not instrumented proof): the new row is composed, but the presentation worker returns BEFORE native drain because its independent 10 s eligibility poll never observes an eligible endpoint. The harness can BIND before the broker publishes its HostedSession; livehost's session poll discards the broker's `bringing_up` ledger, treats only published sessions as alive, and terminal-normalizes the bound endpoint as dead (log order: `CONTROL_REAP_NO_SESSION` → `LIVENESS_RECONCILE_OFFLINE` → `SPAWN row_inserted` at 3366 ms). WAKE_RESUME dedup does not restore online or rebind. The 45 s test barrier then expires without retrying presentation (79.834 − 38.159 = 41.7 s = the outer wait exhausting). Final `controllable=true` does not establish `online=true`. The exact offline state write and per-poll predicate values were not captured by the current diagnostics.<br><br>Pre-existing: PROVEN. `git rev-parse` blob ids for the ER test, broker, livehost, inject, info, liveness, deliver, api/startup and mock/main are identical between S2 527cd8e8 and 7890ead3 (identities retained in `er-briefing-source-and-sequence-proof.json`); fix-2's exhaustive file list is CHANGELOG.md, `crates/spt-daemon/src/bootstrap_firewall/windows.rs`, docs-site changelog, `docs/297-ENFORCEMENT-CODES-DIAGNOSIS.md`, ADR-0059, `traceable-reqs.toml`. The two `inject_control_wedge`-only deadline knobs have no path to this cell. Not a test defect; clause-4 assertions must be preserved.<br><br>Repair direction (after GO, not started): reconciliation must distinguish a legitimately STARTING session from definitive ABSENCE using coherent broker-owned lifecycle truth. A bring-up-in-flight guard is relevant, but blindly merging `bringing_up` into live sessions misstates control/liveness and is incomplete: KIND_SESSIONS snapshots session rows before reading `bringing_up`, so a publication/ledger-clear between those reads opens another gap. Define coherent live/starting/absent observation and protect false-death mutations, including control cleanup. Do NOT lengthen the briefing wait or weaken the assertions. Verification: the real broker/bind/reconcile chain with controlled pre-publication scheduling, asserting the live bound endpoint stays eligible and its briefing is taken by native-inject; capture per-predicate / terminal-normalize results at the seam.<br><br>Milestone home: operator ruling pending (with #308, stop-and-referred via lia). Sibling defects from the same leg: #308 (registry lost-update); a third (inject_control_wedge c1 give-up spool) under RCA.<br><br>*\\-doyle@HFENDULEAM*</EVENT>","peer":"doyle","msg_id":"TS2WJWFL"} 428 {"at_ms":1789522493079,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4JJ2BTOV\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"4JJ2BTOV"} 429 {"at_ms":1789522636609,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"35JNPTWW\">#308, #309 added to milestone BigscreenVR/spt-bs-releases#307 REFRESH-FREEZE & RC-HITCH remedies (fast-follow of #304)</EVENT>","peer":"doyle","msg_id":"35JNPTWW"} 430 {"at_ms":1789522684660,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5BAF7LGR\">milestone BigscreenVR/spt-bs-releases#307 → greenlit (github open)<br>cascaded to #49, #267, #302, #308, #309</EVENT>","peer":"doyle","msg_id":"5BAF7LGR"} 431 {"at_ms":1789522725270,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GPMEPB75\">comment 5690720085 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"doyle","msg_id":"GPMEPB75"} 432 {"at_ms":1789522735845,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"SSG5G6KL\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #308 'Serve registry lost-update: broker Attach/List and brain TTL reaper use different REGISTRY_WRITE mutexes' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/308<br>Dispatch note: W1a per #307 JIT plan: rebase fefc4d64 onto 289e3cdf, red-first two-process int, thin PR<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #308' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"SSG5G6KL"} 433 {"at_ms":1789522736452,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2TKLPRON\">BigscreenVR/spt-bs-releases#308 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"2TKLPRON"} 434 {"at_ms":1789522740117,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4ETBFZGR\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #49 'all spt rc connections freeze across `spt daemon refresh` / staged self-update restart (long-standing; prior fixes unsuccessful)' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/49<br>Dispatch note: W2b remedy after hertz's W1b observation rig receipt (RCA-first; must explain the failed prior fixes)<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #49' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"4ETBFZGR"} 435 {"at_ms":1789522741681,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4ZE4MTVU\">BigscreenVR/spt-bs-releases#49 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"4ZE4MTVU"} 436 {"at_ms":1789522743677,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FEP5QOMS\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #267 'fix: `spt daemon refresh` stalls session PTYs' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/267<br>Dispatch note: same lane as #49 (one root, two filings); W2b<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #267' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"FEP5QOMS"} 437 {"at_ms":1789522743745,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UOQC3MRH\">BigscreenVR/spt-bs-releases#267 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"UOQC3MRH"} 438 {"at_ms":1789523401477,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YSYY7W67\">#310 added to milestone BigscreenVR/spt-bs-releases#307 REFRESH-FREEZE & RC-HITCH remedies (fast-follow of #304)<br>state synced: #310 backlog → greenlit</EVENT>","peer":"doyle","msg_id":"YSYY7W67"} 439 {"at_ms":1789523504158,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MVFMBFGW\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #310 'fix: `spt update` concludes with outdated links' (type change).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/310<br>Dispatch note: W1d per #307 JIT plan: queued after #308 gate handoff, before #309; local docs URLs via docshost::docs_url<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #310' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"MVFMBFGW"} 440 {"at_ms":1789523504587,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4BFRWVJE\">BigscreenVR/spt-bs-releases#310 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"4BFRWVJE"} 441 {"at_ms":1789523508682,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RO42YBHX\">comment 5690823110 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"doyle","msg_id":"RO42YBHX"} 442 {"at_ms":1789524158506,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LDTNWHGW\">comment 5690901925 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"LDTNWHGW"} 443 {"at_ms":1789524258205,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VSXZHWD5\">minted BigscreenVR/spt-bs-releases#311 Sealed passage mints but exposes no token to its author (regression of #223 on 0.70.0): a sealed directive cannot be relayed to a verifier — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/311</EVENT>","peer":"doyle","msg_id":"VSXZHWD5"} 444 {"at_ms":1789524432467,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QRFJZKCN\">minted BigscreenVR/spt-bs-releases#312 spt update fetch gate keys on `gh auth status` EXIT code, so one stale stored gh account blocks the update even when a valid GH_TOKEN (or another valid account) is present — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/312</EVENT>","peer":"doyle","msg_id":"QRFJZKCN"} 445 {"at_ms":1789524490639,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4G6LKGQS\">minted BigscreenVR/spt-bs-releases#313 Access-model asymmetry: an operator-held ssh route can update/restart a host whose resident agents refuse the same operator's delegate a MESSAGE (knock pending) — the two surfaces answer to different authorities — state backlog, type change<br>https://github.com/BigscreenVR/spt-bs-releases/issues/313</EVENT>","peer":"doyle","msg_id":"4G6LKGQS"} 446 {"at_ms":1789524631091,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EBILFC74\">comment 5690960778 added to BigscreenVR/spt-bs-releases#312</EVENT>","peer":"doyle","msg_id":"EBILFC74"} 447 {"at_ms":1789524822910,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"L255BLVF\">comment 5690984742 added to BigscreenVR/spt-bs-releases#313</EVENT>","peer":"doyle","msg_id":"L255BLVF"} 448 {"at_ms":1789524947417,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"SGIQVS2S\">comment 5691002473 added to BigscreenVR/spt-bs-releases#49</EVENT>","peer":"doyle","msg_id":"SGIQVS2S"} 449 {"at_ms":1789525076917,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2F7QTITX\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"2F7QTITX"} 450 {"at_ms":1789525319493,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"F6CTFCNA\">minted BigscreenVR/spt-bs-releases#314 Fresh rc attach refuses defunct session while hosted generator remains alive — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/314</EVENT>","peer":"doyle","msg_id":"F6CTFCNA"} 451 {"at_ms":1789525319915,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LZ7G53WL\">file 'defunct-request-body.txt' staged (753 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"LZ7G53WL"} 452 {"at_ms":1789525390547,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RJZS3XOZ\">comment 5691062720 added to BigscreenVR/spt-bs-releases#314</EVENT>","peer":"doyle","msg_id":"RJZS3XOZ"} 453 {"at_ms":1789525549089,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"SAB7PME3\">comment 5691086274 added to BigscreenVR/spt-bs-releases#312</EVENT>","peer":"doyle","msg_id":"SAB7PME3"} 454 {"at_ms":1789525758929,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OMTCRFKA\">comment 5691117842 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"OMTCRFKA"} 455 {"at_ms":1789525947924,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"A7MNOIZT\">minted BigscreenVR/spt-bs-releases#315 Inbound WAN message ADMITTED while the sender's knock is still PENDING on the receiver (0.70.0 broker); the same sender was WAN_REFUSED by the 0.69.0 broker minutes earlier — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/315</EVENT>","peer":"doyle","msg_id":"A7MNOIZT"} 456 {"at_ms":1789525962718,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"7CLOZHR7\">comment 5691147375 added to BigscreenVR/spt-bs-releases#313</EVENT>","peer":"doyle","msg_id":"7CLOZHR7"} 457 {"at_ms":1789526586160,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"47V2U3XK\">comment 5691242896 added to BigscreenVR/spt-bs-releases#315</EVENT>","peer":"doyle","msg_id":"47V2U3XK"} 458 {"at_ms":1789526903908,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EOQRQS25\">comment 5691292618 added to BigscreenVR/spt-bs-releases#315</EVENT>","peer":"doyle","msg_id":"EOQRQS25"} 459 {"at_ms":1789526976683,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TPA2XVML\">comment 5691303196 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"TPA2XVML"} 460 {"at_ms":1789527118359,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LUEX7H4A\">comment 5691323505 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"LUEX7H4A"} 461 {"at_ms":1789527172454,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2NSFI2ZK\">comment 5691330935 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"2NSFI2ZK"} 462 {"at_ms":1789527249380,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"KEANIY7U\">comment 5691342938 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"KEANIY7U"} 463 {"at_ms":1789527341230,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"P3X5MQJR\">comment 5691354240 added to BigscreenVR/spt-bs-releases#315</EVENT>","peer":"doyle","msg_id":"P3X5MQJR"} 464 {"at_ms":1789527437792,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MKY55LBB\">comment 5691366552 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"MKY55LBB"} 465 {"at_ms":1789527802433,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EILGZFXV\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"EILGZFXV"} 466 {"at_ms":1789527846571,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DGOOVXAP\">comment 5691417348 added to BigscreenVR/spt-bs-releases#308</EVENT>","peer":"doyle","msg_id":"DGOOVXAP"} 467 {"at_ms":1789527848412,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6OXOL2YO\">comment 5691417538 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"6OXOL2YO"} 468 {"at_ms":1789527904244,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"R6MW3AEP\">BigscreenVR/spt-bs-releases#308 → acceptance (github closed, completed)</EVENT>","peer":"doyle","msg_id":"R6MW3AEP"} 469 {"at_ms":1789527957767,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"KUQR27E6\">comment 5691431222 added to BigscreenVR/spt-bs-releases#315</EVENT>","peer":"doyle","msg_id":"KUQR27E6"} 470 {"at_ms":1789527962326,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2SJEMEPH\">BigscreenVR/spt-bs-releases#315 flags: needs-operator</EVENT>","peer":"doyle","msg_id":"2SJEMEPH"} 471 {"at_ms":1789528835764,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"O4Q3TXIZ\">comment 5691540025 added to BigscreenVR/spt-bs-releases#314</EVENT>","peer":"doyle","msg_id":"O4Q3TXIZ"} 472 {"at_ms":1789529320333,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4ZCHSFJW\">comment 5691599796 added to BigscreenVR/spt-bs-releases#310</EVENT>","peer":"doyle","msg_id":"4ZCHSFJW"} 473 {"at_ms":1789529725508,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FDZAY5SH\">comment 5691648539 added to BigscreenVR/spt-bs-releases#314</EVENT>","peer":"doyle","msg_id":"FDZAY5SH"} 474 {"at_ms":1789530540529,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"Q2II6QFF\">comment 5691746060 added to BigscreenVR/spt-bs-releases#49</EVENT>","peer":"doyle","msg_id":"Q2II6QFF"} 475 {"at_ms":1789531162752,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"C3D7VL5V\">comment 5691820885 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"C3D7VL5V"} 476 {"at_ms":1789531253499,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"THUIPAAT\">comment 5691833899 added to BigscreenVR/spt-bs-releases#310</EVENT>","peer":"doyle","msg_id":"THUIPAAT"} 477 {"at_ms":1789531255849,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HCWRT5GV\">BigscreenVR/spt-bs-releases#310 → acceptance (github closed, completed)</EVENT>","peer":"doyle","msg_id":"HCWRT5GV"} 478 {"at_ms":1789534332890,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FT76EZAG\">comment 5692223081 added to BigscreenVR/spt-bs-releases#49</EVENT>","peer":"doyle","msg_id":"FT76EZAG"} 479 {"at_ms":1789534334618,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VSM5FTTW\">BigscreenVR/spt-bs-releases#49 → acceptance (github closed, completed)</EVENT>","peer":"doyle","msg_id":"VSM5FTTW"} 480 {"at_ms":1789534336669,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PQFYFCVK\">comment 5692223572 added to BigscreenVR/spt-bs-releases#267</EVENT>","peer":"doyle","msg_id":"PQFYFCVK"} 481 {"at_ms":1789534339324,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"VRMHXUNL\">BigscreenVR/spt-bs-releases#267 → acceptance (github closed, completed)</EVENT>","peer":"doyle","msg_id":"VRMHXUNL"} 482 {"at_ms":1789534538121,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4JPLQ7C7\">file 'alch-302.txt' staged (364 bytes) — your next create reads its text as the request body; add --attach on line 1 to link it as an attachment instead (a comment, or a file that is not text, always attaches)</EVENT>","peer":"doyle","msg_id":"4JPLQ7C7"} 483 {"at_ms":1789534562291,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FJTVGFE7\">comment 5692252097 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"FJTVGFE7"} 484 {"at_ms":1789537150275,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YIP2AVWJ\">comment 5692591125 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"YIP2AVWJ"} 485 {"at_ms":1789537150677,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WIWOTKFX\">error: #309 is state: GREENLIT — `flag: NEEDS-OPERATOR` exists only in Backlog and Eval (clearing it is legal in any State)</EVENT>","peer":"doyle","msg_id":"WIWOTKFX"} 486 {"at_ms":1789538599203,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XDXDEQFN\">comment 5692808359 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"XDXDEQFN"} 487 {"at_ms":1789538775753,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RDY7DXVR\">comment 5692840578 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"RDY7DXVR"} 488 {"at_ms":1789539541849,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"AOWGXYWL\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #309 'Engine-room briefing lost when liveness reconciliation offlines a session that is still bringing up' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/309<br>Dispatch note: product fix on hertz rig c0ef9571; receipts verified by doyle<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #309' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"AOWGXYWL"} 489 {"at_ms":1789539541944,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ARKLLEGX\">BigscreenVR/spt-bs-releases#309 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"ARKLLEGX"} 490 {"at_ms":1789539543426,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XTDRKA5H\">comment 5692962154 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"XTDRKA5H"} 491 {"at_ms":1789543903800,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"CNBGNGSD\">comment 5693715931 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"CNBGNGSD"} 492 {"at_ms":1789543907362,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5RTNP573\">BigscreenVR/spt-bs-releases#309 → acceptance (github closed, completed)</EVENT>","peer":"doyle","msg_id":"5RTNP573"} 493 {"at_ms":1789544650251,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2OPAMAGE\">comment 5693857643 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"2OPAMAGE"} 494 {"at_ms":1789546853835,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PTAZBLD7\">comment 5694369447 added to BigscreenVR/spt-bs-releases#309</EVENT>","peer":"doyle","msg_id":"PTAZBLD7"} 495 {"at_ms":1789547249041,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DYBAIR4T\">comment 5694446838 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"DYBAIR4T"} 496 {"at_ms":1789550766494,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"3ZSJE4IV\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"3ZSJE4IV"} 497 {"at_ms":1789550783676,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"P7ZQZMQW\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"P7ZQZMQW"} 498 {"at_ms":1789550834790,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HV2RCODP\">comment 5695200444 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"HV2RCODP"} 499 {"at_ms":1789634715854,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"7TQ6GALX\">comment 5711566298 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"7TQ6GALX"} 500 {"at_ms":1789635675019,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QDY4VSOS\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #302 'diagnose + fix: rc sessions frequently hitch' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/302<br>Dispatch note: STEP 2 remedy: meet-listener lifecycle off spt-broker-net + rendezvous portmapper off; field CONFIRMED via analyzer v2 (doyle 09:05Z)<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #302' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"QDY4VSOS"} 501 {"at_ms":1789635675148,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"HX77WTWT\">BigscreenVR/spt-bs-releases#302 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"HX77WTWT"} 502 {"at_ms":1789635683878,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JVFLUJMY\">comment 5711763508 added to BigscreenVR/spt-bs-releases#302</EVENT>","peer":"doyle","msg_id":"JVFLUJMY"} 503 {"at_ms":1789695923305,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"L2EWUWQC\">sweep BigscreenVR/spt-bs-releases: 1 reconciled<br>#302 diagnose + fix: rc sessions frequently hitch (wip → acceptance)</EVENT>","peer":"doyle","msg_id":"L2EWUWQC"} 504 {"at_ms":1789696681128,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"BE54MJ7I\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"deployah","msg_id":"BE54MJ7I"} 505 {"at_ms":1789698170822,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LQ5BLVD4\">[tag] digest window slid past my cursor — tags issued in the gap may have been missed; re-issue anything unanswered</EVENT>","peer":"deployah","msg_id":"LQ5BLVD4"} 506 {"at_ms":1789698518351,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4VRR3R7Z\">comment 5724230693 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"4VRR3R7Z"} 507 {"at_ms":1789705034695,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"UORJVX4L\">comment 5725074841 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"UORJVX4L"} 508 {"at_ms":1789711949443,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"T2LFQLBF\">comment 5725967377 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"T2LFQLBF"} 509 {"at_ms":1789717329456,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"74OF5KMT\">comment 5726868200 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"74OF5KMT"} 510 {"at_ms":1789718080914,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2LIPQ7CY\">comment 5726992653 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"2LIPQ7CY"} 511 {"at_ms":1789718974247,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"KMZVZN2D\">comment 5727154153 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"KMZVZN2D"} 512 {"at_ms":1789737531190,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WLIBGQ3U\">comment 5730568713 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"WLIBGQ3U"} 513 {"at_ms":1789739697222,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WNJRUILG\">comment 5731010304 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"WNJRUILG"} 514 {"at_ms":1789742697497,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"PFW3BIV2\">comment 5731672641 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"PFW3BIV2"} 515 {"at_ms":1789746662368,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6F66PGJX\">comment 5732525188 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"6F66PGJX"} 516 {"at_ms":1789750977311,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"FE7LNQ2E\">comment 5733386642 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"FE7LNQ2E"} 517 {"at_ms":1789755740441,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MRLTBEIB\">comment 5734357497 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"MRLTBEIB"} 518 {"at_ms":1789760536539,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"KRA7O7QA\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"KRA7O7QA"} 519 {"at_ms":1789764797439,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"TMJNIJSD\">sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state</EVENT>","peer":"doyle","msg_id":"TMJNIJSD"} 520 {"at_ms":1789764843209,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"F6KZLHAQ\">release BigscreenVR/spt-bs-releases spt v0.71.0 (2026-09-18T20:52:04Z) — 6 Request(s) done:<br>- #310 fix: `spt update` concludes with outdated links<br>- #309 Engine-room briefing lost when liveness reconciliation offlines a session that is still bringing up<br>- #308 Serve registry lost-update: broker Attach/List and brain TTL reaper use different REGISTRY_WRITE mutexes<br>- #302 diagnose + fix: rc sessions frequently hitch<br>- #267 fix: `spt daemon refresh` stalls session PTYs<br>- #49 all spt rc connections freeze across `spt daemon refresh` / staged self-update restart (long-standing; prior fixes unsuccessful)<br>https://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.71.0</EVENT>","peer":"doyle","msg_id":"F6KZLHAQ"} 521 {"at_ms":1789764872565,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OLQUSA7Z\">comment 5736052872 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"deployah","msg_id":"OLQUSA7Z"} 522 {"at_ms":1789765111850,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"JXRUQCHE\">BigscreenVR/spt-bs-releases#307 REFRESH-FREEZE & RC-HITCH remedies (fast-follow of #304)<br>state: greenlit · type: ?<br>github: open · updated 2026-09-18T20:54:31Z<br>https://github.com/BigscreenVR/spt-bs-releases/issues/307<br><br>---<br>Requester: doyle<br><br>comments (17):<br>- SaberMage (2026-09-14T05:29:31Z): Fast-follow of #304 (operator-ruled RELOCATE, Reavo in-session 2026-09-14 via lia). Holds the three remedy items whose DIAGNOSTICS shipped in v0.70.0 but whose fixes are unbuilt:<br><br>- #49 / #267 — rc/PTY freeze across daemon refresh / staged self-update restart. v0.70.0 shipped the two refresh-wait observability events (REQ-REFRESH-WAIT-ATTRIBUTION). Next: run the observation leg to answer Q1 (CONTROLLER_SLOT_CLOSED mapping) and Q3 (BRAIN_PROMOTE_GATE_NOT_DRAINED under a real AppliedPending trial), then design/build the fix.<br>- #302 — rc sessions hitch. v0.70.0 shipped SPT_RC_HITCH_DIAG (REQ-RC-HITCH-DISCRIMINATOR). Next: read the probe on the operator's box during a real hitch to pick #1 runtime starvation (seam B) vs #2 synchronous broker/stream wait, then build the chosen remedy.<br><br>Plan draft: .spt/preserved/304-handoff/FAST-FOLLOW-PLAN-draft.md (observation + probe procedure, conditional #302 remedy seams and guards). Not greenlit; milestone stays backlog until operator greenlights the build cycle.<br><br>-doyle@HFENDULEAM<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-14T05:32:00Z): Correction to comment 5659464087 (precision, per deployah): v0.70.0 is NOT yet published — the diagnostics (REQ-REFRESH-WAIT-ATTRIBUTION events for #49/#267; SPT_RC_HITCH_DIAG for #302) are present in the v0.70.0 CANDIDATE (asm/304-v3 @ b8482445), pending golden + publish. Read 'shipped' as 'built into the pending v0.70.0 candidate'. The relocated remedy work here at #307 is unchanged. -doyle@HFENDULEAM<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-16T01:38:44Z): # #307 JIT plan — v0.71.0 "REFRESH-FREEZE & RC-HITCH remedies" (fast-follow of #304)<br><br>doyle, 2026-09-16 01:40Z. Operator directive (2026-09-15): pull relevant/troublesome requests into #307 by doyle's judgment, plan, dispatch, drive to publish. Base: main `289e3cdf`. Target: v0.71.0 (counter 107).<br><br>## Members<br>- Carried from #304 relocation: #49, #267 (refresh freeze), #302 (rc hitch).<br>- Added 2026-09-16 by doyle's judgment (resolves the pending "milestone home" ruling both mints carried): #308 (serve-registry lost-update, prep draft `fix/308-registry-process-lock` @fefc4d64 exists), #309 (ER briefing lost when liveness reconcile offlines a bringing-up session). Both are intermittent CONTRACT losses found by the #304 consumer leg with hertz RCAs on file.<br>- Excluded on purpose: #296 (field PASS on omp-spt 0.9.2 = adapter-side; no core defect shown). #25/#263 adjacent but unscoped; stay BACKLOG.<br><br>## Waves<br>**W1 (parallel, now)**<br>- **W1a — todlando, #308.** Rebase fefc4d64 (base 7890ead3) onto 289e3cdf; build; new fail-closed unit + two-process int (`serving_registry_two_process_int.rs`) via nextest; targeted `serving`/`webserve_attachment_e2e` suites; activate the REQ stages in the same commit; traceable-reqs 0.4.1 check; thin PR. Pool: claim from the lane's own worktree.<br>- **W1b — hertz, #49/#267 observation rig (evidence, not fix).** Per `docs/49-267-REFRESH-OBSERVATION-PLAN.md` (measurement/teardown rules) + `FAST-FOLLOW-PLAN-draft.md` §1–4: isolated `SPT_HOME`, `SPT_PUMP_TRACE=1`, binary pinned by sha (main 289e3cdf build), disposable brain-owned controller/PTY with counter+generation-stamped output, real `spt daemon refresh`; capture `CONTROLLER_SLOT_CLOSED` (Q1) and `BRAIN_PROMOTE_GATE_NOT_DRAINED` (Q3). Q3 needs a real `AppliedPending` trial — report BLOCKED if not admittable, never fabricate. Bound 300 s + 120 s teardown. Output: receipt + RCA candidate that explains why prior fixes failed.<br>- **W1c — hertz, #302 discriminator.** Isolated-home daemon on hfenduleam (NEVER the resident fleet daemon), local rc session, `SPT_RC_HITCH_DIAG=1 spt node status --json` during healthy/hitch/recovery; the five-line cadence experiment ONLY on the isolated home. Plus: doyle asks lia to authorize ball-b (ENLYZEAM) to run the read-only probe on the operator's box during a real hitch. Output: #1 (runtime starvation: seconds-stale canary + hitch-correlated dials) vs #2 (synchronous broker/stream wait: fresh canary).<br><br>**W2 (after W1 receipts)**<br>- **W2a — todlando, #309.** Coherent live/starting/absent observation at the spawn/reconcile authority boundary: livehost session poll honours the broker's `bringing_up` ledger; false-death mutations (incl. control cleanup) protected. NOT a longer briefing wait. Red-first unit on the reconcile arm + `er_briefing_presented_e2e` clause 4 green. hertz: regression cell hardening if the e2e needs a deterministic barrier.<br>- **W2b — todlando, #49/#267 remedy** from the W1b RCA (RCA-first; agreement never promotes to proven). hertz: regression cell on the W1b rig. Rider if the path is touched: IR-82 (daemon.pid predecessor/death record, todlando-owned).<br>- **W2c — todlando, #302 remedy** per W1c: seam B (dials quarantined behind `NetHost`, connections handed to the serving executor BEFORE `register_conn`) if #1; if #2, establish the rc dependency before any remedy. hertz: proof with unchanged gauges (`.spt/preserved/302/REMEDY-DESIGN.md`).<br><br>**W3 — assembly.** doyle assembles the golden head (merge chain off current main, compile-gate + traceable check), hands to deployah; deployah verifies GREENLIT FORM (every member fulfilled or relocated-with-reason on the issue) → golden → publish v0.71.0. Red → doyle RCA-first triage.<br><br>## Gate discipline (every lane)<br>Isolated worktree under `.worktrees/`, own pool claim, targeted suites + compile-gate, `traceable-reqs check` exit 0, ff-only landing of the tested sha, co-author trailer space spelling. Register sweep at intake done (hertz, 82333ca1; IR-86 retired, IR-11 built).<br><br>## One decision that may come back to the operator<br>#302's remedy cannot be CHOSEN without a field reading. If W1c yields neither an hfenduleam repro nor an operator-box reading, #302 RELOCATES (never drops) with the reason on the issue before golden. Everything else proceeds without operator input.<br><br>## Pre-flight (role discipline)<br>Cost: W1a ~1 lane-day (prep exists); W1b/W1c ~half-day each, light rigs. Box: hfenduleam runner idle (last run 289e3cdf 15:54Z), 182 GB free (above the 128 GiB golden floor, but tight — reap own retired targets before golden). Parallel fill: all three W1 legs run concurrently; todlando's cargo vs hertz's single isolated daemon = CPU contention only.<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-16T01:51:46Z): **Addendum 2026-09-16 01:50Z (doyle):** operator added #310 to this milestone (`spt update` concludes with outdated links; small product change). Lane W1d on todlando, queued after #308 is handed to gate and before #309. Sites: `crates/spt/src/cli.rs` RELEASES_URL (3 uses) + `UPDATE_DOCS_LANDED` print, `crates/spt-daemon/src/notif.rs` CONSENT_CHANGELOG_URL; helper already exists (`spt_daemon::docshost::docs_url(node, port)`, `cli::resolved_docs_url`). Operator also authorized ball-b read-only SPT_RC_HITCH_DIAG readings on ENLYZEAM and the ssh route decid@enlyzeam (read-only) for the #302 discriminator (W1c).<br><br>*\\-doyle@HFENDULEAM*<br>- SaberMage (2026-09-18T02:28:37Z): #307 golden intake GO: first release-shaped successor f348ed0c189b5e8c0c07d15a71aa609a5c1cf19d of 712c987f. Scope exactly #49 #267 #302 #308 #309 #310; all ACCEPTANCE/closed, parity against greenlight record 5690720085 + addendum 5690823110; no drops/adds. v0.71.0 workspace, 14 workspace-only lock changes, user-facing notes and generated docs. Own binary renders spt 0.71.0; xtask gen/check pass; traceable-reqs 926/926 zero findings. Counter 107 decoded from prior signed 106. Compatibility constants unchanged; minor version justified by disabling automatic router mappings across all endpoints. All six fix commits since ddd7fc7f map to notes; remaining commits are infrastructure/tests/docs.<br>Superseding intake artifact .spt/preserved/307/GOLDEN-INTAKE-712c987f.md sha256 a4b9fd5f382edef63e7f89632bebdd8490f815c76b8c4b9b05982f2c934a3fe2; carry its named cells and stale-consumer risks, NOT earlier superseded summaries. Six new integration cells across four binaries have zero golden CI denominator. Table enumerates six unit rows (its seven-unit/13-total summary is an arithmetic mismatch). Red => doyle RCA; no automatic rerun authority.<br>Admission after shaping: Windows 157806415872 B free (floor 137438953472), Linux 190460243968 B (floor 130000000000). Main thin CI 35296537885 success; no active cargo/Runner.Worker in sampled census, two operator IDE rust-analyzers untouched. Own pool released. No discarded shape this cycle. Golden/tag target frozen to this exact successor; no post-golden edits. Evidence .spt/preserved/307/deployah-intake/.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T04:17:14Z): Golden 35299506382 CLOSED_RED on f348ed0c189b5e8c0c07d15a71aa609a5c1cf19d; zero retries. Terminal jobs 8 success / 1 failure: sole failure Windows test job 105459081284, Phase B refresh_freeze (241/242 passed; Phase A 3471/3471). Both paired legs SUCCESS: twohost-a 105473277032, twohost-b 105473276934. Doyle ruling: TEST-CEILING, one 2016ms tag exceeds 2000ms; no same-SHA rerun. Await landed predicate fix then fresh release shape on main, not discarded f348ed0c. No main advance, tag, or publication. Full job log + decoded receipt .spt/preserved/307/golden-35299506382/deployah-{windows-job.log,refresh-receipt.json}; terminal snapshot .spt/preserved/307/deployah-intake/golden-final.json.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T06:12:29Z): #307 respin intake GO: fresh v0.71.0 shape aa8a297866a831e2eb87101d16f610baf4d51e3e, direct successor of 0ab1e48b7c4cf4c16e0e46c14b415ff28bbc8f5c. Discarded first shape f348ed0c is NOT an ancestor (merge-base exit 1). Same six ACCEPTANCE children, no scope changes. Delta since prior code head: 046bad44/0ab1e48b, three test/support files only; new Windows HEAVY integration wrapper refresh_ack_policy_distinguishes_jitter_from_stalls joins the live refresh cell. Carry named consumer-risk inventory from GOLDEN-INTAKE-712c987f.md with doyle's respin handoff; first run remains CLOSED_RED, not erased.<br>Own binary renders spt 0.71.0; xtask gen/check pass; traceability 926/926 zero findings; 14 workspace-only lock version changes, no third-party changes. Same reviewed notes, counter 107 (prior signed 106), unchanged compatibility constants. Main post-merge CI 35311316391 success. Post-build Windows sample 158477783040 bytes free (>137438953472); Linux 190440181760 (>130000000000). No active repo runs, no cargo/Runner.Worker; operator IDE analyzers untouched. Own pool released. Freeze this exact head for golden and any release; red returns to doyle, no automatic retry. Evidence .spt/preserved/307/deployah-intake-r2/.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T07:42:09Z): Golden #2 35313912102 CLOSED_RED on aa8a297866a831e2eb87101d16f610baf4d51e3e. Doyle RCA ruling: PRODUCT defect — liveness reconciliation offlined the UNBOUND resume row during run2 spawn; CLI resume lacks custody for the DEFER arm, and preserved session_id lets the CAS pass. RCA: .spt/preserved/307/golden-35313912102/RCA-resume-unbound.md. Sole Windows Phase B red: rc_attach_truth::resume_never_bound_reads_unbound_and_attaches at line 500. Phase A 3471/3471; Phase B 242/243. Both refresh_freeze cells passed. Zero retries; same-SHA rerun refused. Remaining jobs are being allowed to finish. No tag/publication; r2 pool retained. Await gated fix landing, then fresh v0.71.0 shape excluding discarded heads. Raw evidence: .spt/preserved/307/golden-35313912102/deployah-windows-job.log.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T07:54:40Z): Addendum to CLOSED_RED comment 5726868200: doyle identified a second mechanism in golden #2 (35313912102), a CI job-graph defect. twohost-a started 10m39s after twohost-b because Windows n1-gate occupied its runner; missing n1-gate dependency let the Linux rendezvous expire. RCA: .spt/preserved/307/golden-35313912102/RCA-twohost-b.md. This is separate from the resume PRODUCT defect in RCA-resume-unbound.md. twohost-a mirrored failure is predicted, not yet asserted here. Hertz owns paired-job needs:[test,n1-gate]; todlando owns resume custody fix. Both must land on one gated successor before fresh shaping/golden. No same-SHA rerun, tag, or publication; r2 pool retained.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T08:09:32Z): Golden #2 35313912102 now TERMINAL failure on aa8a297866a831e2eb87101d16f610baf4d51e3e: six jobs success, three failure (Windows test 105501438554; twohost-a 105517287267; twohost-b 105517287374). twohost-a actually failed at twohost.rs:1969: pairing never completed within the rig window; twohost-b at twohost.rs:544: never converged, A rostered via daemon-hosted responder. Both full logs preserved in .spt/preserved/307/golden-35313912102/deployah-twohost-{a,b}.log. Two mechanisms per doyle rulings already recorded: resume PRODUCT defect and paired-job CI dependency defect. Zero retries. r2 pool retained. No tag/publication. Await both gated fixes on one successor; fresh shape will exclude both discarded shapes.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T13:18:50Z): #307 golden #3 intake GO: fresh shape b25b2b770e8fadb3e08356032bab3eb335538599, direct successor of 71165e3540295d7b7b9af98d6e1a06163261b0cc. Both discarded shapes f348ed0c and aa8a2978 proven NOT ancestors. Six greenlit members unchanged, all ACCEPTANCE: #49 #267 #302 #308 #309 #310. Both prior reds remain CLOSED_RED. Successor carries CLI spawn custody fix and needs:[test,n1-gate] on both twohost roles. New custody integration cells have local gate evidence per doyle handoff; full golden is next CI-depth proof. User notes include custody fix. v0.71.0 rendered by own binary, gen/check pass, traceability 927/927 zero findings. Lock diff remains 14 workspace-only version changes, compatibility constants unchanged, counter 107 (prior106).<br>Post-merge CI35339675565 classified VOID by doyle: 40-minute cap during Complete job, 3254/3254 passed, all steps/floor/cleanup successful; RCA .spt/preserved/307/deployah-intake-r3/RCA-postmerge-35339675565-void.md. Explicit GO received after desktop load ceased. Fresh post-build disk: Windows145018585088 B >137438953472; Linux258026504192 B >130000000000. No active repo runs or sampled cargo/Runner.Worker; two IDE analyzers untouched. Pool released. IR-142 acceptance will record both startedAt timestamps, gap and conclusions. Freeze this SHA; red to doyle RCA-first. A future cap cancellation needs observed returning desktop load for the specific VOID rerun ruling, not a blanket retry. Evidence .spt/preserved/307/deployah-intake-r3/.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T13:54:54Z): Golden #3 35349501073 CLOSED_RED on b25b2b770e8fadb3e08356032bab3eb335538599. Doyle RCA: PRODUCT ordering defect in listen relay — stdout emitted before MSG_IN journal publication (REQ-IO-MSG-EDGES); not #234 and not load-manufactured. RCA .spt/preserved/307/golden-35349501073/RCA-linux-relay-msg-in-race.md. Linux Phase A 3427/3428 passed; sole failure io_events_undriven_kinds_e2e::relay_backlog_and_live_deliveries_stamp_once_even_after_hook_poll at line818. Raw log deployah-linux-job.log in same directory. Remaining Windows/twohost jobs continue for evidence; IR-142 acceptance pending actual startedAt timestamps and conclusions. Zero reruns, no tag/publication. R2 pool retained. Await gated listen-relay fix landing on main, then fresh r4 shape excluding all discarded shapes.<br><br>*\\-deployah@HFENDULEAM*<br>- SaberMage (2026-09-18T14:44:57Z): Golden #3 (35349501073, b25b2b770e8fadb3e08356032bab3eb335538599) Windows test job105614091181: VOID-with-green-content per doyle ruling. Every step succeeded through Complete job at14:39:57Z; 80-minute job cap marked it cancelled at80m28s. This is NOT a Windows test failure and NOT full ","truncated":true,"peer":"doyle","msg_id":"JXRUQCHE"} 523 {"at_ms":1789765192021,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ROVFQMAG\">BigscreenVR/spt-bs-releases#307 → done (github closed, completed)</EVENT>","peer":"doyle","msg_id":"ROVFQMAG"} 524 {"at_ms":1789765212966,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4BCEBQ7M\">comment 5736114965 added to BigscreenVR/spt-bs-releases#307</EVENT>","peer":"doyle","msg_id":"4BCEBQ7M"} 525 {"at_ms":1790026811610,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DPYQPPHQ\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"DPYQPPHQ"} 526 {"at_ms":1790026817598,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"A4CDCO44\">alchemy — the Requests shell (GitHub Issues is the system of record)<br><br>payload shape (`spt shell send`): line 1 = verb + flags · line 2 = title (create) · rest = body.<br>create and comment are send-only (they carry free text); every other verb runs as a `shell cmd`<br>op with named args — core's `unknown op` refusal lists those ops only. composite tails ride as<br>one quoted string.<br><br>verbs:<br>create --type <bugfix|change|addition|feature|idea> [--needs-operator] [--needs-routing]<br> title on line 2, body from line 3. Mints the Request at state: BACKLOG with a Requester<br> footer. An idea always mints flagged needs-operator.<br>comment #N<br> body from line 2 on, appended to the referenced Request.<br>view <ref> [--json]<br> full facts + comments. refs: #N (bound repo) · repo#N (bound account) · owner/repo#N (any).<br>list [--state S] [--type T] [--flag F] [--tag G] [--all] [--json]<br> default open-minus-shelved, sorted by last activity. --all keeps shelved and closed.<br>state #N <backlog|eval|greenlit|wip|acceptance|done|cut|shelved><br> any jump, except greenlit: milestone-level only, and never while flag: NEEDS-OPERATOR<br> is set. A milestone's greenlit/wip/acceptance cascades to live sub-issues (terminal<br> children skipped; done never cascades). Every transition syncs GitHub open/closed +<br> close reason (ADR-0004).<br>milestone create <title> | milestone add|remove <mref> <ref1>[,<ref2>…]<br> mints a kind: MILESTONE issue / attaches or detaches Requests as native sub-issues.<br> add syncs a fresh joiner to the later of its own and the milestone's state,<br> capped at WIP; terminal children stay put, needs-operator holds at greenlit.<br>bags [--json]<br> the Requests currently bagged (🎒) in Discord — every Alchemist's Bag for their next<br> Milestone — grouped by Alchemist and by State, either grouping omitted when uniform.<br> Read from the index the Hub Daemon writes each cycle, NOT from GitHub, which does not<br> hold Bags; the answer states its as-of time, so it is cycle-fresh rather than live.<br>board [--json]<br> where the Hub Daemon's Board Files for the bound repo are: one Markdown file per<br> State plus milestones.md, titles and facets only, rewritten only when truth changed —<br> absolute paths, so the next move is grep. Refuses by name when the repo is not a Hub<br> Project on this node or the daemon has not written yet; as-of stamped, not live.<br>link #N blocks|blocked-by <ref><br> same-repo: native GitHub dependency. foreign ref: reference comment + a Watch hint<br> (cross-repo dependencies are never written — ADR-0003).<br>type #N <bugfix|change|addition|feature|idea><br> FILLS a missing Type; never changes one. A Request that already carries a Type is<br> refused, naming it — Type is set at mint and never changed, and the refusal is what<br> holds that. For a Request hand-filed on GitHub, where the mint that guarantees a<br> Type never ran. Filling idea also sets needs-operator, exactly as minting one does.<br>tag #N +add -remove bare-adds<br> unprefixed labels only — state:/type:/flag:/kind: namespaces are reserved.<br>flag #N +needs-operator -needs-routing<br> the flag: namespace tag refuses; same token grammar, this vocabulary only.<br> needs-operator may be SET only in backlog/eval, and CLEARED in any state —<br> clearing a stale flag is the repair. A clear records who claims the<br> Operator discussion happened.<br>dispatch #N <endpoint> [note]<br> hands the Request to an agent: flips state: WIP, records an audit comment,<br> and pushes the endpoint a durable message instructing 'fixes #N'.<br>watch <ref> [--states s1,s2] [--persistent] [--for <endpoint>]<br> registers a State-change stream (cross-repo refs legal). Default fires on every<br> change, one-shot; --states narrows (and reports immediately when a named State is<br> already reached/passed/unreachable); --persistent survives fires; --for seats the<br> Watch on another endpoint. Fires arrive as durable spt messages from the Hub Daemon.<br>unwatch <ref> [--for <endpoint>]<br> cancels your Watches on the Request (or the named owner's, with --for).<br>sweep<br> reconcile merge-closes: closed-as-completed Requests still in an open-loop state<br> (backlog/eval/greenlit/wip) move to state: ACCEPTANCE.<br>release <tag><br> promote acceptance Requests closed before the release's publish time to state: DONE<br> and answer with the roundup.<br>bind-repo <owner/repo><br> confirm this instance's bound repo (validates token + repo, bootstraps reserved labels).<br>daemon [status]<br> report the node-local Hub Daemon (daemon.toml in the config dir). Lifecycle belongs<br> to spt's supervisor — alchemy no longer starts, stops or restarts it (v0.5.0);<br> inspect with: spt adapter service status alchemy.<br>daemon project "list | add | remove [owner/repo]"<br> the Hub's Project registry: add puts a repo on the Discord board (channel, State<br> threads, Watch polling) live on the daemon's next cycle — no restart. add takes NO<br> repo: it registers THIS instance's bound repo, and a supplied one is refused (repo<br> is never a verb argument). remove defaults to the bound repo but accepts an explicit<br> ref, because a repo you can no longer bind must still be un-registerable; it<br> un-registers only, and the channel and its history stay.<br>daemon setup "[--token T] [--project owner/repo ...] [--guild N]"<br> agent-driven Discord onboarding: replies with portal instructions to relay to the<br> user, validates + stores the bot token, hands back the invite link, auto-detects<br> the server, and writes daemon.toml; the supervisor brings the daemon up on its next<br> reconcile. Stateless — re-run anytime.<br>help<br>process-guide [lifecycle|operator-agent|operator-discord|shell]<br> the doctrine: how the Hub is meant to be used across the Request/Milestone<br> lifecycle. Bare = index of the four sections; a section token expands it.<br><br>files: `spt shell send --file <path>` stages the file for your next create/comment.<br> a create reads its TEXT as the request body (after any inline body); add --attach<br> on line 1 to upload + link it as an attachment instead. a comment, or a file that<br> is not text, always attaches — and the answer names a non-text reroute.<br>write verbs (create, comment, state, tag) take bare #N refs only; foreign refs are view-only.<br>every write verb ANSWERS with the qualified ref (owner/repo#N) even though it took a bare one —<br>the ack is where you learn which repo this instance is bound to.<br>--json on read verbs (view, list) renders the response as machine-readable JSON.</EVENT>","peer":"doyle","msg_id":"A4CDCO44"} 527 {"at_ms":1790026837549,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"RGYSR3UT\">minted BigscreenVR/spt-bs-releases#316 Resume brief served a stale LLM-echo project tier although the agent's fresh commune was ingested — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/316</EVENT>","peer":"doyle","msg_id":"RGYSR3UT"} 528 {"at_ms":1790029482863,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LNYSIB75\">alchemy process guide — how the Requests Hub is meant to be used.<br>Expand a section: process-guide <section><br><br>lifecycle<br> The intended flow, no usage advice: a Request from Seed to Done, the<br> Milestone that groups Requests for a release, and the release that ships them.<br>operator-agent<br> What to ask your agent for at each point in the flow — directional tips<br> and prompt starters for the Operator.<br>operator-discord<br> The top-level Discord features — Seeds, Type reactions, the Bag, the<br> staging post, card controls, threads — and when to use each.<br>shell<br> Everything an agent needs to drive alchemy for a consistent Requests<br> flow: payload shapes, ref grammar, ack policy, and which verb belongs<br> to which stage.</EVENT>","peer":"doyle","msg_id":"LNYSIB75"} 529 {"at_ms":1790029501821,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"IY7SGLJ5\">comment 5768362088 added to BigscreenVR/spt-bs-releases#317</EVENT>","peer":"doyle","msg_id":"IY7SGLJ5"} 530 {"at_ms":1790029509436,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5X56UMON\">milestone BigscreenVR/spt-bs-releases#318 HANDED-FILE — a file the operator hands an agent arrives, once, with the prompt (#317) + signal-truth riders — state backlog<br>https://github.com/BigscreenVR/spt-bs-releases/issues/318</EVENT>","peer":"doyle","msg_id":"5X56UMON"} 531 {"at_ms":1790029532414,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GPXTBR6C\">#317, #254, #311, #312 added to milestone BigscreenVR/spt-bs-releases#318 HANDED-FILE — a file the operator hands an agent arrives, once, with the prompt (#317) + signal-truth riders</EVENT>","peer":"doyle","msg_id":"GPXTBR6C"} 532 {"at_ms":1790029533488,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"2QBQZ3GB\">comment 5768367416 added to BigscreenVR/spt-bs-releases#318</EVENT>","peer":"doyle","msg_id":"2QBQZ3GB"} 533 {"at_ms":1790029548340,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"4QN37PDA\">milestone BigscreenVR/spt-bs-releases#318 → greenlit (github open)<br>cascaded to #317, #254, #311, #312</EVENT>","peer":"doyle","msg_id":"4QN37PDA"} 534 {"at_ms":1790029598534,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"ZAUO77F3\">DISPATCH from doyle via alchemy (BigscreenVR/spt-bs-releases): Request #317 'fix: filepaths with spaces do not trigger now-signal's `FILE_ACCESS_HELPER`' (type bugfix).<br>https://github.com/BigscreenVR/spt-bs-releases/issues/317<br>Dispatch note: W1 quoted-span paths + line dedupe, then W2 second audience + with-prompt delivery; plan .spt/preserved/318/JIT-PLAN.md<br>You are expected to implement this Request and reference it in the implementing commit or PR with 'fixes #317' so merge-close flows back to the Hub. Comment progress on the issue.</EVENT>","peer":"todlando","msg_id":"ZAUO77F3"} 535 {"at_ms":1790029598645,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"CVCU2D6F\">BigscreenVR/spt-bs-releases#317 → dispatched to todlando (github open)<br>push to todlando: accepted</EVENT>","peer":"doyle","msg_id":"CVCU2D6F"} 536 {"at_ms":1790029639664,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"D6SEVG6Y\">minted BigscreenVR/spt-bs-releases#319 FILE_ACCESS_HELPER never fires for a second endpoint when the quoted path is already served — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/319</EVENT>","peer":"doyle","msg_id":"D6SEVG6Y"} 537 {"at_ms":1790029656487,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"WSELKWEK\">#319 added to milestone BigscreenVR/spt-bs-releases#318 HANDED-FILE — a file the operator hands an agent arrives, once, with the prompt (#317) + signal-truth riders<br>state synced: #319 backlog → greenlit</EVENT>","peer":"doyle","msg_id":"WSELKWEK"} 538 {"at_ms":1790029657459,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"YLYIOADY\">comment 5768387503 added to BigscreenVR/spt-bs-releases#318</EVENT>","peer":"doyle","msg_id":"YLYIOADY"} 539 {"at_ms":1790034929753,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"5L47GFBV\">comment 5769251872 added to BigscreenVR/spt-bs-releases#317</EVENT>","peer":"doyle","msg_id":"5L47GFBV"} 540 {"at_ms":1790035914272,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"EB2IK3FZ\">minted BigscreenVR/spt-bs-releases#320 Peer-delivered text re-encoded with XML entities escapes core's input-provenance exclusion, so the controller's node serves a file on a peer's say-so — state backlog, type bugfix<br>https://github.com/BigscreenVR/spt-bs-releases/issues/320</EVENT>","peer":"doyle","msg_id":"EB2IK3FZ"} 541 {"at_ms":1790035942716,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XRLI3ISW\">#320 added to milestone BigscreenVR/spt-bs-releases#318 HANDED-FILE — a file the operator hands an agent arrives, once, with the prompt (#317) + signal-truth riders<br>state synced: #320 backlog → greenlit</EVENT>","peer":"doyle","msg_id":"XRLI3ISW"} 542 {"at_ms":1790035943395,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"LB7AHKDJ\">comment 5769389874 added to BigscreenVR/spt-bs-releases#318</EVENT>","peer":"doyle","msg_id":"LB7AHKDJ"} 543 {"at_ms":1790039553104,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"QPWA47EQ\">comment 5769829686 added to BigscreenVR/spt-bs-releases#318</EVENT>","peer":"doyle","msg_id":"QPWA47EQ"} 544 {"at_ms":1790040231479,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"MXGYKUIW\">comment 5769904355 added to BigscreenVR/spt-bs-releases#318</EVENT>","peer":"doyle","msg_id":"MXGYKUIW"} 545 {"at_ms":1790043063861,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"OV7XJARP\">comment 5770237352 added to BigscreenVR/spt-bs-releases#254</EVENT>","peer":"doyle","msg_id":"OV7XJARP"} 546 {"at_ms":1790047018129,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"DCTXXZCZ\">comment 5770708375 added to BigscreenVR/spt-bs-releases#312</EVENT>","peer":"doyle","msg_id":"DCTXXZCZ"} 547 {"at_ms":1790048739517,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"6IBJZFCE\">comment 5770908392 added to BigscreenVR/spt-bs-releases#311</EVENT>","peer":"doyle","msg_id":"6IBJZFCE"} 548 {"at_ms":1790058380378,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"AURU67HD\">error: bad ref '318': expected #N, repo#N, or owner/repo#N</EVENT>","peer":"deployah","msg_id":"AURU67HD"} 549 {"at_ms":1790058415723,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"XBOMXCA5\">milestone BigscreenVR/spt-bs-releases#318 → acceptance (github closed, completed)<br>cascaded to #317, #254, #311, #312, #319, #320</EVENT>","peer":"deployah","msg_id":"XBOMXCA5"} 550 {"at_ms":1790058614895,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"GEVFIQGK\">sweep BigscreenVR/spt-bs-releases: nothing to reconcile — no merge-closed Requests in an open-loop state</EVENT>","peer":"doyle","msg_id":"GEVFIQGK"} 551 {"at_ms":1790058648796,"kind":"MSG_OUT","payload":"<EVENT type=\"msg\" from=\"alchemy-0\" msg-id=\"NCTFO5ZD\">release BigscreenVR/spt-bs-releases spt v0.72.0 (2026-09-22T06:29:16Z) — 7 Request(s) done:<br>- #320 Peer-delivered text re-encoded with XML entities escapes core's input-provenance exclusion, so the controller's node serves a file on a peer's say-so<br>- #319 FILE_ACCESS_HELPER never fires for a second endpoint when the quoted path is already served<br>- #318 HANDED-FILE — a file the operator hands an agent arrives, once, with the prompt (#317) + signal-truth riders<br>- #317 fix: filepaths with spaces do not trigger now-signal's `FILE_ACCESS_HELPER`<br>- #312 spt update fetch gate keys on `gh auth status` EXIT code, so one stale stored gh account blocks the update even when a valid GH_TOKEN (or another valid account) is present<br>- #311 Sealed passage mints but exposes no token to its author (regression of #223 on 0.70.0): a sealed directive cannot be relayed to a verifier<br>- #254 spt-shells deprecation gate is inert on 2 of 3 session-start paths: cmd_bind and cmd_boundary resolve no manifest, so a compliance-declaring adapter still gets the legacy row<br>https://github.com/BigscreenVR/spt-bs-releases/releases/tag/v0.72.0</EVENT>","peer":"doyle","msg_id":"NCTFO5ZD"}