Advertise the C29 authoring surfaces: description slot in introspect, op reference in help, guide-literal guard #323
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fieldtest findings of the self-description cycle (#316, consumer-seat run 2026-07-23). The C29 gates work and their refusals are comprehensible, but the authoring side of the new surfaces is not yet advertised where a headless agent (#319) would look — three concrete gaps, the documentation half of which already landed with the cycle (guide op table, README op list, surface-neutral refusal hint):
process/campaign introspect --unwiredomit thedescriptionslot. Both listings enumerate every other slot — including optional ones (risk, cost) in per-knob detail — but not the C29 field itself. Add a slot line:description (optional, one-line meaning; C29-gated when present)to both document kinds.doc) live only in repo docs;aura graph build --help/graph introspectshould carry an op reference so the register refusal's fix is discoverable from the binary alone.NodeSchema.doc(hard E0063 for anyone pasting it; fixed in the cycle) — compile the guide literal in a test (doctest or a fixture extraction) so the worked example cannot drift from the schema again.All three serve the same promise the milestone closes on: the binary as the only always-present teacher.
Binary-only field evidence (milestone fieldtest, 2026-07-24)
The "Surface honesty on stderr" milestone fieldtest ran source-blind — knowledge floor = the release binary and its own help surfaces, per the user's 2026-07-23 direction. Directly relevant to this issue's ask:
aura graph build --helpdocuments nothing about the stdin op-list. The fieldtester could author blueprints only by feeding malformed JSON and reading serde refusals; the op kinds (source|input|add|feed|connect|expose|tap|gang|doc) and per-op fields (op/type/role/kind/into/from/to/as/bind/text) are otherwise invisible from the binary.graph build --help(or agraph introspect --opslisting kinds + fields + one worked element each) is the missing piece that would have made blueprint authoring self-serve.The adjacent silent-unknown-field defect found on the same runs is filed separately as #326 (a typo'd
paramsinstead ofbindsilently drops the binding).Shipped in the same commit as #315 (
829a198, branchworktree-issue-315-help-self-description):process|campaign introspect --unwiredenumerate the optionaldescriptionenvelope slot for both document kinds (absent-only, the risk/cost precedent). The risk/cost-bound e2e now also bindsdescription, so its "no open slots" keeps meaning complete.aura graph build --helpcarries the op-list reference — all nine op kinds with fields and a worked element each (OP_REFERENCElives besideOpDoc, one screen from the enum).LIB_RStemplate (rendered with the guide'smy_labnamespace); the scaffold e2es compile that template for real, so the equality pin is a transitive compile guard — the literal can no longer drift silently from the schema.closes #323fires on the owner-ratified merge.