* Add Nuxt UI 4.12.0 guidance
Add rows 77-83 to the nuxt-ui stack:
- UChart usage, categories and colors, donut data shape
- UApp automatic locale with @nuxtjs/i18n
- UCheckboxGroup max and UFileUpload reject event
- Security upgrade note for 4.11.3 (set/setAtPath prototype
pollution, ChatPrompt GET leak)
Existing rows are unchanged. Mirrored copies synced with
npm run sync:assets.
* Fix Nuxt UI 4.12.0 data gate
Move the nuxt-ui current target from 4.11.1 to 4.12.0 so the new rows
pass validation:
- Update the pin in core.py and test_web_stack_freshness.py.
- Retag the 76 existing rows to nuxt-ui 4.12.0. Verified At stays
unchanged. The 4.11.2 to 4.12.0 release notes list no breaking
changes.
- Use an official ui.nuxt.com URL for row 83 (High severity).
- Regenerate catalog-summary.json for the new row count.
- Refresh the relevance threshold runtimeFingerprint. Relevance
metrics are identical to the committed baseline.
* fix: stop Cursor skill pointing at empty Quick Reference
Platforms that set quickReference to false omitted the inlined
reference but still told the agent to use "the Quick Reference
sections above." Resolve QR/NOQR variants so Cursor (and other
non-inlined platforms) follow the existing search flow instead.
Claude and Codex keep the inlined reference wording.
Co-authored-by: Neal Meyer <ngmeyer@users.noreply.github.com>
* fix: accept 21 platform configs after ZCode
ZCode landed on main without updating the agent-guide validator
or the platform-count e2e assertion. This branch did not add a
platform; the stale expected count of 20 was failing CI.
Co-authored-by: Neal Meyer <ngmeyer@users.noreply.github.com>
* fix: refresh stale relevance runtime fingerprint
verify:data would fail next on evaluate:relevance because main's
threshold manifest still hashed the pre-#500 runtime. Metrics are
unchanged; only the fingerprint now matches current scripts/data.
Co-authored-by: Neal Meyer <ngmeyer@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Neal Meyer <ngmeyer@users.noreply.github.com>
The Three.js stack claims `threejs 0.185.1` but several rows still
recommend APIs that 0.185.1 deprecates and warns about at runtime:
- THREE.Clock (deprecated since r183) -> THREE.Timer with
timer.update(timestamp) once per frame, getDelta()/getElapsed(),
and timer.connect(document) to avoid a huge delta after a hidden tab.
Rows 13, 31, 34, 45. Row 45 also stops calling getElapsedTime()
per vertex (Clock.getElapsedTime() calls getDelta() internally).
- THREE.PCFSoftShadowMap (deprecated since r182, WebGLShadowMap warns
and falls back to PCFShadowMap) -> PCFShadowMap, with shadow.radius /
VSMShadowMap noted for softer edges. Rows 22, 23.
- GLTFLoader imported from three/examples/jsm -> three/addons, matching
the rest of the file. Row 52.
Bump Verified At on touched rows, extend the freshness test's
forbidden-token list (three.clock, clock.getdelta,
clock.getelapsedtime, pcfsoftshadowmap, three/examples/jsm/) and add a
positive Timer lookup, refresh the relevance runtime fingerprint and
baseline, and re-sync mirrored assets.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Reverify the full stack catalog against Nuxt UI 4.11.1 and correct stale API examples. Add Splitter, ProgressGroup, motion, Vite detection, and CommandPalette security guidance.
Co-authored-by: Ray <ray.tien@cloudeep.com.tw>
Squash-merged by github-maintain cron after maintainer approval (review 2026-06-20 by @mrgoonie) and conflict resolution (rebase to head 4bd45ba5, all checks green).