Link the built-with-nanoodle showcase from the product

[mikkel]

What breaks today

The showcase at built-with-nanoodle
is an orphan. Nothing on nanoodle.com links to it. Its only mention in this
repo is one row of the README ecosystem table, which no visitor reads. The
showcase is the strongest available proof that the app builder makes real,
shippable things, and it sells nothing to anybody.

What this change does

Two in-product links, at the 2 moments where they convert.

1. The share popover in play.html. One line, last in the popover, after
the link row and the share targets. That is the one moment the reader already
holds the #a= link that a showcase entry needs:

Proud of it? add your app to the showcase ↗ — it needs the full link, not a shortened one.

The line is owner-only. body.recipient #sm-showcase{display:none} hides it
for a share-link recipient, who did not build the app they are re-sharing.
This is the same gate the mobile bar already uses for #export. The editor's
✨ Create app modal embeds this same play.html chrome, so the create-app
success moment gets the link from the same element.

The trailing clause is not decoration. "Make it shorter — optional" sits a few
lines above in the same popover, and a click there calls setShareUrl(short),
which replaces the link box with the short link. The showcase decodes the app
straight out of the #a= fragment, so its checker rejects a shortened entry.
Read top to bottom, the popover walked the reader into the one link form the
showcase cannot take. Naming the form in the invite closes that dead end before
the copy happens. guide/share-links.html says the same thing in its showcase
paragraph, which also sits directly under a shortening section.

2. The Examples panel note in index.html. Beside the existing
awesome-noodles link, in the same sentence shape:

Made an app from one? built-with-nanoodle — the showcase. Every app on it is
still one of ours; make yours the first that isn't. One line.

The gallery answers "what can I start from". The showcase answers "does this
make anything real".

Every entry in the showcase today is a nanoodle-team demo, and its own README
says so. So the copy says so too, in all 5 places this PR touches: the Examples
note above, the guide's "Elsewhere" list, the share-links guide, llms.txt,
and the README ecosystem row. An empty-of-outsiders showcase is an invitation,
not a wall of other people's work, and a reader who clicks through now gets
what the copy promised.

llms.txt was the last of the 5 to say it. Until the final commit here it
described the showcase but named neither the "still ours" fact nor the
full-link rule, so an agent that reads only that file would describe the
showcase as a collection of third-party apps, and would hand a reader the
shortened link the showcase cannot decode. Both sentences are in it now.

The README ecosystem row is fixed here too. It read "Showcase of apps people
shipped"; it now reads "Showcase of finished apps, every one still ours — use
when you want to see what nanoodle makes, or to put yours on the list".
llms-full.txt is generated from that README, so it carries the same one-line
change. scripts/gen-llms-full.mjs does not read llms.txt, so the final
commit left llms-full.txt byte-identical.

