@imfusion/web-ui 0.6.4-dev.43.g3f16d49f → 0.6.4-dev.45.gbaffa741

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@imfusion/web-ui",
3
- "version": "0.6.4-dev.43.g3f16d49f",
3
+ "version": "0.6.4-dev.45.gbaffa741",
4
4
  "description": "The official Web UI component library for ImFusion web apps",
5
5
  "author": "ImFusion GmbH",
6
6
  "homepage": "https://imfusion.com",
@@ -27,22 +27,39 @@ Never overwrite user changes or commit without fresh approval.
27
27
 
28
28
  ## Update the base
29
29
 
30
- Run from the consumer package root:
30
+ Before installing, query the registry from the consumer package root:
31
31
 
32
32
  ```sh
33
- npm install @imfusion/web-ui
33
+ npm view @imfusion/web-ui dist-tags --json
34
+ ```
35
+
36
+ Honor an explicitly requested version or tag. Otherwise, target `latest`; if the installed version is a prerelease, ask
37
+ whether to use `latest` or `dev` before proceeding. Resolve the selected tag or version with
38
+ `npm view @imfusion/web-ui@<selected-tag-or-version> version --json` and record the exact target version. Stop if the
39
+ registry lookup fails. Report "already current" only when the pre-update version matches this resolved target; npm's "up to
40
+ date" message alone does not prove that.
41
+
42
+ Install the resolved version, then refresh the existing installer target:
43
+
44
+ ```sh
45
+ npm install @imfusion/web-ui@<resolved-version>
34
46
  npx web-ui-install
35
47
  npx web-ui-install --hooks
36
48
  ```
37
49
 
38
- Use `npm install @imfusion/web-ui@<version>` when the user supplied an explicit version. Stop on install failure. Preserve
39
- the installer's existing target. Do not use `--force` or `--legacy-peer-deps`.
50
+ Stop on install failure. Preserve the installer's existing target. Do not use `--force` or `--legacy-peer-deps`.
40
51
 
41
52
  The installer owns the vendored skills, its `AGENTS.md` fence, and hook scripts. Run both installer commands after the
42
53
  package update even when the existing registrations look complete: they refresh scripts, prune retired registrations, and
43
54
  merge installer-owned entries idempotently into `.claude/settings.json` and `.codex/hooks.json`. Stop on malformed settings
44
55
  or installer conflicts. Read existing host registrations first and do not stack an event the project already covers.
45
56
 
57
+ After both installer commands, inspect the installed skill diffs and briefly report any guidance changes; version-marker
58
+ changes alone do not count. Re-read changed skills and references relevant to the remaining work, including this update skill
59
+ if it changed. Continue from the current step using the updated guidance, keeping the original baseline, user choices, and
60
+ completed changes in mind. Check for newly required steps without repeating completed mutations or expanding the approved
61
+ scope.
62
+
46
63
  ## Verify the base update
47
64
 
48
65
  After every mutating command, compare the status with the preflight snapshot. Stop on an unexpected path or overlapping
@@ -51,7 +68,8 @@ change.
51
68
  Run the consumer's documented full verification. Read its scripts first; prefer an aggregate check, otherwise run the
52
69
  non-watch format, lint, typecheck, test, and build commands that exist.
53
70
 
54
- Check the dependency and lockfile, skill markers, `AGENTS.md` fence, hook registrations, and final update-owned path list.
71
+ Verify that the installed package, manifest, and lockfile match the recorded target version. A mismatch is a base-update
72
+ conflict. Check skill markers, the `AGENTS.md` fence, hook registrations, and the final update-owned path list.
55
73
 
56
74
  Report before the first commit:
57
75