feat: 3.12.0 — standard words on the outside, so nothing has to be learned before it works

[devin-ai-integration]

Summary

Adoption was gated on vocabulary. The biggest offender was the one string a host reads before deciding to load a skill — the frontmatter description — which triggered on @fde plus nouns only we use ("hygiene", "receipts"). An FDE who simply talked about their client got no memory at all.

-description: … Use when the human says @fde or asks about client memory, debrief, prep,
-             receipts, trust, hygiene, or sponsor status …
+description: Keeps engagement memory for client work - sponsor, promise, what shipped,
+             who accepted it. Use when the human names a client, customer or stakeholder.
+             Use when they debrief a meeting or paste notes from one. Use when they ask
+             what was agreed, or want dates and receipts. Use when they prep a client
+             meeting or readout, when scope or trust shifts, or when they say @fde. …

@fde survives as one trigger among several rather than the password. Two gates in check.js keep it that way: the description must carry several Use when … clauses, and must not re-gate on @fde. Kept it to ~95 words so the routing eval's leanness nit stays clear.

fde tidy is the verb; fde garden still works. "Garden" was a metaphor only we used. Nothing is removed — same code, and the output strings moved with the name (TIDY (contract: …), Nothing to tidy., fde tidy --apply, (tidy dedupe)), which is what makes the rename real rather than cosmetic.

// `garden` was the name through 3.11.x; it keeps working.
case 'tidy':
case 'garden': cmdGarden(args); break

capture and preserve left the human help. Only hooks call them; listing them as verbs invited an FDE to run a snapshot by hand and wonder why nothing happened. Both still route.

One glossary, gated. The six words that carry the method (fieldbook, brief vs reality, terrain, trust signal, receipts, vault) are now defined once in the README instead of being met scattered and guessed.

Positioning: "engagement memory for AI coding agents" replaces "second brain" across npm, plugin and marketplace descriptions — searchable, and accurate. README examples drop the prefix (New client, Garvey. …) since naming a client is now enough to trigger.

A README gate also pins the advertised installer to --skill fde, so the documented command can't drift back to also installing the contributor-only testing-fieldbook.

Not renamed: the memory files. Existing users would pay a migration for cosmetics.

npm run check green — gates plus 120 tests, including a regression test asserting tidy and garden produce byte-identical output and that neither degrades to the usage banner.

Link to Devin session: https://app.devin.ai/sessions/f135381c4682413bae73dff38eb6d1a3
Open in Devin Desktop: https://app.devin.ai/desktop/session/f135381c4682413bae73dff38eb6d1a3?variant=devin
Requested by: @suboss87

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring