liteagents 2.24.1 → 3.5.0

package/packages/droid/commands/remember.md

@@ -1,7 +1,5 @@
 ---
-name: remember
 description: Consolidate stashes + friction into project memory
-usage: /remember
 ---
 
 Run friction analysis, then consolidate session stashes + friction antigens into a single project-local MEMORY.md, and inject into AGENTS.md. Friction runs automatically (best-effort) — there is no separate `/friction` command. A docs reconcile check runs at the end, detect-only.
@@ -38,10 +36,31 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
    - **Locate `friction.cjs`** — it is bundled next to this command at `remember/friction.cjs`
      (the same directory as `remember.md`, whether installed or run from the package). If it
      exists nowhere, skip to step 1 (stash-only) and tell the user friction.cjs is missing.
+   - **Check for a newer liteagents** (best-effort, one line, never blocking) — bundled
+     beside `friction.cjs` as `remember/version-check.cjs`. Call it by its **absolute
+     path**, exactly as step 7 calls `docs-builder.cjs`: the cwd here is the target repo,
+     not this package, so a cwd-relative path fails everywhere except the liteagents repo
+     itself.
+     ```bash
+     node ~/.factory/commands/remember/version-check.cjs
+     ```
+     **If that path does not exist, use the directory you just resolved for
+     `friction.cjs`** — the two ship side by side, so that directory is correct for a
+     non-default install and when running from a checkout, where the path above would
+     point at the installed copy instead of the one under test.
+     It prints one advice line if the installed version is behind the registry, and prints
+     nothing otherwise. It exits 0 on every path, caches the registry answer for 24h, and
+     is bounded to ~2s, so it cannot stall this run. If it prints a line, relay it verbatim
+     in your final report; never act on it and never run the install yourself.
+   - **If the script is missing from both locations, say so** — one line, same rule as step
+     7's "applicable but could not run". A failed *check* (offline, registry down, timeout)
+     stays silent by design: it is a once-a-day nudge, not a result anyone is waiting on. A
+     missing *script* means the install is incomplete, which is worth a word.
    - **Resolve the global sessions root** — probe this list top-to-bottom, use the first that
      exists and contains `.jsonl` files directly, or one level down in per-project
      subdirectories (friction.cjs scans exactly those two levels, not a deep recursive walk).
      **Never prompt the user.**
+     <!-- mirror:literal:start — every tool's real path, identical in all four kits -->
      ```
      # ── Add your own global sessions root at the TOP so it is checked first ──
      ~/.claude/projects/                 # Claude Code
@@ -51,6 +70,7 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
      ~/.codex/sessions/                  # Codex CLI  (use $CODEX_HOME/sessions/ if set)
      ~/.gemini/antigravity-cli/brain/    # Antigravity
      ```
+     <!-- mirror:literal:end -->
      > Note: `friction.cjs` parses Claude Code's session schema. The Codex/Antigravity roots
      > will resolve but yield no signals until friction learns their formats — open an issue
      > to request one: https://github.com/hamr0/liteagents/issues
@@ -72,11 +92,26 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
      fresh output). **Move only those pipeline files** — anything else in `.factory/memory/`
      (e.g. user-owned rule files) stays where it is. Remove the old dirs only if empty, update the managed MEMORY section in AGENTS.md to
      the new reference (step 5), and tell the user exactly what moved.
