Adom Wiki Skill Pack

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.23",+  "version": "0.8.24",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"

@@ -131,7 +131,7 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.23",+  "version": "0.8.24",   "description": "The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marking, reusable thumbnail caches and component-page widgets.",   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",@@ -173,7 +173,8 @@     "skills/wiki-component-lod/references/verification.md",     "skills/wiki-component-lod/references/runtime.md",     "skills/wiki-workspaces/SKILL.md",-    "skills/wiki-brand/SKILL.md"+    "skills/wiki-brand/SKILL.md",+    "skills/wiki-hero-glb/SKILL.md"   ],   "scripts": {     "install": "./install.sh",

@@ -46,8 +46,8 @@ fires the moment someone is about to embed a hero).  For pages a user has **not** installed yet, the wiki exposes: - `GET /api/v1/search?q=<query>`, full-text search. **Works** (finds pages by-  slug/title/brief). Caveat: the FTS hyphen bug (`chip-fetcher` →-  "no such column: fetcher").+  slug/title/brief/README/tags; hyphenated slugs are fine). Takes the filter+  syntax below. - `GET /api/v1/discover?triggers=<csv>`, intended to surface pages whose   declared `discovery_triggers` match what the user is doing. **This is where   discovery is currently weak, see the state + TODO below.**@@ -56,6 +56,35 @@ You declare a page's triggers in the **package manifest** (`package.json` `discovery_triggers: [...]`) and they ARE stored (verify: `GET /api/v1/packages/<slug>/manifest`). +## Search syntax: filters and search inside a page (2026-09-21)++The one search box (the `/search` page, the nav typeahead, the Ctrl+K palette+and `GET /api/search`) understands `key:value` words mixed with the text:++| Filter | Meaning |+|---|---|+| `type:app` `type:skill` `type:hardware` `type:bootstrap` | page type |+| `kind:board` (any hardware kind) | narrows hardware; implies `type:hardware` |+| `owner:john` `org:adom` | the namespace; `org:` only org-owned pages |+| `tag:kicad` (repeatable, AND) | a page tag |+| `has:3d` `has:symbol` `has:footprint` `has:datasheet` `has:skill` `has:hero` | what the page ships |+| `in:docs` | search the DOCUMENTS pages ship (README family, docs/**, sub-READMEs, every SKILL.md) instead of the page fields; each result names the file and heading that matched and opens that section |+| `in:title` | title and brief only |+| `path:docs/research` | only documents under that folder (implies `in:docs`) |++The words left over are the text query; a word with an unknown key stays a+word. A bad value (`has:bogus`) is a 400 `BAD_FILTER` with the allowed set.+Filters with no words (`tag:kicad`) list the matching pages, most installed+first. Example: `hero studio in:docs owner:adom` finds the section of any+Adom page's documents that talks about the studio, and links to the heading.++**Search inside one page:** every page has a "Search this page" box in its tab+bar (`/` focuses it) backed by `GET /api/pages/<owner>/<slug>/search?q=<words>`+(`&family=1` adds the family's children, `&per_file=2` folds sections). It+answers sections with anchors and deep links, so an AI thread can ask "where+in this pack is X documented" without reading the whole pack. Every markdown+document a page ships is indexed by heading at index time; nothing to declare.+ ## ⚠️ Current real state (verified 2026-06-21: re-verify, this WILL change)  - ✅ Local installed-skill discovery (Layer 1) works.