toga-ai 1.0.423 → 1.0.424

package/knowledge/2.0/apps/toga-blox/workflows/dynamic-publish-pipeline.md

@@ -6,8 +6,8 @@ project: TOGa Blox
 client: shared
 type: workflow
 status: active
-updated: 2026-07-21
-owners: [jcardinal]
+updated: 2026-07-23
+owners: [jcardinal, apeterson]
 files:
   - toga-blox/.github/workflows/publish.yml
   - toga-blox/src/utils/getFontAwesomeIcon.tsx
@@ -35,6 +35,26 @@ resolve in a consuming app's build, or touching `publish.yml`.
 - **Every** branch (including `_production`) publishes a **prerelease** version
   `X.Y.Z-<mode>.<run>` under dist-tag `<mode>`. There is no longer a production special case.
   Verified live: `production:1.0.315-production.96`, `sandbox-client:1.0.315-sandbox-client.97`.
+  Observed 2026-07-23: `sandbox-client:1.0.317-sandbox-client.101`, `sandbox-dev:1.0.316-sandbox-dev.102`.
+
+### Version derivation (CI owns the suffix; dev owns only the base)
+
+- CI reads `version` from `package.json`, **strips any `-<suffix>`**, does **`patch + 1`**, then
+  appends `-<mode>.<GITHUB_RUN_NUMBER>`. So base `1.0.317` on `_sandbox-client` run 104 publishes
+  `1.0.318-sandbox-client.104` under dist-tag `sandbox-client`.
+- **The developer controls only the BASE version** committed in `package.json` on the feature
+  branch. **Never hand-write the `-<mode>.N` prerelease suffix** — CI generates it. There is no
+  manual `npm publish`; CI is the only publisher.
+
+### Deploy procedure (e.g. `_sandbox-client`)
+
+1. Ensure a clean tree; optionally bump the base version in `package.json` on the feature branch.
+2. Merge the feature branch into `_sandbox-client`, then push (this triggers the CI publish).
+3. Monitor with `gh run watch`; verify with `npm dist-tag ls @agilant/toga-blox`.
+4. Consuming apps (e.g. `toga25-supply` on `_sandbox-client`) install from the `sandbox-client`
+   dist-tag or a pinned `1.0.x-sandbox-client.N` version and must **re-install** to pick up a new
+   build. The `deploy-sandbox-client` project skill (`.claude/skills/` in this repo) drives this
+   procedure end-to-end.
 
 ### What was removed (and why it's safe)
 
@@ -66,6 +86,12 @@ environment needs its own maintained `_<mode>` branch in `toga-blox-npm`.
 - **Publish before build.** `npm install @agilant/toga-blox@<mode>` fails `ETARGET No matching
   version` in the app build until this repo has published that channel. GitHub Actions runs the
   workflow version *on the pushed branch*, so the branch must carry the current `publish.yml`.
+- **`publish.yml` has diverged across branches (2026-07-23).** The dynamic `_*` wildcard trigger
+  lives on `_sandbox-client`, but older/feature branches (e.g. `feature-new-table`) still carry the
+  *old* `publish.yml` that triggers only on `_production/_gamma/_beta`. Because Actions runs the
+  copy on the pushed branch, a new `_<mode>` channel will **not** publish unless the branch you push
+  carries the wildcard-trigger version. When standing up a new channel, merge from a branch that has
+  the dynamic `publish.yml` (or update it first).
 - **FontAwesome v7 `style`-prop TS2322** (fixed 2026-07-21 in `getFontAwesomeIcon.tsx`, and a
   reusable pattern for any consumer). FA v7 types the `FontAwesomeIcon` `style` prop as
   `CSSProperties & CSSVariables`, where `CSSVariables` requires a `--fa-*` custom-property index
@@ -78,6 +104,11 @@ environment needs its own maintained `_<mode>` branch in `toga-blox-npm`.
   the pattern the consuming apps should follow (see the commerce workflow's secret-hygiene note).
 
 ## Change history
+- 2026-07-23 — Documented CI version derivation (strip suffix → patch+1 → append `-<mode>.<run>`;
+  dev owns only the base version, never the suffix) and the `_sandbox-client` deploy procedure now
+  driven by the `deploy-sandbox-client` project skill. Recorded that `publish.yml` has diverged
+  across branches: the dynamic `_*` trigger is on `_sandbox-client` while older/feature branches
+  still trigger only on `_production/_gamma/_beta`. (apeterson)
 - 2026-07-21 — Made `publish.yml` fully dynamic: trigger `_*`, branch→dist-tag by stripping the
   leading underscore (mode == channel 1:1), every branch (incl. `_production`) publishes a
   `X.Y.Z-<mode>.<run>` prerelease; removed the `_production`→`latest` special case (workflow no

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.423",
+  "version": "1.0.424",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",