vendor select <name> --add/--remove/--mode all changes what a source
contributes without advancing the pinned rev: ids are validated against
the pinned upstream (typos abort listing available ids), collisions
re-run, renames from the lockfile are honored, and the external area is
rewritten via the same staging-swap as update. include mode grows and
shrinks the include list; all mode --remove moves ids onto exclude;
--mode all resets to everything. Failed selects mutate nothing.
Closes beads: agent-lib-cd3
sync/status now resolve the work repository from a fallback chain:
--repo flag > --config flag > AGENT_LIB_CONFIG env > user-level config
(XDG / AppData) > admin platform default. --repo works without any
config file; tokens fall back to AGENT_LIB_GIT_TOKEN/AGENT_LIB_GIT_USER
without ever overriding a configured token. A completely empty chain
yields an error listing every searched location, a minimal config
example and the --repo shortcut.
Closes beads: agent-lib-9o8
- skills are found at any depth under the skills dir, so category-nested
layouts (skills/<category>/<id>/SKILL.md) vendor correctly; the folder
basename is the upstream id and the outermost SKILL.md wins over anything
nested inside a skill folder
- web-tree urls pointing directly at a type directory (.../tree/main/skills)
now map that directory as the type root instead of nesting it under the
default layout
- verified against the real github.com/mattpocock/skills repository
(36 skills across categories; include-selection by basename)
m3ta-chiron