drive: the agent-group ledger item is resolved by its deletion

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

Author: wmadden-electric

.drive/projects/agent-skills-npm-packages/deferred.md

@@ -2,6 +2,7 @@
 
 - **When facade skill content diverges per database, split the skill by name — do not add a carrier package.** Today every facade ships an identical `prisma-8` skill and cross-package conflicts are arbitrated by highest version (`collectSkillSources`), which is safe only while content is identical and versions are lockstep. When per-database content arrives, give each facade a differently named skill (per-target skills, or a shared core plus per-target references) so names never conflict. A common or standalone skills package was considered and rejected 2026-08-21 (operator concurred): a transitive carrier is unresolvable from the project root under pnpm, and a direct-dependency skills package breaks the installed-version guarantee (facade upgraded, skills package not, check reports in sync). The allowlist still grows one deliberate line per facade either way.
 
+- **RESOLVED 2026-08-21: the `agent` command group is deleted** (operator ruling "kill it"; commit 257d785 on PR #219). The post-login tip now offers `prisma skills sync` when copies are stale. Residual: the browser login success page's static `npx skills add prisma/skills` copy button remains, pending an operator decision (reviewer recommends deleting it). Original entry follows.
 - **Retire or re-scope the `agent` command group in prisma-cli.**
   `prisma agent install|update|status` still installs the v6/v7-line
   skills by shelling out to `npx skills@latest add prisma/skills`, and