Repository navigation
feat(soc-optimization-unified): targets[] expansion and per-action dispatch mode in SOCCommandWrapper - #1199
Merged
Merged
Conversation
…spatch mode in SOCCommandWrapper Two registry-row fields, both optional, neither an operator setting: - target_arg names the inline arg that carries the thing being acted on. When its context reference resolves to a list, the wrapper dispatches once per element instead of stringifying the list into one garbage value - the multi-domain bug. One approval upstream covers the run. - dispatch: all_applicable dispatches every vendor branch the action declares, each checked and recorded on its own; one vendor failing cannot kill the rest. Absent means routed: the original ladder, unchanged. The single-vendor single-target path is the original main() body moved into _dispatch_one with terminal semantics preserved - same war-room entries, same records, same return_error/raise - so every existing action behaves byte-for-byte as before. Per-(vendor,target) execution records and dataset rows carry target/action_target; a dispatch summary war-room entry appears only when a run fans out. Tests: 9 new cases (fan-out matrix, dedupe, failure isolation, shadow per-pair, legacy equivalence pins); 6 fail on the pre-change code, 3 pin equivalence. Existing suites pass unchanged; the 9 pre-existing detonate-file failures are identical on main and here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X6z5STKWCdm3aN5XwxWpgz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two optional registry-row fields on
SOCFrameworkActions_V3entries — zero operator-facing settings, absent = today's behavior byte-for-byte:target_arg— names the inline arg carrying the thing acted on. A context reference resolving to a list dispatches once per element (kills the multi-domain stringify bug); scalars unchanged. One approval upstream covers the whole run.dispatch: all_applicable— dispatches every vendor branch the action declares, each checked/recorded on its own; one vendor failing cannot kill the rest;return_erroronly when every dispatch failed. Absent/unknown =routed(the original ladder, untouched).Per-(vendor,target) execution records and dataset rows (
target/action_target); a dispatch-summary war-room entry only when a run fans out. First consumers: soc-block-domain, then the partner's phishing purge.Testing
soc-star-caseshadow wrapper row per issue, shape identical to the pre-change rows from yesterday's identical replay (1494772/73) → war-room entry profile identical. No dispatch summary emitted on legacy paths, as designed.🤖 Generated with Claude Code
https://claude.ai/code/session_01X6z5STKWCdm3aN5XwxWpgz