diff --git a/design/author.md b/design/author.md index 27c01e96..e51f9420 100644 --- a/design/author.md +++ b/design/author.md @@ -681,6 +681,52 @@ to 3,000. Twenty-four things the code does not say by itself: since this computer's npm answered. With npm cut off, 5 of 6 handed over the exact link and the source file; the sixth, whose user wanted "not a link and not JSON", ended with the `npx` command for the user, as one run of the old text had. +- **Where nothing downloads, the person attaches the build archive** (2026-11-13, #200). ChatGPT's + sandbox runs Node 22.16, but nothing reaches it from outside. npm goes through OpenAI's mirror, + which fails or hangs. Its download tool saved none of eleven files on the owner's free account + that day, from the organisation's site or any other. An installed plugin's files never reach + its code. A file the person attaches does: the owner attached the one-file tool and a Question + Set's libraries as a `.tar.gz`, with a prompt that named the commands, and ChatGPT built a + Question Set that the verifier passes. The owner played it, and Claude and Grok built from the + same archive. The same files as a `.zip` were refused, read as a plugin to install ("Plugin + archive must contain …"). + + So the organisation's site writes one archive for every type, + `/h5p/bundles/h5p-author-build.tar.gz` (missing-elements.github.io#47), from the release it + pins: the tool, every part of the pack with its index, and `libraries.txt`, laid out as a + build from a bundle reads them. With pack 1.1.0 it is 14.9 MB, and the same bytes on every + rebuild. Every type goes in one file, rather than the tool in each type's bundle, because the + person downloads it before a type is chosen. A tool that still crashed on `--version` (#198) + could send a model that checks it first off to the link, so the archive starts with 0.9.8. + Nothing passes through a server of the organisation's this way either: the archive is the + tool and the libraries, public already, and the chat's provider holds no more than the chat + already gave it. That, with no MCP server, is what the guide and the plugin lead with, in the + owner's words, privacy first. + + Step 3 builds from an attached archive first. Where Node runs and nothing installs or + downloads, the build page's route carries one fixed line offering the archive. Measured on + Haiku in a sandbox with no network: + - **The archive attached:** 3 of 3 runs built from it under the old text and 3 of 3 under the + new, and all six packages pass the verifier. So the route's words are for a model that needs + the step written out, as ChatGPT's prompt wrote it out. + - **No archive, the offer as a sentence:** 1 of 3 runs offered it with the exact address, as a + last note that promised to verify too. One named the file without an address, and one said + nothing. + - **No archive, the offer as a line to copy as it is, right after the link:** 2 of 3 runs did + so. The third left it out. + - **Across both no-archive arms:** all six links were exact, and all six gave the source file. + + As with the feedback line before it, a weak model drops some of what it is asked to write. So + the skill does not rest on the offer: the organisation's guide, not the skill, tells people + using ChatGPT to attach the archive to the message where they ask + (missing-elements.github.io#47). + + A source with media needs the network for them all the same: a `path` at a web address is + downloaded as the package builds, which a sandbox that fetches nothing cannot do. So the archive + route says that there a `path` names a file in the sandbox, such as one the person attached + (cubic's review). A source that names files gets no link, so the offer's line follows the source + where no link was printed. Neither change was run on Haiku: the six no-archive runs above named + no file. - **The skill names no product** (2026-11-12, the owner's call). Its routes were told apart by the apps they were measured in; they now say what each needs: a shell that reaches the npm registry, Node and a download where npm cannot install, or nothing that runs or fetches. What a diff --git a/skills/h5p-author/SKILL.md b/skills/h5p-author/SKILL.md index f5d6ff61..6eaa150a 100644 --- a/skills/h5p-author/SKILL.md +++ b/skills/h5p-author/SKILL.md @@ -9,10 +9,10 @@ license: MIT You write a short source: the content type and only what its defaults cannot know. `@missing-elements/h5p-author` fills in the rest from the libraries, copies them, and checks every field. Needs Node 22 and a shell; nothing to install. Where `npx` cannot install, it builds -from two downloaded files, or a page in the user's browser builds it (step 3), so never end with -commands for the user to run. Only it writes the `.h5p`: never put one together yourself from -`h5p.json` and `content.json`, since one made by hand carries no libraries and nothing checks it. -Keep [LICENSE](./LICENSE) with the skill. +from the build archive the user attaches, or from two downloaded files, or a page in the user's +browser builds it (step 3), so never end with commands for the user to run. Only it writes the +`.h5p`: never put one together yourself from `h5p.json` and `content.json`, since one made by +hand carries no libraries and nothing checks it. Keep [LICENSE](./LICENSE) with the skill. With this text alone and none of its files beside it, open https://missing-elements.github.io/h5p/skill/ first and take every address from it: it writes out in full each file this text names and each @@ -113,11 +113,14 @@ from what you know of the type: the build says, for each place that is wrong, wh Build the best way this environment allows, and tell the user which you take: +- **Here, from the build archive**: Node runs and the user attached `h5p-author-build.tar.gz`, + the build tool and every type's libraries in one file. *From the build archive*, below. - **Here, with npm**: a shell that reaches the npm registry, as in a terminal. The command below. - **Here, from two files**: Node runs and files can be fetched, but npm cannot install, as in a chat's sandbox that reaches the web and no registry. *If it cannot install here*, below. - **In the user's browser**: nothing here runs, or nothing fetches, as in a chat with no tools - or one that cannot open a web address. *The build page*, below, with no attempt here first. + or one that cannot open a web address. *The build page*, below, with no attempt here first; + where Node runs, with its line on the build archive. Take the first that applies, and the next if it fails. @@ -127,6 +130,20 @@ Build in a working folder of your own, not in the folder the user named: npx @missing-elements/h5p-author@latest build source.json course.h5p ``` +**From the build archive.** Find the file the user attached, in the folder the chat keeps +attachments in (`find / -name 'h5p-author-build*.tar.gz' 2>/dev/null`), unpack it in your working +folder and build from it: nothing to install or fetch, for any type. + +```bash +tar -xzf # or: python3 -m tarfile -e . +node h5p-author.mjs build source.json course.h5p --libraries parts +``` + +With no network, a file's `path` must name a file here, such as one the user attached: a web +address is downloaded as it builds. Where npm cannot install, the verifier cannot run either: +hand the package over **unverified**, with the build page's link below for the user to play it +before using it. + **If it cannot install here, build from files instead.** No network for npm (`EAI_AGAIN`, `ENOTFOUND`, a registry's 403, 404 or 503, or an install that hangs until the command times out): do not retry, try another way to install it, or end with commands for the user to run once npm @@ -172,6 +189,14 @@ nothing to build. Where you can give the user a file, give them the source too, under the activity's name with `.source.json` (`course.source.json`): the page opens it, and a link copied wrong into your reply builds nothing. +Where Node runs here and nothing could be installed or downloaded, put this line in that reply, +right after the link, or after the source where no link was printed, as it is: attached to a +message, the archive builds the `.h5p` here. + +``` +To get the .h5p file here instead: download https://missing-elements.github.io/h5p/bundles/h5p-author-build.tar.gz (15 MB) and attach it to your next message. +``` + Where nothing is built here and they print no link, with neither, or with no tool that runs anything at all (a chat's code tool can be unavailable for hours), give no link: the page sees only what the user pastes, so put the **whole source in your reply**, in one `json` code block, @@ -208,8 +233,8 @@ removing what fails. Without a browser, say the package is **unverified**. Check answers and feedback against the material. Where nothing was built here, step 3's build page route is the whole hand-over: the link it printed, with the source as a file where you can -give one, or the whole source and the page's address. Otherwise let the user play it in their -browser: +give one, or the whole source and the page's address; and the line on the build archive, where +step 3 gives it. Otherwise let the user play it in their browser: ```bash npx @missing-elements/h5p-verify@latest course.h5p --preview