diff --git a/.gitignore b/.gitignore index 97dec9fc..ae5d3238 100644 --- a/.gitignore +++ b/.gitignore @@ -18,9 +18,10 @@ packages/player/LICENSE packages/normalize/LICENSE packages/verify/LICENSE packages/author/LICENSE -# The h5p-author skill's text, which the author's `prepack` copies beside its type files (#178). +# The h5p-author skill's text and build routes, which the author's `prepack` copies beside its type files (#178, #204). packages/author/SKILL.md packages/author/references/authoring.md +packages/author/references/build/ packages/cmi5/LICENSE packages/embed/LICENSE diff --git a/design/author.md b/design/author.md index 82380d20..0591a607 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-eight 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 @@ -552,7 +555,9 @@ to 3,000. Twenty-four things the code does not say by itself: for, so that no reader has to guess: on the new text five of five runs (those three, both skipped, both given) wrote what was given and the default for what was skipped, and the run with the author named in the request asked for the licence alone. Those eight packages play - too. + too. On 2026-11-14 the owner dropped the question (*Each build route is a file of its own, every + fact is written once, and one question at most is asked*, below): the author and the licence are + taken as given, or the defaults above, and never asked. - **A text's own marks are said where a chat reads, and what a library cannot take apart is a problem** (2026-11-12, #187). Haiku with a shell and the skill built each of the 32 content types that need no media twice: 64 packages, all built, all passing the verifier with no @@ -695,6 +700,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 +763,168 @@ 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 `noscript`, 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 source is held in a `noscript`, not in a `script` of type `application/json`, as it first + was (cubic's review of PR #203). A `script` ends at the first ``, `` and `