Expand V1 API-test coverage from the single seed flow to the remaining detected resources. Use this AFTER devloop_mutation_demo has surfaced a positive catch result for the FIRST resource — that's the "manufactured proof" gate the dev needed before agreeing to scale.
Returns a procedure that loops over the dev-approved candidates:
for each resource:
devloop_generate_resource_flow(app_id, resource, app_dir, base_url)
ASK dev: continue / stop / pick a different resource
end
Mutation demo is NOT in the per-resource loop. Once a session has seen
mutation_demo run on the seed resource and prove its catch behavior,
re-firing it for every new resource produces busywork. The dev opts in
to mutation-on-expanded-resources via the post-expand multi-option
menu (see DevloopInstructionsAddendum "After devloop_expand_coverage"),
not as a default step inside this loop. If the dev asks "mutate this
too" mid-expand, fine — fire devloop_mutation_demo on that resource
on demand.
Stop conditions:
* Dev says "stop" / "enough" / "later" → exit cleanly.
* Any generate step errors → surface to dev, ASK whether to retry, skip, or stop.
DO NOT silently run all candidates without dev confirmation per
resource — the DEVLOOP decision-gate defaults explicitly require an
opt-in between each resource, because (a) the dev may want to inspect
each test before approving the next, and (b) a tangentially-named
candidate may be the wrong fit and the dev wants to swap.