fix(client): harden label pinning and close review findings
- Resolve the Windows admin config via the ProgramData known folder instead of the user-controlled ProgramData variable, so a user cannot redirect the admin lookup and drop pinned labels - vendor rename rewrites matching agent-lib.labels.json entries, so a renamed item keeps its labels instead of going to every client - validate checks the labels file in repositories without a lockfile - A kept modified copy of a deselected item is no longer drift in status, and the toast explains it as "no longer assigned to you" - Labels parser rejects trailing data such as an extra closing brace - Tests: admin pin wiring (config chain, --repo, admin as chosen config), reselect redeploy with byte-level no-op, status labels JSON, validate without lockfile, rename keeps labels - README: document unreadable admin config, drift semantics, rename Refs: agent_lib-fh4 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
59735c3b24
commit
ae316860e5
17 files changed
+296
-17
No files matched your search
@@ -109,7 +109,7 @@ a separately authenticated repository.
|
||||
unknown version) → **sync aborts before any change** with a clear
|
||||
error. Never fall back to "deliver everything".
|
||||
- A name that matches no item → warning on sync output and in
|
||||
`status`, not fatal and no toast (the curator-side `validate` is the
|
||||
`status` of labeled clients, not fatal and no toast (the curator-side `validate` is the
|
||||
hard gate).
|
||||
3. Drop items whose labels do not intersect the client labels before
|
||||
hashing/planning (`internal/client/sync.go`, loop over
|
||||
|
||||
Reference in new issue
Block a user