I deliberately did not touch the editor's own Share popover. That link is a
workflow (#g=), and the showcase takes apps.

Where the full-link rule comes from

The rule is already on the showcase repo's main, in CONTRIBUTING.md
lines 8–9, inside step 2 "Get the link", which starts on line 7:

Use the full-length link, not a shortened one — the checker (and future
embeds) need the payload in the fragment.

I read that from main today through the contents API, not from a branch.

So the copy this PR ships is true today, and this PR is independently
mergeable. It is not contingent on nanoodlecom/built-with-nanoodle#1.
That PR does edit CONTRIBUTING.md, but those 2 lines appear in its diff as
unchanged context — it adds a "no third-party app has landed yet" note, a
browser-edit link and a longer npm test paragraph around them. An earlier
revision of this description sourced the rule to #1. That citation was wrong.

Related, but not a dependency: nanoodlecom/built-with-nanoodle#1 fixes 2 dead
links inside the showcase itself.

i18n

Every new string goes through the existing path, like its neighbours.

• play.html: 3 new PLAY_I18N_B keys — "Proud of it?", the link label, and
  the full-link clause — each with all 5 translations.
• index.html: 2 new keys in each of the 5 language maps (10 added lines),
  split at the anchor exactly like the awesome-noodles line above it, so the
  repo name stays data-no-i18n and each surrounding text node is its own key.

One correction inside this branch, for the record: commit 0892685, the first
commit here, wrote the German word for the showcase as "Galerie" in both files
(2 occurrences, 1 per file). Commit d46e9a1, the very next commit and still on
this branch, removed both and wrote "Schaufenster". Nothing shipped in between
— "Galerie" appears 0 times in index.html and 0 times in play.html, both on
main and at this branch's head. This was a defect this branch introduced and
this branch fixed, not a pre-existing one. "Schaufenster" matches es "vitrina",
fr/pt "vitrine" and ja "ショーケース".

scripts/check-i18n-coverage.mjs passes, so all 5 maps stay at parity.

Agent-facing and docs index

• llms.txt gains an Examples section naming the gallery and the showcase,
  with a line each on when to use which.

• guide/index.html "Elsewhere" list gains both repos.

• guide/share-links.html gains a "Where shared apps end up" section. A share
  link is the whole distribution step, so that page is where a reader asks the
  question the showcase answers.

• llms-full.txt is regenerated with node scripts/gen-llms-full.mjs. That
  file is generated and its header says not to hand-edit it.

  Re-measured against the current base. The 126-added / 22-removed figure an
  earlier revision quoted here was measured against dbd4543, when this file was
  missing the whole Ecosystem table and still listed the retired 🎨 Draw node.
  Drop the retired draw node from the agent-facing docs #372 has since landed and its own regeneration corrected both of those. So
  against main as it stands (6d7c065) this PR changes exactly 1 line of
  llms-full.txt — line 144, the showcase row. diff between the merged file
  and main's reports that 1 row on each side and nothing else.

  "Ecosystem" appears 1 time in the merged file and "Draw" 0 times, as before.
  Every line comes from committed sources, and re-running the generator on the
  merged branch leaves the working tree clean, so the committed file is exactly
  what the generator produces.

The llms-full.txt collision with #372 — resolved, no longer a prediction

#372 has landed (6d7c065). The collision an earlier revision of this
description simulated is now merged for real, in commit 924ca03 on this branch:
git merge origin/main, run with rerere disabled so the genuine conflict
appeared.

What conflicted. 1 file, llms-full.txt. 1 hunk. Markers at lines 144,
146 and 148 — one line on each side, the built-with-nanoodle row of the
Ecosystem table. The other 15 paths the merge brought in (from #372 and #373)
merged clean, and neither .githooks/pre-commit nor
.github/workflows/checks.yml conflicted: this branch never touched either
file, so main's unioned versions came through as-is. Both new clauses are
present in the merged hook and both fire — see the guard trace below.

Why this branch's row wins, checked in the generator rather than assumed.
localParts() in scripts/gen-llms-full.mjs pushes embed(mainReadme, …)
under the heading ## nanoodle (the site), and embed() only demotes
headings, drops images and absolutizes links. So the Ecosystem row in
llms-full.txt is a verbatim copy of the row in README.md. This PR is the
one that changes that README row (line 140); #372 leaves README.md alone, so
#372's row was simply the pre-change text carried forward. Keeping this
branch's row is the only resolution the generator can agree with.

Corrected: keeping the row is not the same as keeping the file. The earlier
revision said "the resolved file is then identical to this branch's
llms-full.txt". That was true when it was measured and is false now.
nanoodle-py 0.5.0 landed (nanoodlecom/nanoodle-py#12) and #372's regeneration
already carries its new README sections, which this branch's copy of the file
predates. Re-running the generator on the merged tree therefore rewrote 88
lines into the file (71 of them non-blank): the optional-inputs paragraph, the
"Breaking in 0.5.0" section, the timeout= paragraphs, the prompt-caps section
and the --json failure section. Taking this branch's file whole would have
left llms-full.txt stale against the sibling READMEs and failed #372's own
--check.

So the rule for llms-full.txt is the second half of the old sentence, not the
first: re-run node scripts/gen-llms-full.mjs. Keep this branch's row to
clear the markers, then regenerate.

Result. The merged llms-full.txt differs from origin/main's on exactly
1 line, line 144, and node scripts/gen-llms-full.mjs --check is clean on it.

#372's 2 new guards both pass on the merged branch:

• scripts/check-llms-full.mjs → "✓ check-llms-full — locally-sourced sections
  match; 6 supported-node rows name only registered types"
• node scripts/gen-llms-full.mjs --check → "✓ llms-full.txt matches the
  current sources"

The --check ran twice: once letting the generator make its own shallow clones
of the 2 library repos, and once CI-style with NANOODLE_JS / NANOODLE_PY
pointed at fresh checkouts of them, which needs no network. Both green. The
checkouts were at nanoodle-js bff73bb and nanoodle-py deea945, the current
default-branch heads. Do not point those variables at a long-lived local
clone — the one on this machine still sat at nanoodle-py 0.4.0 and would have
reported a false failure.

CI

All 3 checks on the current head, 924ca03 — the merge commit, so CI ran
against main as it stands — pass. Read back from the GitHub check-runs API
after the push. All times are UTC on 2026-07-30:

Check	Result	Completed
Workers Builds: nanoodle	success	00:25:14Z (build 6bd62281)
parity	success	00:25:44Z
checks	success	00:26:33Z

The checks job is the one that matters most here: it is where #372's
node scripts/gen-llms-full.mjs --check now runs, against fresh checkouts of
nanoodle-js and nanoodle-py.

mergeable is MERGEABLE and mergeStateStatus is CLEAN. The earlier
revision's figures for head f2a5c4e are superseded; that head predates the
merge.

One reading note for whoever checks this: the legacy
/commits/<sha>/status endpoint reports pending for this commit. It has 0
entries in statuses — all 3 checks are check-runs, not commit statuses — and
that endpoint returns pending for an empty set. gh pr checks and the
check-runs endpoint are the ones to read.

Across the 6 commits of this branch there are 18 check-runs, 3 per commit. 17
are green.
The 1 red is Workers Builds: nanoodle on the earlier head commit 57cfd3d, at
05:10:36Z (build 78e1e5e1).
checks and parity were green on that same commit. The failure was not in
the diff:

• 57cfd3d changed 2 files: README.md and llms-full.txt. README.md is on
  line 11 of .assetsignore, so it is never uploaded as an asset at all.
• Both files are byte-identical between 57cfd3d (red) and 3cfd075 (green):
  git diff 57cfd3d 3cfd075 -- README.md llms-full.txt is empty. The exact
  content blamed for the red build is in a build that passed.
• The Cloudflare API confirms the failing build produced no worker version.
  Version uploads run 04:37:20Z (v1141) then 05:25:07Z (v1142), so the
  05:10:36Z failure sits inside a gap. The build died before the upload step,
  not on anything the tree contains.
• Other PRs' builds around it are green, so this is not an exhausted quota.
  Read from the check-runs API shortly after 17:16Z on 2026-07-29, on each PR's
  head at that moment: Let the signed-out sample reach a video result #376 (f5030c2) 04:01:39Z, Drop the retired draw node from the agent-facing docs #372 (830cc55) 04:28:35Z,
  growth: refresh the 4 slipped launches, remove the stale r/mcp gate, add a launch checklist #373 (2f746cb) 04:35:39Z and Guard the index.html ↔ play.html twin: a one-sided edit now fails the commit #375 (4929e35) 17:16:22Z — all success. Those
  are a historical snapshot: Drop the retired draw node from the agent-facing docs #372 and growth: refresh the 4 slipped launches, remove the stale r/mcp gate, add a launch checklist #373 have since merged, and the open PRs'
  heads move as they get pushed, so re-read them rather than trust these
  timestamps.
• The wrangler build.command is node scripts/stamp-sw.mjs; it exits 0. And
  wrangler deploy --dry-run validates the config: 5 runs on a clean detached
  worktree of f2a5c4e, exit 0 every time.
• Settled by the merge itself: Workers Builds: nanoodle is green on 924ca03,
  which contains everything 57cfd3d contained. Whatever caused that one red
  build, it is not in this tree.

I could not read Cloudflare's own build log. The API token in the repo .env
does work for the deploy path — it lists /workers/scripts and the nanoodle
version history — but it returns 12006 Invalid token on every
/accounts/{id}/builds/... path, re-checked today. (It also fails
/user/tokens/verify with code 1000, which is a separate permission and does
not affect the calls that do work.) A token with "Workers Builds
Configuration: Read" would close that gap for the next person; the deploy path
itself is unaffected.

Correction: the "asset files" figure

An earlier revision of this description said the dry-run "reads 643 asset
files". That number is not an asset count, and quoting it as one was
misleading. Both halves are re-measured on this machine at the final commit,
with wrangler@4.115.0:

• Clean detached worktree of f2a5c4e, env -u CLOUDFLARE_API_TOKEN npx wrangler@4.115.0 deploy --dry-run: 346, on 5 of 5 runs.
• The same command in my development worktree: 647, on 5 of 5 runs.

Both figures are stable — no spread across the 5 samples on either side. Both
depend on the tree they are read in, not on the machine: 346 is what any
clean checkout of this commit gives; 647 counts scratch content only my
worktree holds.

The 643 came from that same development worktree, at a moment when it held
less scratch content. The worktree carries 2 gitignored directories a clean
checkout does not: .tmp-libs/ (226 files in 71 directories — the scratch
clones of nanoodle-js and nanoodle-py that scripts/gen-llms-full.mjs makes)
and proof/showcase-note/ (3 files in 1 directory — this PR's browser
harnesses, added after the 643 reading). 346 + 226 + 71 = 643 exactly, and
adding the harnesses' 3 files and 1 directory gives the 647 I read today.

The figure counts directories as well as files, and counts paths that
.assetsignore excludes. Two probes on the clean worktree, each read twice,
each returning to 346 after cleanup:

• 11 new files in 2 new directories moved 346 → 359, that is +13, not +11.
• 5 new files inside proof/, which is in .assetsignore, moved 346 → 351.

With WRANGLER_LOG=debug the line prints its list: exactly 346 path entries,
and they include /proof (a directory on disk) and /proof/COMPARISON.md. So
the figure is a census of the directory tree, not a count of what deploys.

What deploys is a different walk. In the wrangler 4.115.0 bundle the asset
walker getFilesInFolder skips ALWAYS_IGNORE, which is
Set(["node_modules"]), and skips every entry whose name starts with .
unless it is in HIDDEN_FILES_TO_INCLUDE, which is Set([".well-known"]) —
then .assetsignore filters what is left. Confirmed against a local
wrangler dev on the clean worktree, with a scratch
.tmp-libs/nanoodle-js/README.md and a non-hidden control directory in place:

Path	Status
/llms.txt	200
/zzscratch/x.txt (control: not hidden, not in .assetsignore)	200
/.tmp-libs/nanoodle-js/README.md	404
/proof/REPORT.md (in .assetsignore)	404
/scripts/gen-llms-full.mjs (in .assetsignore)	404
/README.md (in .assetsignore)	404
/wrangler.jsonc (in .assetsignore)	404

So a scratch clone cannot reach production through this path, and no
.assetsignore change is needed. The dry-run figure should be read as "the
config validates and the command exits 0", which is all this PR ever needed
from it.

How I verified it

Every figure below was re-measured on the merged branch head, 924ca03, not on
the old base. The counts moved, because #372 and #373 each added a guard.
Sample counts are stated wherever a figure can vary.

Guards, all green:

• I staged the branch's full diff against origin/main (7 files: README.md,
  guide/index.html, guide/share-links.html, index.html, llms-full.txt,
  llms.txt, play.html — 54 insertions, 3 deletions) and ran
  .githooks/pre-commit over it. Exit 0, 305 lines of output, 267 of them
  carrying ✓, 0 carrying ✗. The diff is much smaller than the 179/24 an
  earlier revision quoted because main now carries Drop the retired draw node from the agent-facing docs #372's regeneration of
  llms-full.txt, so this PR's share of that file is down to its 1 row.
• A bash -x trace of that same run shows which guards fired: the hook can
  invoke 53 scripts, and 51 ran. The 2 the staged file set does not trigger
  are check-sw-routing and check-updates. The 51 include both clauses the
  merge brought in — check-llms-full (from Drop the retired draw node from the agent-facing docs #372) and check-launch-facts
  (from growth: refresh the 4 slipped launches, remove the stale r/mcp gate, add a launch checklist #373) — plus check-html-js, check-hidden-css,
  check-i18n-coverage, check-policy, check-lang-pages, check-export,
  check-share-link, check-create-app, check-drifted-model,
  check-bridge-consent, check-share-samples, sync-examples --check and
  check-prompt-caps. Most guards print prose rather than their own filename,
  so the trace is the evidence, not the output.
• Separately, every scripts/check-*.mjs guard runs clean: 53 of 53 pass, 0
  fail (51 last time; Drop the retired draw node from the agent-facing docs #372 added check-llms-full.mjs and growth: refresh the 4 slipped launches, remove the stale r/mcp gate, add a launch checklist #373 added
  check-launch-facts.mjs). The 2 in that glob the hook never invokes are
  check-example-models and check-lora-models, which are the monthly cron
  guards. The sweep bumps lora-models.json. I ran it in a throwaway worktree,
  so the mutation never reached this branch — git status on the branch
  worktree is empty and lora-models.json is in no commit here.
• check-i18n-coverage on the merged tree reports: index.html 512 keys;
  play.html runtime 82 + builder 72 keys × 5 languages, chrome covered.

Real browser, headless Edge over CDP, serving the worktree from a Node static
server. No key seeded, no shorten button clicked, so no network call leaves the
machine and no API spend. Both harnesses were re-run on the merged tree
(924ca03), so the German strings are read back after the merge, not only
before it. Both exited 0.

• play.html, English, app loaded, share popover open. #sm-showcase reads
  back exactly "Proud of it? add your app to the showcase ↗ — it needs the full
  link, not a shortened one.", display: block, href is the showcase.
• play.html, German. Same popover, read back in full: "Stolz darauf? füge
  deine App dem Schaufenster hinzu ↗ — dafür braucht es den vollständigen Link,
  keinen gekürzten." "Schaufenster" present, "Galerie" absent, no English left.
• The shorten section is in the same popover in both runs — its heading reads
  back as "MAKE IT SHORTER — OPTIONAL" / "KÜRZER MACHEN — OPTIONAL" — so the
  2 lines a contributor reads in sequence were checked together, not apart.
• play.html loaded from a real #a=u… share link: body.recipient is true
  and #sm-showcase computes to display: none. The recipient gate holds.
• index.html with noodle_lang=de, Examples panel open, full #examplesnote
  read back: "…diese stammen aus awesome-noodles — remixe eins und schick uns
  deins. Daraus eine App gebaut? built-with-nanoodle — das Schaufenster. Alle
  Apps darin sind noch unsere eigenen; mach deine zur ersten, die es nicht ist.
  Eine Zeile." No "Galerie", no English left in the note.
• 9 of 9 browser assertions pass in the play.html run, 5 of 5 in the
  index.html run.

curl -sL -o /dev/null -w '%{http_code} %{time_total}' on
https://github.com/nanoodlecom/built-with-nanoodle returns 200 on 5 of 5
samples, in 0.45 s to 1.24 s from this machine. The timing is network-dependent
and will differ elsewhere; only the 200 matters.

Not verified

• The README ecosystem row, llms.txt and the regenerated llms-full.txt are
  text only. No browser check applies to any of them.
• es, fr, pt and ja renderings of the new play.html line are checked in the key
  map only. de and en were read back in the browser.
• The Cloudflare build log for 78e1e5e1 itself. The token cannot read it, so
  the cause of that one red build is inferred from the version-upload gap, not
  read from the log.
• curl against the showcase URL was measured on the earlier head and not
  repeated on 924ca03; this branch does not change that URL.
• No paid workflow ran. No API spend in this change.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	nanoodle	924ca03	Commit Preview URL Branch Preview URL	Jul 30 2026, 12:25 AM