fix(author): the record of #212's runs, and route 3 fails where either file does not arrive

Merged
AL
3d ago
+26-18

Closes #213. A follow-up to #212, from a review of it after it merged.

  • design/author.md, the rule A code tool that says it has no internet still tries the two files:
    • The run that took 110 seconds was slow on route 1's find /, run with no archive attached. The record blamed the verifier's npx, which was a lab check of mine in that run's folder.
    • Three spoiled runs were left out, not four.
    • Both offline runs tried the two files before the json block, and one ran no npm check.
    • The cost where a network hangs is now stated, and marked as not measured, with ChatGPT.
  • design/author.md, elsewhere: the section counts thirty rules, and the older bullet on Grok says it has no place to install a skill.
  • references/build/two-files.md: "Where a file does not arrive, this route has failed", where it said "neither file".
  • README.md: the line on chat apps no longer counts zips.

Haiku with the corrected sentence, each run told its code tool has no internet: with npm hanging and the web reachable, 1 of 1 fetched both files and built a package that passes the verifier; with nothing reachable, 1 of 1 tried the fetch and gave the json block, which builds and passes.


Summary by cubic

Corrects the run records and failure conditions documented in the author design, following a post-merge review of #212.

  • The 110-second run was slow on route 1's find /, not the verifier's npx; three runs were spoiled, not four.
  • Both offline runs tried fetching the two files before giving the json block, and the route's failure rule now says "a file does not arrive" instead of "neither file".
  • Adds the unmeasured cost of a hanging network, updates the rule count to thirty, and notes Grok has no place to install a skill.
  • README now says who installs the skill's zip, where it is, and which release it holds.