From 40386a3881cfb287993d222b44432b5c1990846f Mon Sep 17 00:00:00 2001 From: Aleksandr Shevchuk Date: Sat, 14 Nov 2026 18:25:37 +0200 Subject: [PATCH 1/6] feat(author): in a chat that built nothing, a page the chat writes makes the link, and the verifier is not waited for Where no package was built and the reply is read in a chat, step 3 hands the source over in a small page: the source in a script of type application/json and a fixed script that makes the build page's link in the user's browser. Nothing compressed is typed or copied, and no code tool is needed. The link a command prints stays for a reply read outside a chat and for a package built here. Step 4 asks npm for the verifier's version first and gives up after ten seconds, so an npm that cannot install, as after a build from the archive, is found out at once. design/author.md records the probes in ChatGPT's preview, the six wordings and what each cost, the Haiku numbers, the archive kept in a ChatGPT Project, and the verifier's wait. Closes #202. --- design/author.md | 94 +++++++++++++++++++++++++++++++++++++- skills/h5p-author/SKILL.md | 84 +++++++++++++++++++++++++--------- 2 files changed, 155 insertions(+), 23 deletions(-) diff --git a/design/author.md b/design/author.md index 82380d20..e7f38665 100644 --- a/design/author.md +++ b/design/author.md @@ -15,7 +15,7 @@ already holds text to the content check's rules, from the pack an untrusted chec `apps/skills` plays every example untrusted too. Measured on a five-question quiz, at four characters a token: `content.json` was about 3,470 tokens to write by hand, after reading 3,900 to 9,500 of a type's semantics; the source is 1,000 to 1,800 tokens, written from a type file of 200 -to 3,000. Twenty-four things the code does not say by itself: +to 3,000. Twenty-seven things the code does not say by itself: - **One generator, three ways to run it.** The third, `saved`, checks content as H5P stores it (*Saved content is checked as the build checks what it writes*, below). `ContentGenerator` was the sweep's @@ -290,7 +290,10 @@ to 3,000. Twenty-four things the code does not say by itself: the author package pins, so the page plays with the pack it built from. A chat with no tool to run at all, as ChatGPT on a free account once its data-analysis quota is spent (for hours, the owner's test of 2026-11-09), cannot write the link: the skill has it put the whole source in its - reply, since that test's chat gave the page's bare address, which builds nothing. + reply, since that test's chat gave the page's bare address, which builds nothing. Since + 2026-11-14 a chat writes a page that makes the link, with or without a tool (*In a chat that + built nothing, a page the chat writes makes the link*, below), and a source goes over in a + `json` block only where it names files. A link is only what a command printed (2026-11-11). A link ChatGPT gave the owner carried 3,167 characters that were no deflate stream, its table broken at byte 82 of 2,375: the chat had typed them itself, made up or copied wrong, and the page built nothing. So the skill says it @@ -695,6 +698,10 @@ to 3,000. Twenty-four things the code does not say by itself: file. Haiku in a sandbox told it had no network and could give files handed the file over under the old text already, in 5 of 6 runs, as under the new; every link it gave was exact and the reply's one web address. + + Since 2026-11-14 a chat that built nothing hands the source over in a page that makes the + link, and the link a command prints is for a reply read outside a chat and for a package built + here (*In a chat that built nothing, a page the chat writes makes the link*, below). - **Only the build tool writes the `.h5p`** (2026-11-13). ChatGPT, asked to prove it could make the file where it could not install the tool, zipped an `h5p.json` and a `content.json` it had written: no library in it, and the content wrapped in a `params` key. The verifier fails it @@ -754,6 +761,89 @@ to 3,000. Twenty-four things the code does not say by itself: (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 archive kept in a ChatGPT Project builds too** (2026-11-14, the owner's free account). The + owner put the archive into a Project and asked in a chat of it ("works in the gpt project, i + attached tar file, file was created"): ChatGPT built a Question Set from it, 1.3 MB, which the + verifier passes with no warning, run here on the file. So the organisation's guide tells people + using ChatGPT to keep the archive in a Project and ask there (missing-elements.github.io#49), in + place of an upload with every message, of which a free account has few a day. One run: a second + chat of the same project was not tried. Python's index is closed there as npm's is: `pip download + six` answered "from versions: none", so the archive as a PyPI package is no way in. + + **The verifier is asked for, not waited for** (the same run, #202). After that build ChatGPT ran + step 4's `npx`, which cannot install there, waited until its tool gave up, and wrote "Unverified. + The separate verification tool timed out". A build from the archive never tries npm, so nothing + had told it that npm does not answer. Step 4's command now asks npm for the verifier's version + first, `npm view … --fetch-timeout=10000 --fetch-retries=0 &&`, and runs the verifier only where + it answers: against a registry that takes a connection and never answers, as that mirror does, it + gives up after 10.5 seconds, measured. Haiku with the archive attached and such a registry, 2 of + 2: built from the archive, made one connection to the registry, and handed the package over + unverified, with its files and the link its command printed. With npm working, 1 of 1 ran the + verifier as before and handed over its pass. +- **In a chat that built nothing, a page the chat writes makes the link** (2026-11-14, #202). The + link to the build page was the weak point of a chat that cannot build: compressed text that a + command prints and the model copies into its reply. ChatGPT broke 2 of 3 on 2026-11-13 (*The + hand-over carries the source and one web address*, above), and with its code tool unavailable, as + on a free account for hours, no command runs and there is none. ChatGPT shows an `html` code + block of a reply as a page, under Preview, on a free account too, at an address of its own + (`https://codex-inline-visualization-<16 hex>.web-sandbox.oaiusercontent.com`). The owner opened + two probe pages there, which ChatGPT was asked to give back as they were. A script in the page + runs; `CompressionStream('deflate-raw')` deflates a source; a link the page writes opens the + build page in a tab, with the right source, once ChatGPT has asked the user to allow it; a + download from a `blob:` address saves. A module from jsDelivr loads, but `connect-src` refuses a + fetch to the organisation's site and to jsDelivr, and `frame-src` refuses a frame on the build + page. So such a page can make the link, and can neither build nor play: that would take the pack + as scripts and a player without its worker. + + So where no package was built and the reply is read in a chat, step 3 has the chat write a page: + the source in a `script` of type `application/json`, and a short fixed script that deflates it + and writes the address into a link, *Build and play it*. Nothing compressed is typed or copied, + no code tool is used, and the source is in the reply once. The reply tells the user to open the + block with Preview and click the link, and, where their chat shows no Preview, to save the block + as a file ending in `.html` and open it: the page makes the link from a `file:` address too, + which is how the runs below opened it. A source that names files gets no page, as it gets no + link: it goes over whole in a `json` block, its files chosen on the build page. The script calls + its link `link`, since the preview's own scripts are reported to redefine `window.open` (Check + Point Research, 2026-11-05). + + The words took six tries. Each was run on Haiku, two of them in ChatGPT on the owner's free + account, and what each cost is why they read as they do: + + - **"Where no command runs here, a page you write makes the link, if the chat shows an `html` + code block of yours as a page":** Haiku with no tools, 6 of 6. It left a chat whose code tool + works printing the link by command, which is the chat that damages links. + - **"Where the chat shows an `html` code block of yours as a page the user opens (a preview), a + page you write makes the link, whether or not a command runs here":** Haiku with no tools, 3 of + 3. ChatGPT with it as a plugin gave a link a command had printed, a sound one that time, and + asked afterwards, quoted the sentence back. A condition a model must judge about its own chat + is one it passes over. + - **"In a chat, hand the source over in a page that makes the link … Only where your reply is not + read in a chat, as in a terminal, give a link instead":** no tools, 5 of 5, two of them told + nothing of a Preview; a code tool with no network, 2 of 2. With npm working, the one run built + and verified the package and then added the page to its reply, the source a second time. + - **"Where no package was built here and your reply is read in a chat":** with npm working, the + one run built with no page, and with no link either, and gave the preview command: the sentence + that kept the link for a terminal had taken it from a package built in a chat. + - **"A package built here is handed over as step 5 says, with the link a command prints and no + page", and the link's sentence naming both its places:** no tools 1 of 1, a code tool with no + network 1 of 1, and with npm working 1 of 1 with the package, the verifier's pass and the + command's link, which decodes to the source file it delivered. ChatGPT with this text as a + plugin tried npm and the two files, wrote the page, and Preview showed the link, which opened + the build page with the right source. Its reply said to save the block as a file first and + named Preview second. + - **So the order is in the words, "first … only then":** no tools 2 of 2 and a code tool with no + network 1 of 1, Preview first in each; and 2 of 2 sources naming the user's picture went over + in a `json` block with the page's address and the picture named, with no page. + + Across the 31 Haiku replies, 24 wrote a page, and in all 24 the script was the one given, the + link carried the page's source, and that source built a package the verifier passes with no + warning: Question Sets in English and Ukrainian and Accordions with markup, links of 701 to 1,973 + characters. The other seven rightly wrote none: three built with npm, two from the archive, two + named a picture. Haiku is a floor here, since it never damages a link: it shows that the words + are followed, and what ChatGPT does with them is the owner's runs. Not measured: whether ChatGPT + keeps the script as given for a long source (one run, whose link worked), and any other chat + app's preview. - **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 519c4108..970e4845 100644 --- a/skills/h5p-author/SKILL.md +++ b/skills/h5p-author/SKILL.md @@ -133,9 +133,9 @@ 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. +address is downloaded as it builds. Where npm cannot install, the verifier cannot run either, +which step 4's command finds out in ten seconds: 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): @@ -166,9 +166,46 @@ for the user to play it before using it. **Where nothing can be fetched or run, the build page builds it.** No shell, no Node, or no download: [the build page](https://missing-elements.github.io/h5p/build/) builds the same package in the user's -browser from the source alone, with no install. Give them a link that carries the source, written -with Node or Python, which need no network. A source that names files gets none: a link carries -its text, not the files: +browser from the source alone, with no install. + +**Where no package was built here and your reply is read in a chat, hand the source over in a +page that makes the link**, whether or not a command runs here (a chat's code tool can be +unavailable for hours), and whether or not you can tell how the chat shows it. A package built +here is handed over as step 5 says, with the link a command prints and no page. Write the page +below in one `html` code block, with the whole source in place of the line `SOURCE`, and every +other line copied as it is: change nothing in its script. The user's browser makes the link from +the source, so nothing compressed is typed or copied; a link copied into a reply from a command's +output can arrive damaged, and with no package built there is nothing else to fall back on, so +run no command for one. Tell the user, in a line or two and in this order: first, to open the +block as a page with the chat's Preview and click *Build and play it*, which the chat may ask +them to allow; only then, as the way where their chat shows no Preview, to save the block as a +file ending in `.html` and open it. Give the source nowhere else in that reply, and no `#source=` +link beside it. A source that names files gets no page. + +```html + + +Build and play +

Making the link…

+ + +``` + +**A link that carries the source is written by a command**, with Node or Python, which need no +network. Give one in place of the page where your reply is not read in a chat, as in a terminal; +and give one with a package built here, as step 5 says. A source that names files gets none: a +link carries its text, not the files: ```bash node -e "const s=require('fs').readFileSync('source.json'),f=[];JSON.parse(s,(k,v)=>(k==='path'&&typeof v==='string'&&f.push(v),v));console.log(f.length?'No link: the source names files, which a link cannot carry.':'https://missing-elements.github.io/h5p/build/#source='+require('zlib').deflateRawSync(s).toString('base64url'))" @@ -183,22 +220,22 @@ under the activity's name with `.source.json` (`course.source.json`): the page o 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. +right after the page or the link, or after the source where neither was given, 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, -and tell them to paste it into the page at https://missing-elements.github.io/h5p/build/. Never -give the page's address without the source, in the link or beside it: it builds nothing. The -page lists every problem by its path, with a button that copies them for the chat: fix them all -and give a new link, or the whole source again. A source that names files of its own waits for -the user to choose them there. Steps 4 and 5 are then the user's, on that page: the package is -**unverified** until they have played it there, and they download it from there. +Where neither a page nor a link can carry the source, as one that names files, or where outside +a chat neither command runs, give neither: the build page sees only what the user pastes, so put +the **whole source in your reply**, in one `json` code block, and tell them to paste it into the +page at https://missing-elements.github.io/h5p/build/. Never give the page's address without the +source, in a page, in the link or beside it: it builds nothing. The page lists every problem by +its path, with a button that copies them for the chat: fix them all and give a new page, a new +link, or the whole source again. A source that names files of its own waits for the user to +choose them there. Steps 4 and 5 are then the user's, on that page: the package is **unverified** +until they have played it there, and they download it from there. A source with a problem writes nothing: the build lists every problem by its path, so fix them all and run it again under the same name. Once a build has written its file it never writes @@ -211,9 +248,14 @@ too much. ## 4. Verify ```bash -npx @missing-elements/h5p-verify@latest course.h5p +npm view @missing-elements/h5p-verify version --fetch-timeout=10000 --fetch-retries=0 && npx @missing-elements/h5p-verify@latest course.h5p ``` +Run it as one line. Its first half asks npm for the verifier's version and gives up after ten +seconds, so that an npm that cannot install here, as after a build from the archive or from two +files, is found out at once and not waited for: where it prints no version, the verifier did not +run and cannot, so do not run it by itself or again, and say the package is **unverified**. + It writes `course.verify/report.json` and `course.verify/screenshot.png` beside the package (`--out ` puts them elsewhere). Read the report's `verdict`, `reasons`, `errors` and `warnings`: a run that fails may say why only in `reasons`, such as content that never reached @@ -225,9 +267,9 @@ removing what fails. Without a browser, say the package is **unverified**. ## 5. Review and hand over 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; and the line on the build archive, where -step 3 gives it. Otherwise let the user play it in their browser: +page route is the whole hand-over: in a chat, the page that makes the link; outside one, the link +it printed, with the source as a file where you can 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 From b38ab602e628a5395b709f3739371287e3993fcc Mon Sep 17 00:00:00 2001 From: Aleksandr Shevchuk Date: Sat, 14 Nov 2026 22:46:53 +0200 Subject: [PATCH 2/6] fix(author): the page holds the source in a noscript, which no tag in a source ends, and the record counts every run A source showing or