Skip to content

fix(author): route 3 tries the two files wherever Node runs, whatever the code tool says about the internet - #212

Merged
alekswebnet merged 2 commits into
mainfrom
fix/author-route3-always-tries
Nov 16, 2026
Merged

alekswebnet merged 2 commits into
mainfrom
fix/author-route3-always-tries

Conversation

@alekswebnet

@alekswebnet alekswebnet commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Closes #211.

Since 0.10.0, step 3 took "no internet" from the chat's own tools and then skipped route 3, the two files from the organisation's site. Grok documents its code tool as having no network, yet the tool fetches the site (v24.15.0, 200), so Grok handed over the JSON source unless the build archive was attached.

  • SKILL.md: the Internet answer is gone. Step 3 finds one answer, whether npm reaches its registry, which a chat with no code tool does not. Route 3 now reads "Node runs here", and says to try it even where the tools say there is no internet or npm gave up.
  • two-files.md: where neither file arrives, the route has failed, so the next one is taken.
  • design/author.md: the step 3 bullet and two measurement bullets are updated, and a new rule, A code tool that says it has no internet still tries the two files, holds the Grok finding and the numbers below.

Measured on Haiku

Each run's prompt said the code tool's sandbox has no internet access.

Sandbox Runs Result
npm hangs, the web is reachable (as Grok) 3 All took route 3, fetched both files, and built packages that pass the verifier here, each marked unverified
Nothing reachable 2 Both gave the json block, which builds and passes, plus the .source.json file equal to it and the archive line

One Grok-like run first ran route 1's find / for an archive nobody had attached, which ran to the code tool's 110 seconds on this computer's disk. (Corrected after the merge: this line first said the verifier's npx had hung in that run. That was a check of mine in the run's folder, not the run's.)

Three earlier runs were not counted because the lab leaked. npm answered from this computer's cache with no network, and one run working in a subfolder escaped the dead registry. The design record now holds the full recipe: a package.json, a .npmrc naming a dead or hanging registry, and a cache of the run's own.


Summary by cubic

Closes #211. Since 0.10.0, step 3 took "no internet" from the chat's own tools and then skipped route 3, although Grok's code tool—documented as having no network—fetches the organisation's site (v24.15.0, 200), so Grok handed over the JSON source unless the build archive was attached.

Now step 3 checks only whether npm reaches its registry, and route 3 is tried wherever Node runs, even when the tools say there is no internet or npm gave up.

  • SKILL.md: the Internet answer is gone; route 3 reads "Node runs here" and says to try it despite tool claims or npm failure.
  • two-files.md: when neither file arrives, the route is treated as failed and the next one is taken.
  • design/author.md: updated the step 3 and measurement bullets, added the rule A code tool that says it has no internet still tries the two files with the Grok finding and measured numbers, and noted why the check still takes an answer from npm's cache.

Measured on Haiku

Each run's prompt said the code tool's sandbox has no internet.

  • npm hangs, the web reachable (as Grok): 3 of 3 took route 3, fetched both files, and built packages that pass the verifier, each marked unverified.
  • Nothing reachable: 2 of 2 gave the json block, which builds and passes, with the equal .source.json file and the archive line.

One Grok-like run also ran the verifier's npx before building, which hung for the code tool's 110 seconds; the hand-over still runs it only where npm answered, so this PR leaves that alone.

Four earlier runs were discarded because the lab leaked: npm answered from this computer's cache with no network, and one run working in a subfolder escaped the dead registry. The design record now holds the full recipe—a package.json, a .npmrc naming a dead or hanging registry, and a cache of the run's own.Closes #211. Since 0.10.0, step 3 took "no internet" from the chat's own tools and then skipped route 3, although Grok's code tool—documented as having no network—fetches the organisation's site (v24.15.0, 200), so Grok handed over the JSON source unless the build archive was attached.

Now step 3 checks only whether npm reaches its registry, and route 3 is tried wherever Node runs, even when the tools say there is no internet or npm gave up.

  • SKILL.md: the Internet answer is gone; route 3 reads "Node runs here" and says to try it despite tool claims or npm failure.
  • two-files.md: when neither file arrives, the route is treated as failed and the next one is taken.
  • design/author.md: updated the step 3 and measurement bullets, added the rule A code tool that says it has no internet still tries the two files with the Grok finding and measured numbers, and noted why the check still takes an answer from npm's cache.

Measured on Haiku

Each run's prompt said the code tool's sandbox has no internet.

  • npm hangs, the web reachable (as Grok): 3 of 3 took route 3, fetched both files, and built packages that pass the verifier, each marked unverified.
  • Nothing reachable: 2 of 2 gave the json block, which builds and passes, with the equal .source.json file and the archive line.

One Grok-like run also ran the verifier's npx before building, which hung for the code tool's 110 seconds; the hand-over still runs it only where npm answered, so this PR leaves that alone.

Four earlier runs were discarded because the lab leaked: npm answered from this computer's cache with no network, and one run working in a subfolder escaped the dead registry. The design record now holds the full recipe—a package.json, a .npmrc naming a dead or hanging registry, and a cache of the run's own.

Written for commit 69e743a. Summary will update on new commits.

View guided diff Turn on auto-fix

… the code tool says about the internet

Since 0.10.0 step 3 took "no internet" from the chat's own tools and then skipped route 3.
Grok's code tool is documented as having no network, yet it fetches the organisation's site
(v24.15.0, 200), so Grok handed over the JSON source unless the build archive was attached.
Now only having no code tool means no npm; route 3 holds wherever Node runs and is tried
even where the tools say otherwise or npm gave up.

Haiku: 3 of 3 runs with npm hanging and the web reachable fetched both files and built
packages that pass the verifier; 2 of 2 with nothing reachable gave the json block, which
builds and passes.

Closes #211

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 3 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread design/author.md Resolved
Comment thread skills/h5p-author/SKILL.md Resolved
Comment thread design/author.md Resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

h5p-author: Grok builds nothing without the archive since 0.10.0: step 3 believes a code tool that says it has no internet

1 participant