graph introspect --taps: positive declared-tap discovery view #337
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?
#333 shipped the refusal-roster half (the undeclared-tap refusal enumerates declared taps) and deliberately deferred the introspect view "until authoring (rather than recovery) turns out to need one" (decision comment there). The harvest-sweep fieldtest supplied that evidence immediately: a blueprint's declared tap names have no POSITIVE discovery surface —
graph introspecthas no--taps,--unwiredis silent about taps — so the only way to learn them without opening the blueprint JSON is deliberately provoking the undeclared-tap refusal. The fold half of the discovery loop is self-guiding; the tap half is recovery-only.Ask:
aura graph introspect --taps <bp.json>— one row per declared tap: name + source wire (node.field) + column kind, doc-gated per C29's view idiom. Same line as the fold-selector fieldtest's finding on #333; also adjacent to the M6 tap work (#312/#327) but a pure graph-surface view, independent of the registry path.Corpus: fieldtests/harvest-sweep/hs_1_discovery.ops.json / hs_3_three_taps.ops.json.