update-agentic-workspace 0.1.8 → 0.1.9

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.
Files changed (2) hide show
  1. package/README.md +10 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -49,11 +49,17 @@ and want it to stay that way, disable it again after the update, or migrate that
49
49
  `--cleanup`, every candidate path and registration is still previewed, but nothing is removed and
50
50
  no `claude` invocation runs for this phase at all. Pass `--cleanup` to actually delete what was
51
51
  previewed.
52
- 4. **Reinitialization** — the same never-clobber managed-file reconcile and additive permission-floor
52
+ 4. **Reinitialization** — the same never-clobber managed-file reconcile and permission-floor
53
53
  reconcile `create-agentic-workspace --existing` already implements: an operator-edited file is
54
- reported drifted and left byte-identical, never overwritten. `.gitignore`'s own managed-block
55
- reconcile runs here too, so a workspace that predates a later block content change catches up on
56
- the next update run rather than staying stuck on whatever it was scaffolded with.
54
+ reported drifted and left byte-identical, never overwritten. The permission-floor reconcile is
55
+ additive with one narrow exception a row shaped exactly like the floor's own root-glob rows,
56
+ whose `(name, sub)` PAIR not the script name alone the shipped floor no longer declares, is
57
+ retired from `allow`/`ask` (printed `[retired] <row>`): retiring one dropped subcommand of a
58
+ script that still ships others removes only that stale pair, never the whole family, and a
59
+ script deleted outright does not leave a standing grant behind forever. `.gitignore`'s own
60
+ managed-block reconcile runs here too, so a workspace that predates a
61
+ later block content change catches up on the next update run rather than staying stuck on
62
+ whatever it was scaffolded with.
57
63
 
58
64
  Every run previews every `claude` invocation and every path it will touch **before** the first one
59
65
  happens, and ends with a per-phase summary (`changed` / `already current` / `skipped: <reason>`).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "update-agentic-workspace",
3
- "version": "0.1.8",
3
+ "version": "0.1.9",
4
4
  "description": "One command to bring an installed Agentic Foundry workspace current: refresh the plugin marketplace (migrating a pre-v1.7.0 tag-pinned registration if found), update the plugin in every scope that enables it, and re-run the workspace + permission-floor reconcile. A thin wrapper: every shared module is resolved from create-agentic-workspace at an exact version — no vendored second copy.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -25,7 +25,7 @@
25
25
  "README.md"
26
26
  ],
27
27
  "dependencies": {
28
- "create-agentic-workspace": "0.15.0"
28
+ "create-agentic-workspace": "0.15.1"
29
29
  },
30
30
  "scripts": {
31
31
  "test": "echo 'no local tests: every shared module is unit-tested in ../cli/test against create-agentic-workspace'\"'\"'s own src/'"