[GH-ISSUE #5490] [Feature] Add manifest-driven batch mode for independent offline artifact inspections #3344

Open
opened 2026-10-31 00:39:21 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5490

Problem

Analysts often need to inspect several local artifacts with the same command. Running each separately makes repeatable inventories and CI automation verbose, while one failed item can make it harder to see which other inputs completed successfully.

Proposed change

Add an opt-in CLI batch mode for independent, offline artifact inspections driven by a caller-supplied manifest. This is distinct from batching several tool calls within one live provider session: each manifest entry should be a separate local inspection with explicit per-item status.

Acceptance criteria

  • The manifest schema is documented and validates all entries before starting work.
  • Each item returns its own result or typed error; one invalid item does not silently erase successful sibling results.
  • Concurrency is bounded and configurable within safe defaults.
  • Output includes stable input identifiers and never claims a failed or skipped item was inspected.
  • The initial scope excludes target execution and interactive providers; these can be considered separately.
  • Tests cover empty manifests, duplicate IDs, mixed success/failure, and deterministic result ordering.

This is an optional workflow request, not a claim that single-artifact commands are broken.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5490 ### Problem Analysts often need to inspect several local artifacts with the same command. Running each separately makes repeatable inventories and CI automation verbose, while one failed item can make it harder to see which other inputs completed successfully. ### Proposed change Add an opt-in CLI batch mode for independent, offline artifact inspections driven by a caller-supplied manifest. This is distinct from batching several tool calls within one live provider session: each manifest entry should be a separate local inspection with explicit per-item status. ### Acceptance criteria - The manifest schema is documented and validates all entries before starting work. - Each item returns its own result or typed error; one invalid item does not silently erase successful sibling results. - Concurrency is bounded and configurable within safe defaults. - Output includes stable input identifiers and never claims a failed or skipped item was inspected. - The initial scope excludes target execution and interactive providers; these can be considered separately. - Tests cover empty manifests, duplicate IDs, mixed success/failure, and deterministic result ordering. This is an optional workflow request, not a claim that single-artifact commands are broken.
Author
Owner

@matbrgz commented on GitHub (Oct 20, 2026):

Cross-referencing with canonical feature #5481 and siblings #5482-#5489. Forms part of the headless CLI batch inspection, structured I/O, and streaming suite. Cataloged under Cluster AV in consolidation tracker #4330.

<!-- gh-comment-id:6292623001 --> @matbrgz commented on GitHub (Oct 20, 2026): Cross-referencing with canonical feature #5481 and siblings #5482-#5489. Forms part of the headless CLI batch inspection, structured I/O, and streaming suite. Cataloged under Cluster AV in consolidation tracker #4330.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#3344
No description provided.