@drawbridge/drawbridge-agents 0.1.35 → 0.1.37

package/.claude-template/settings.json

@@ -35,6 +35,24 @@
       "../drawbridge-website"
     ]
   },
+  "extraKnownMarketplaces": {
+    "ponytail": {
+      "source": {
+        "source": "github",
+        "repo": "DietrichGebert/ponytail"
+      }
+    },
+    "humanizer": {
+      "source": {
+        "source": "github",
+        "repo": "blader/humanizer"
+      }
+    }
+  },
+  "enabledPlugins": {
+    "ponytail@ponytail": true,
+    "humanizer@humanizer": true
+  },
   "hooks": {
     "PreToolUse": [
       {

package/.claude-template/skills/drawbridge-asana-ship-handoff/SKILL.md

@@ -40,14 +40,23 @@ need to retest. Use this right after merging the work to `develop` (which deploy
    **Open with an @-mention of the reassignee** — use `html_text` and start the body with
    `<a data-asana-gid="<their user gid>"/>` (Asana expands it into a proper mention). A
    comment without a mention may notify no one; reassignment alone is easy to miss.
-4. **Confirm before writing.** This posts to an external system. Show the user the chosen
+4. **Run the draft through `humanizer`.** A real teammate reads this, and generated-sounding
+   prose reads as effort nobody spent. Invoke the `humanizer` skill on the drafted body: it
+   strips the AI tells — inflated claims, hedging, stock transitions, "it's worth noting",
+   restating the ask twice.
+
+   It pulls in the same direction as the word limit above, so apply it *before* the final
+   trim and re-check the result against both rules. Two things it must not touch: the
+   `<a data-asana-gid="..."/>` mention (leave the markup exactly as-is) and any concrete
+   detail from the Retest steps — if a pass makes the steps vaguer, keep the original wording.
+5. **Confirm before writing.** This posts to an external system. Show the user the chosen
    assignee and the drafted comment and get a go-ahead, unless they've told you to proceed
    without asking.
-5. **Apply** (on approval):
+6. **Apply** (on approval):
    - `asana_update_task` — set `assignee` to the last commenter's gid and `due_at` to the
      current date/time (ISO 8601).
    - `asana_create_task_story` — post the comment.
-6. **Report** the task URL, who it was assigned to, and confirm the due date was updated.
+7. **Report** the task URL, who it was assigned to, and confirm the due date was updated.
 
 ## Notes
 

package/.claude-template/skills/drawbridge-ship-feature/SKILL.md

@@ -14,13 +14,22 @@ knowledge graph, and the Asana handoff so nothing drifts at ship time.
 1. **Verify it works.** Run the project's verification (the `verify` skill / build / lint /
    manual smoke — there's no unit-test framework in api/sync/app-web). Confirm the behaviour
    end-to-end, not just that it compiles.
-2. **Reconcile the spec.** Find the matching `drawbridge-docs` user story by its
+2. **Review the diff for over-engineering.** Invoke the `ponytail-review` skill on the change
+   before it merges. It reports one line per finding — reinvented stdlib, a dependency that
+   wasn't needed, a speculative abstraction, flexibility nothing calls. Act on what's real and
+   say why you're keeping anything you skip; a finding that survives review deliberately is
+   fine, one that survives because nobody looked is how the family accretes code. This is the
+   cheapest point to cut it — after merge it's someone else's inheritance.
+
+   Ponytail's baseline is already ambient (a SessionStart hook applies it at `full` intensity
+   family-wide), so this step is the explicit diff pass, not the switch that turns it on.
+3. **Reconcile the spec.** Find the matching `drawbridge-docs` user story by its
    `<domain>/<slug>` ID (or the relevant `reference/` doc). If behaviour changed, update the
    story in the same change (use `write-user-stories` for a new/edited story). If you can't,
    flag the drift explicitly. See `conventions/docs-linkage.md`.
-3. **Confirm doc anchors resolve.** Run `npx drawbridge-agents-check-docs`; fix any unresolved
+4. **Confirm doc anchors resolve.** Run `npx drawbridge-agents-check-docs`; fix any unresolved
    `@story` / `@doc` tag. Add an anchor to newly-added feature code where it maps to a story.
-4. **Refresh the knowledge graph — always, on every feature wrap** (not conditional on whether
+5. **Refresh the knowledge graph — always, on every feature wrap** (not conditional on whether
    structure "obviously" changed). The canonical graph is the committed snapshot in
    `drawbridge-docs`, shared by the whole team; skipping it lets the shared graph drift. From the
    `drawbridge-docs` repo: `npx drawbridge-agents-graph` (rebuilds `knowledge/graphs/global.json`
@@ -28,9 +37,9 @@ knowledge graph, and the Asana handoff so nothing drifts at ship time.
    knowledge graph (<feature>)" && git push origin main`. If it reports "graphify runtime not
    found", the `uv`/`graphify` binaries are in `~/.local/bin` — `export PATH="$HOME/.local/bin:$PATH"`
    and retry (do NOT run `graphify install`; it rewrites `CLAUDE.md`).
-5. **Hand off the task.** Invoke `drawbridge-asana-ship-handoff` with the Asana task to reassign
+6. **Hand off the task.** Invoke `drawbridge-asana-ship-handoff` with the Asana task to reassign
    to the last commenter, post the change summary + retest steps, and set the due date.
-6. **Clear the worktree.** If the feature was built in a git worktree (a sibling directory or a
+7. **Clear the worktree.** If the feature was built in a git worktree (a sibling directory or a
    `.worktrees/` folder), remove it now that the branch is merged: from the main checkout,
    `git worktree remove <path>` then `git worktree prune`. If the removal complains about
    uncommitted changes, inspect them first — add `--force` only once you've confirmed the dirt
@@ -39,6 +48,6 @@ knowledge graph, and the Asana handoff so nothing drifts at ship time.
 
 ## Notes
 
-- Steps 2–4 are what the drift-check Stop hook enforces; running them here means you won't get
+- Steps 3–5 are what the drift-check Stop hook enforces; running them here means you won't get
   blocked at turn end.
 - "Shipped" in this family means merged to `develop` (that's the deployed dev environment).

package/README.md

@@ -20,7 +20,8 @@ claude/
   CLAUDE.md                 ← aggregator — @-imports every conventions/*.md
 
 .claude-template/           ← the complete shared .claude/, mirrored into each consumer repo
-  settings.json             ← permissions, additionalDirectories, drift-check Stop hook
+  settings.json             ← permissions, additionalDirectories, drift-check Stop hook,
+                              family-wide plugin marketplaces + enabledPlugins
   skills/                   ← shared skills (drawbridge-ship-feature, -asana-ship-handoff, ...)
   hooks/  agents/  commands/
 

package/conventions/cross-repo-contracts.md

@@ -48,6 +48,15 @@ skill) so it stops living only in tribal memory.
   `ads-republishing.<connectionId>`). Never unique-index `coalesce` (superseding requires the
   second insert to land), and writes that set `key` need the writer-side E11000 handler or a
   replayed event logs a false error.
+- **Adding an email/SMS vendor is a two-repo change** (api ↔ sync). A connection is deliverable
+  only if sync implements a sender for its slug — `lib/email.js` (`{ mailchimp, sendgrid }`) and
+  `lib/sms.js` (`{ twilio }`), which `queue/notification.js` reads **directly** as its guard and
+  org-scoped lookup; never re-list the slugs as literals, or the guard drifts from the senders
+  that exist. Adding a vendor to drawbridge-api `lib/connections.js` with `group : 'email'`/`'sms'`
+  makes it selectable throughout api and app-web, but with no sync sender every send is
+  cancelled, not delivered — merchant sees a workflow that ran and no message. The miss is
+  detectable, not silent: `notification.reason = 'connection-slug-mismatch'` plus an
+  Error-instance `logger.error` (a string never reaches Sentry Issues — see `sentry-sdk.md`).
 - Schema-gated fields ship **api-first, booted**: a sibling writer setting a field new to a
   drawbridge-api `$jsonSchema` (validators are strict + `additionalProperties: false`) must not
   go live until the api has **booted** with the schema change on that environment — creating the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drawbridge/drawbridge-agents",
-  "version": "0.1.35",
+  "version": "0.1.37",
   "description": "Shared agent-instruction content (rules, code style, conventions) for the drawbridge-* monorepo.",
   "license": "UNLICENSED",
   "publishConfig": {