From d65b6ca029146b6eae087160b7f24b7729eb6ad1 Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Wed, 22 Jul 2026 00:43:35 -0700 Subject: [PATCH] Name the sandbox cause in the degraded seed and suggest a network retry Co-Authored-By: Claude Fable 5 --- skill/scripts/concept-seed.mjs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/skill/scripts/concept-seed.mjs b/skill/scripts/concept-seed.mjs index 93ad63a66..caeddebc6 100644 --- a/skill/scripts/concept-seed.mjs +++ b/skill/scripts/concept-seed.mjs @@ -458,7 +458,10 @@ ASSIGNED INDEX: ${buildIndex} The assignment exists to refuse the model's ranking rut, never to outrank the user or the brief. Never expose assignment metadata in user-facing labels. No challengers this run: the roll service was unreachable and no local -catalog exists. Proceed with the grounded candidates alone; the assignment +catalog exists. A sandboxed shell without network egress is the most common +cause: if this harness can rerun the command with network access granted, +do that once before proceeding. Otherwise proceed with the grounded +candidates alone; the assignment above still applies at full strength. Tell the user plainly that this roll ran degraded, with no challengers and no quality-bar boards; do not present the outcome as a full roll. A degraded roll changes the cards, not the