-   - **Bootstrap `AGENT_RULES.md` (one-time, silent-if-present).** If
-     `.factory/remember/AGENT_RULES.md` does not exist, copy it from the bundled template next
-     to this command (`remember/AGENT_RULES.md`, same directory as `friction.cjs`). If it
-     already exists, leave it untouched — never overwrite, even if the bundled template
-     changes in a later version; it becomes user-owned the moment it lands in the project.
+   - **Sync `AGENT_RULES.md` from the installed template** — run the bundled script, which
+     does the whole decision itself. Call it by **absolute path**, for the same reason as
+     `version-check.cjs` in step 0: the cwd is the target repo, not this package.
+     ```bash
+     node ~/.factory/commands/remember/sync-rules.cjs
+     ```
+     It compares `.factory/remember/AGENT_RULES.md` against the template shipped beside it
+     and takes one of three actions: **absent** — copies it in; **identical** — does
+     nothing at all, no write and no output; **differs** — moves the old body to
+     `AGENT_RULES.md.bak` and copies the new one in, reporting both. Relay whatever it
+     prints in the step-8 report; it is silent when nothing changed.
+
+     **This replaced a bootstrap-once rule that never refreshed**, which left a measured 35
+     repos many releases behind. The rules doc is a shipped standards document, so it is
+     kept current rather than frozen on first write — nothing is destroyed, because a
+     differing body is always preserved in the backup first.
+
+     The comparison is a byte compare done *by the script*, never by you: a model-performed
+     copy can re-wrap a line or drop a trailing newline, and the file would then differ
+     forever, backing up on every single run.
    - Read all `.factory/stash/*.md` files in the current project
    - Read friction output written in step 0: `.factory/remember/friction/antigen_clusters.json` (preferred) or `.factory/remember/friction/antigen_review.md` (fallback). On the fallback path, step 4c does NO counting — merge quotes into
      matching entries only; never change `sessions`, `last_seen`, or `recurred_while_hot` (the
@@ -88,7 +123,11 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
      length-gate debt on `.factory/remember/MEMORY.md`. Steps 4-5 (friction → ledger count →
      Antigens render) are stash-independent and still run whenever friction produced output
      (see step 4's own guard). If there is also no friction
-     output, report "nothing to consolidate" and stop after step 1.
+     output, report "nothing to consolidate" and stop after step 1 — **but run
+     step 5's `stub-check.cjs` before you stop.** The stub shape does not depend on
+     there being anything to consolidate, and skipping it on quiet runs is exactly
+     how a repo with nothing to remember stays broken forever. `sync-rules.cjs`
+     already ran above, for the same reason.
 
 2. **Extract from unprocessed stashes** (up to 5 stashes per agent, as few agents as possible — see Guardrails)
    - Each agent reads its batch of stashes together and calls the mid-tier model (see Guardrails) to extract:
@@ -387,11 +426,32 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
      Users trim this section deliberately (a pointer-only variant is common), and rewriting
      it silently re-adds text they removed, on every single run, forever. Observed in the
      field: a run restored the inline rules into a AGENTS.md whose owner had cut them, and
-     the edit had to be reverted by hand. This matches how `AGENT_RULES.md` itself is
-     handled — bootstrapped once, never overwritten after.
+     the edit had to be reverted by hand. Note this no longer matches how `AGENT_RULES.md`
+     itself is handled: `sync-rules.cjs` refreshes that file every run, because it is a
+     shipped standards document with a backup behind it. This section is prose the user
+     owns, with nothing behind it — so it stays bootstrap-once.
    - If an existing pair is present but its **path pointer** is missing or wrong, that is
      load-bearing: **report it and stop**, do not silently rewrite the section around it.
 
+   - **Then assert the stub SHAPE mechanically** — run the bundled script by **absolute
+     path**, for the same reason as steps 0 and 1:
+     ```bash
+     node ~/.factory/commands/remember/stub-check.cjs
+     ```
+     It edits only *inside* the marker pairs, and only the mechanism: a MEMORY include that
+     is not `@.factory/remember/MEMORY.md` is repaired, and an `@`-include of
+     `AGENT_RULES.md` is demoted to a plain pointer. Prose inside the blocks is user-owned
+     and is never touched, which is why the bootstrap-once rule above still holds. It will
+     **not** repoint a MEMORY include at a file that does not exist — an un-migrated
+     `.factory/memory/` repo has a live MEMORY.md at the old path, and breaking a working
+     include to satisfy a naming convention is worse than reporting it. Silent when the
+     shape is already current; relay whatever it prints in the step-8 report.
+
+     Measured 2026-09-03: 21 of 37 local repos still carried the pre-v2.19 `@`-include of
+     `AGENT_RULES.md`, hot-loading ~300 lines into every session. A shape rule checked by
+     asking you to look is a rule that drifts back; this one is a byte-level assertion done
+     by the script, never by you.
+
    ```markdown
    # Project Memory
    > Auto-generated by /remember. Do not edit manually.
@@ -452,8 +512,10 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
    `index-flat` script `/docs-builder` already uses, never a model call. Wrapped so any
    failure here can never block the memory write that already happened in steps 3-6.
 
-   - **Locate `docs-builder.cjs`** — bundled next to this command at
-     `docs-builder/docs-builder.cjs` (same convention as `remember/friction.cjs`). Call it by
+   - **Locate `docs-builder.cjs`** — it ships in the `docs-builder/` directory
+     that sits beside this one (under `skills/` on Claude Code and Amp, under
+     `commands/` on Droid and opencode), exactly as `friction.cjs` ships beside
+     this file. Call it by
      its **absolute path** in the command below — the cwd here is the target repo, not this
      package, so a cwd-relative path fails everywhere except the liteagents repo itself.
    - **Not applicable, stay silent:** if the project has no `docs/` directory, skip without
@@ -535,7 +597,14 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
      ledger: ag-003 "don't commit per change"    RECURRED while hot (2/2) → rephrased, attempt 2
      ledger: ag-002 "literal scoped ask"         ESCALATED → Fact; 2 phrasings failed. Hook or accept?
      ```
-   - If AGENT_RULES.md was bootstrapped this run, say so (one line)
+   - Relay verbatim whatever `version-check.cjs` (step 0), `sync-rules.cjs` (step 1), and
+     `stub-check.cjs` (step 5) printed. Never re-word or summarize them: they are the
+     record of a file that was written or a version gap, and a paraphrase of "your body
+     was backed up to AGENT_RULES.md.bak" can lose the filename the user needs.
+   - Each is silent when nothing changed, so silence is the normal case and there is
+     nothing to invent — never report an action that produced no output.
+   - Never a silent write: if any of the three wrote or moved a file and you did not
+     relay its line, that is a defect.
    - If step 7 ran the auto re-index, say so and name the regenerated files
      (`docs/index.md`, plus `docs/log.md` if touched) so they are staged with this run
    - Confirm MEMORY.md and AGENTS.md updated
@@ -543,7 +612,8 @@ Reads all raw material (`.factory/stash/*.md` + `.factory/remember/friction/anti
 **File locations (all project-local — two dirs: `/stash` owns `.factory/stash/`, `/remember` owns `.factory/remember/`)**
 - Stash files: `.factory/stash/*.md`
 - Memory file: `.factory/remember/MEMORY.md` (single source of truth, referenced as `@.factory/remember/MEMORY.md`)
-- Rules template: `.factory/remember/AGENT_RULES.md` (bootstrapped once from the bundled package template on first `/remember` run, never overwritten again — user-owned after that; referenced by a plain path pointer, not `@`-referenced — see step 5)
+- Rules template: `.factory/remember/AGENT_RULES.md` (refreshed from the bundled package template every `/remember` run by `sync-rules.cjs`; a differing body is backed up first, not silently overwritten — referenced by a plain path pointer, not `@`-referenced — see step 5)
+- Rules backup: `.factory/remember/AGENT_RULES.md.bak` (written by `sync-rules.cjs` only when the existing body differs from the template; a single file, overwritten each time it fires — not timestamped)
 - Antigen ledger: `.factory/remember/ledger.json` (per-rule evidence trail: class, status, attempts/rejected-buffer, recurrence-while-hot)
 - Consolidation report: `.factory/remember/report.md` (latest step-8 report, overwritten each run)
 - Processed manifest: `.factory/remember/.processed`

package/packages/droid/commands/root-cause.md

@@ -0,0 +1,218 @@
+---
+description: Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time
+---
+
+# Root Cause
+
+**Find the cause before you change any code.**
+
+## The Law
+
+```
+NO FIX WITHOUT A CAUSE YOU CAN POINT AT
+```
+
+A fix at the place the error *appeared* is a symptom fix. It is a failure even when
+the symptom goes away, because the real cause is still there and will surface
+somewhere else, later, with less context.
+
+You cannot propose a fix until Phase 1 is done.
+
+## When to Use
+
+Any technical issue: a failing test, a production bug, unexpected behaviour, a
+performance problem, a broken build, an integration that will not talk.
+
+**Especially when it feels like overkill:**
+- Under time pressure — emergencies are exactly when guessing is most tempting and most expensive
+- "Just one quick fix" looks obvious
+- You have already tried a fix and it did not work
+- You do not fully understand the issue
+
+Simple bugs have root causes too, and finding one takes minutes. Guess-and-check
+takes hours and leaves damage behind.
+
+---
+
+## Phase 1 — Gather Evidence
+
+Do all of this **before** forming any opinion about the fix.
+
+### 1. Read the error completely
+
+Do not skim past it. Read the whole message, the whole stack trace, every warning
+above it. Note line numbers, file paths, error codes. The answer is often written
+there in full.
+
+### 2. Reproduce it consistently
+
+Can you trigger it on demand? What are the exact steps? Does it happen every time?
+
+If it is not reproducible, gather more data. Do not start guessing — an
+intermittent bug you cannot trigger is a bug you cannot prove you fixed.
+
+### 3. Check what changed
+
+Recent commits, the working diff, new dependencies, config edits, environment
+differences between the place it works and the place it does not.
+
+Be careful here: the most recent change is the most *available* suspect, not the
+most likely one. Recency is a lead to test, never a conclusion.
+
+### 4. Instrument the boundaries (multi-component systems)
+
+When the path crosses components — CI → build → sign, API → service → database,
+workflow → script → tool — do not reason about where it breaks. Measure it.
+
+For each boundary, log what goes **in** and what comes **out**, and confirm
+configuration and environment actually propagated across it.
+
+```bash
+echo "=== layer 1: is the secret present in the workflow? ==="
+echo "IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}"
+
+echo "=== layer 2: did it survive into the build script? ==="
+env | grep IDENTITY || echo "IDENTITY not in environment"
+
+echo "=== layer 3: what does the tool actually see? ==="
+security find-identity -v
+```
+
+Run it **once** to find which boundary fails, then investigate only that
+component. This turns "somewhere in the pipeline" into a named layer.
+
+### 5. Trace the bad value back to where it was born
+
+When the error surfaces deep in the call stack, the place it exploded is almost
+never the place it went wrong. Walk backwards.
+
+**The chain:**
+
+1. **Observe the symptom** — `git init` ran in the source directory
+2. **Find the immediate cause** — the code that directly did it:
+   `execFileAsync('git', ['init'], { cwd: projectDir })`
+3. **Ask what called this, and with what value** — `projectDir` was `''`, and an
+   empty `cwd` silently resolves to the process's own directory
+4. **Keep going up** — who passed the empty string? and who gave it to *them*?
+5. **Stop at the origin** — the point where a correct value first became wrong
+
+Fix it **there**. Then, if the value is dangerous, validate it at each layer on
+the way down as well, so the same mistake cannot recur through a different path.
+
+**When you cannot trace it by reading, instrument it:**
+
+```typescript
+async function gitInit(directory: string) {
+  console.error('DEBUG git init:', {
+    directory,
+    cwd: process.cwd(),
+    stack: new Error().stack,
+  });
+  await execFileAsync('git', ['init'], { cwd: directory });
+}
+```
+
+- Capture the **stack**, not just the value — it names the caller you are looking for
+- Log **before** the dangerous operation, not in its failure handler
+- Include surrounding context: the directory, the working directory, relevant environment
+- In tests, write to standard error directly; a project logger may be suppressed
+
+**When something pollutes a test run but you cannot tell which test:** bisect.
+Run the tests one at a time and stop at the first one that leaves the mess behind.
+`find-polluter.sh` in this skill's directory does exactly that.
+
+---
+
+## Phase 2 — Compare Against Something That Works
+
+You are looking for a difference, and the fastest way to see one is a side-by-side.
+
+- **Find a working example** — similar code in the same codebase that behaves correctly
+- **Read the reference completely** if you are following a pattern. Every line. Skimming a
+  reference and adapting "the idea" is how half-understood patterns ship
+- **List every difference**, however small. Do not filter by "that can't matter" — that
+  judgement is exactly what you do not have yet
+- **Check the dependencies**: what config, what environment, what other components does
+  the working one have that the broken one does not?
+
+---
+
+## Phase 3 — One Hypothesis, One Variable
+
+- **State it in writing:** "I think X is the cause, because Y." Specific, not vague.
+- **Test it with the smallest possible change.** One variable. A controlled test that
+  isolates your suspect beats a plausible story about the most recent commit.
+- **Read the result honestly.** Confirmed → Phase 4. Not confirmed → form a *new*
+  hypothesis. Never stack a second fix on top of an unconfirmed first one.
+- **Say when you do not know.** "I don't understand why X happens" is a real state and a
+  useful thing to report. Pretending to know produces confident wrong fixes.
+
+---
+
+## Phase 4 — Fix at the Source
+
+### 1. Write the failing test first
+
+The simplest reproduction you can manage — an automated test if there is a suite, a
+throwaway script if there is not.
+
+**Run it against the unfixed code and watch it fail, for the reason you expect.** A
+test written after the fix, or one that passes both before and after, proves nothing.
+This is the step that converts your hypothesis into evidence.
+
+### 2. Make one change
+
+Fix the cause you identified. One change. No "while I'm here" improvements, no bundled
+refactoring — those make it impossible to tell what actually worked.
+
+### 3. Verify
+
+Does the new test pass? Does the rest of the suite still pass? Is the original symptom
+actually gone — checked, not assumed?
+
+### 4. If the fix did not work, stop and count
+
+Under three attempts: return to Phase 1 with what you just learned. The failed attempt
+is evidence.
+
+**Three or more failed fixes means you have the wrong model of the problem.** Do not
+attempt a fourth. The pattern to watch for: each fix uncovers a new problem somewhere
+else, or each one needs "just a bit of refactoring" to land.
+
+That is an architecture question, not a hypothesis question. Stop and raise it.
+
+---
+
+## Red Flags — Stop and Return to Phase 1
+
+- "Quick fix now, investigate later"
+- "Just try changing X and see"
+- Several changes at once, then run the tests
+- "Skip the test, I'll check it by hand"
+- "It's probably X" — probably is not a cause
+- "I don't fully understand this, but this might work"
+- Listing fixes before tracing where the bad value came from
+- "One more attempt" when two have already failed
+- Each fix revealing a new problem somewhere else
+
+## Quick Reference
+
+| Phase | You do | Done when |
+|---|---|---|
+| **1. Evidence** | Read the error, reproduce, check changes, instrument boundaries, trace the value back | You can say what happened and where it started |
+| **2. Compare** | Find a working case, read it fully, list every difference | You know what is different |
+| **3. Hypothesis** | State one cause, test one variable | Confirmed, or you have a new hypothesis |
+| **4. Fix** | Failing test first, one change, verify | The test that failed now passes, and nothing else broke |
+
+## When There Really Is No Root Cause
+
+It happens — a genuine race, an upstream bug, a hardware fault. But roughly nineteen
+times in twenty, "no root cause" means the investigation stopped early.
+
+Before you conclude it: can you reproduce it? Did you instrument every boundary? Did
+you trace the value to its origin, or only to the last function you recognised?
+
+## Related
+
+- **AGENT_RULES.md → Testing Standards** — what makes the Phase 4 test a real one
+- **`/test-generate`** — build out the suite once the cause is fixed

package/packages/droid/commands/security.md

@@ -1,9 +1,6 @@
 ---
-name: security
 description: Security audit — recurring six, injection, auth, trust boundaries
-usage: /security
 argument-hint: [file, directory, or leave empty for full scan]
-allowed-tools: Read, Grep, Glob, Bash(git log *), Bash(git grep *), Bash(rg *)
 ---
 Audit $ARGUMENTS for security vulnerabilities. **Reports, never edits** — it
 verifies every claim, then hands the findings to whoever asked.

package/packages/droid/commands/ship.md

@@ -1,8 +1,5 @@
 ---
-name: ship
 description: Mechanical pre-deploy gate — tests, build, tree state
-usage: /ship
-allowed-tools: Read, Grep, Glob, Bash(git *), Bash(npm *), Bash(pnpm *), Bash(yarn *), Bash(pytest *), Bash(python *), Bash(go *), Bash(cargo *), Bash(make *)
 ---
 Mechanical pre-deploy / pre-merge gate. Every item here is answerable by
 **running a command** and reading its exit code — no code judgment. Code

package/packages/droid/commands/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/packages/droid/commands/skill-creator.md

@@ -1,9 +1,5 @@
 ---
-name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
-usage: /skill-creator <skill-type> <skill-description>
-auto_trigger: false
-license: Complete terms in LICENSE.txt
 ---
 
 # Skill Creator

package/packages/droid/commands/stash.md

@@ -1,7 +1,5 @@
 ---
-name: stash
 description: Stash session context [name]
-usage: /stash ["optional-name"]
 argument-hint: [optional stash name]
 ---
 

package/packages/droid/commands/test-generate.md

@@ -1,9 +1,6 @@
 ---
-name: test-generate
 description: Generate and run tests [file]
-usage: /test-generate <file>
 argument-hint: [file or symbol to test]
-allowed-tools: Read, Edit, Write, Grep, Glob, Bash(npm test *), Bash(npx jest *), Bash(npx vitest *), Bash(pnpm test *), Bash(yarn test *), Bash(pytest *), Bash(python *), Bash(go test *), Bash(cargo test *), Bash(make test *)
 ---
 Generate tests for $ARGUMENTS, then run them. This is a generate → run →
 verify loop, not just file generation.
@@ -28,7 +25,7 @@ Match existing patterns:
   or new test-runner config.
 - Do **not** add test-only public methods or exports to production code to
   make a test possible — if the test wants a hook the prod code doesn't
-  expose, stop and ask (`test-traps` territory).
+  expose, stop and ask.
 
 ## 3. Run
 Execute the project's real test command, scoped to just the new tests