Parts Search

@@ -12,6 +12,34 @@ description: Build and release a new version of adom-parts-search. Use when the 5. Show user a screenshot of the 3-column grid + recommendation banner; wait for explicit approval. 6. `./publish.sh`: git tag, registry tarball (bin + skills + dockbar.json + docs/icon.svg + screenshots), page-repo push of dockbar.json / docs/icon.svg / docs/hero.png, verify with a clean `adom-wiki pkg install`. +## Check the inbox, at the start and end of every work block++`adom-wiki inbox` is the only place issue comments, closures, and @mentions+surface. Nothing pushes them to you, so an unread inbox looks exactly like a+quiet one.++```bash+adom-wiki inbox --unread                 # what changed while you were heads-down+adom-wiki issue list adom/adom-parts-search   # open issues on this page+adom-wiki issue view 'adom/adom-parts-search#<n>'+```++Read the `reason` field on each row: `author` and `participant` are threads you+are already in, `mentioned` means someone typed `@<you>` and is waiting, and+`owner`/`watching` are pages you look after. A `mentioned` row is a person+blocked on an answer; treat it like a direct message, not a feed item.++Two habits that cost this app real time:++- **A fixed issue is not a closed issue.** Issue #1 (deprecated install refs)+  was fixed in a docs pass and then sat OPEN for seven weeks, so the page looked+  broken to anyone reading its tracker, and the reporter got no answer. When a+  release fixes something someone filed, close it in the same release, with the+  verification, not from memory.+- **Verify against the LIVE page, not your working tree.** Fetch the published+  file (`.../files/<path>?raw=1`) and grep the installed binary. A fix that+  never made it into the package reads exactly like a fix that did.+ ## Pre-release checklist  - [ ] VERSION / Cargo.toml / `--version` / wiki metadata all match

@@ -1,5 +1,13 @@ # Changelog +## 1.3.4 (2026-08-24)++Skill updates: check the wiki inbox, and verify on the instance the dock runs++- The build skill now opens with the inbox rule: `adom-wiki inbox` is the only place issue comments, closures and @mentions surface, nothing pushes them, and an unread inbox looks exactly like a quiet one. Includes the reason-field guide (a `mentioned` row is a person waiting), and two habits this app paid for: close an issue in the release that fixes it, and verify against the live published file rather than the working tree.+- The dock skill documents the two-installs split: the developer container copy and the dock-installed copy in the user workspace do not share settings, timing or localStorage, so user-facing state must be checked on the instance the dock runs.+- Closed issue #1 (deprecated install refs, open since 7 July): the dead `wiki-ufypy5dpx93o.adom.cloud` host and `adompkg` references were removed earlier today, including the hardcoded fetch URL in install.rs that had been silently forcing every skill install onto its bundled fallback.+ ## 1.3.3 (2026-08-24)  Send to AI: 120s budget, delivery proven by delivered_to, honest recovery

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {   "slug": "adom-parts-search",-  "version": "1.3.3",+  "version": "1.3.4",   "type": "app",   "description": "One search box across Mouser, DigiKey and JLCPCB. Parallel queries, side-by-side product photos, and a Mouser-preferred recommendation that reasons around stock and lead time. Dock Bar ready: serve, health, settings, Say it.",   "dependencies": {@@ -38,5 +38,44 @@     "SKILL.md",     "BUILD-SKILL.md",     "CHANGELOG.md"+  ],+  "changelog": "Skill updates: check the wiki inbox, and verify on the instance the dock runs",+  "discovery_triggers": [+    "parts search",+    "find part",+    "source component",+    "source part",+    "compare distributors",+    "compare vendors",+    "Mouser or DigiKey",+    "BOM sourcing",+    "price this part",+    "where can I get",+    "check stock",+    "parts availability",+    "fastest delivery",+    "cheapest part",+    "component search",+    "part lookup",+    "price breaks"+  ],+  "discovery_pitch": "Search Mouser, DigiKey and JLCPCB in parallel with product photos; Mouser-preferred best-source pick. Say 'with parts search' to your AI.",+  "sample_prompts": [+    {+      "label": "source an STM32F103RBT6",+      "prompt": "source an STM32F103RBT6"+    },+    {+      "label": "where can I get an ESP32-S3-WROOM cheape",+      "prompt": "where can I get an ESP32-S3-WROOM cheapest and fastest"+    },+    {+      "label": "compare Mouser, DigiKey and JLCPCB for a",+      "prompt": "compare Mouser, DigiKey and JLCPCB for an LM555"+    },+    {+      "label": "price this BOM across distributors",+      "prompt": "price this BOM across distributors"+    }   ]-}+}\ No newline at end of file

@@ -12,6 +12,34 @@ description: Build and release a new version of adom-parts-search. Use when the 5. Show user a screenshot of the 3-column grid + recommendation banner; wait for explicit approval. 6. `./publish.sh`: git tag, registry tarball (bin + skills + dockbar.json + docs/icon.svg + screenshots), page-repo push of dockbar.json / docs/icon.svg / docs/hero.png, verify with a clean `adom-wiki pkg install`. +## Check the inbox, at the start and end of every work block++`adom-wiki inbox` is the only place issue comments, closures, and @mentions+surface. Nothing pushes them to you, so an unread inbox looks exactly like a+quiet one.++```bash+adom-wiki inbox --unread                 # what changed while you were heads-down+adom-wiki issue list adom/adom-parts-search   # open issues on this page+adom-wiki issue view 'adom/adom-parts-search#<n>'+```++Read the `reason` field on each row: `author` and `participant` are threads you+are already in, `mentioned` means someone typed `@<you>` and is waiting, and+`owner`/`watching` are pages you look after. A `mentioned` row is a person+blocked on an answer; treat it like a direct message, not a feed item.++Two habits that cost this app real time:++- **A fixed issue is not a closed issue.** Issue #1 (deprecated install refs)+  was fixed in a docs pass and then sat OPEN for seven weeks, so the page looked+  broken to anyone reading its tracker, and the reporter got no answer. When a+  release fixes something someone filed, close it in the same release, with the+  verification, not from memory.+- **Verify against the LIVE page, not your working tree.** Fetch the published+  file (`.../files/<path>?raw=1`) and grep the installed binary. A fix that+  never made it into the package reads exactly like a fix that did.+ ## Pre-release checklist  - [ ] VERSION / Cargo.toml / `--version` / wiki metadata all match

@@ -69,6 +69,20 @@ Dock settings (the gear at the top of the rail), **Add app**, `adom/adom-parts-s Being in the curated list is not required. The card appears with no LED until the app is running; that is the honest state. +## Two installs, not one++There are two copies of this app in play, and they do not share state: the one a+developer runs in their own workspace container, and the one the dock installs+into the USER's workspace. Separate filesystems, so separate+`~/.adom/parts-search-settings.json`, separate timing files, and (different+origin) separate localStorage.++So verify user-facing state on the instance THE DOCK runs, never the one you+develop against. This app shipped a dashboard with its prompts panel missing+because the user's instance had `showSayStrip:false` persisted while the+developer's copy looked perfect. Read the user's instance through its own API+(`/api/settings`, `/state`) from the box the dock launched it on.+ ## Diagnose  Read the LED payload first; every facet carries a `_hint` naming the fix: