toga-ai 1.0.533 → 1.0.535

package/knowledge/INDEX.md

@@ -39,7 +39,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **togatech** (TOGA Technology Website) — 4 doc(s) → [standalone/apps/togatech/INDEX.md](standalone/apps/togatech/INDEX.md)
 - **websocket** (WebSocket Server) — 2 doc(s) → [standalone/apps/websocket/INDEX.md](standalone/apps/websocket/INDEX.md)
 - **forward** (Forwarder) — 3 doc(s) → [standalone/apps/forward/INDEX.md](standalone/apps/forward/INDEX.md)
-- **claude** (Claude Harness) — 5 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
+- **claude** (Claude Harness) — 7 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
 
 ## Clients
 

package/knowledge/standalone/standards/communication-clarity.md

@@ -0,0 +1,59 @@
+---
+title: Communication — short, clear, plain words
+framework: "standalone"
+repo: claude
+project: Claude Harness
+client: shared
+type: standard
+status: active
+updated: 2026-08-05
+owners: ["jcardinal"]
+files: []
+related:
+  - standalone/standards/deploy-instruction-communication.md
+---
+
+# Communication — short, clear, plain words
+
+Claude talks to the whole team. Many teammates do not speak English as a first language.
+So Claude keeps every message **short, clear, and to the point** — in thoughts, plans, and
+answers. This applies to **all** developers, **both** frameworks, and **every** session.
+
+This is a team directive, not a style tip. Follow it by default.
+
+## The rules
+
+1. **Be short.** Say the thing, then stop. Cut every sentence that does not help the reader
+   act or decide. If one line works, use one line.
+2. **Use plain words.** Prefer common words over rare or fancy ones. If a simpler word means
+   the same thing, use it.
+3. **No obscure jargon.** Do not use uncommon technical terms like "sargability",
+   "idempotent", "cardinality" without a short plain-English note. Better: skip the term and
+   say what it means. Example: instead of "make the query sargable", say "let the query use
+   the index (no function on the indexed column)".
+4. **Still be technical enough.** The team are developers. Keep the real detail — file names,
+   errors, exact steps. Be brief, not vague. Short does not mean leaving out what matters.
+5. **Lead with the answer.** Put the point first. Add reasons after, only if needed. Do not
+   build up to the answer with a long intro.
+6. **Use lists and steps.** For anything with more than two parts, use a numbered or bulleted
+   list, not a paragraph.
+7. **Deploy steps follow their own rule.** See [[deploy-instruction-communication]] — lead with
+   the exact SQL file(s) and order, then repos.
+
+## Quick check before sending
+
+- Can I cut half the words and keep the meaning? Then cut them.
+- Is there a rare word a non-native English reader might not know? Replace it.
+- Did I say the main point in the first line? If not, move it up.
+
+## Why
+
+Long, wordy, jargon-heavy answers are hard and tiring to read, especially for non-native
+English speakers. The team moves faster when Claude is brief and plain. Clear beats clever.
+
+## Change history
+- 2026-08-05 — Standard recorded: keep all communication short, clear, and plain; avoid
+  obscure jargon (e.g. "sargability"); lead with the answer; stay technical but brief.
+  Team-wide, both frameworks. (jcardinal)
+</content>
+</invoke>

package/knowledge/standalone/standards/deploy-instruction-communication.md

@@ -0,0 +1,56 @@
+---
+title: Deploy Instructions — lead with SQL, state exact order
+framework: "standalone"
+repo: claude
+project: Claude Harness
+client: shared
+type: standard
+status: active
+updated: 2026-08-05
+owners: ["jcardinal"]
+files: []
+related:
+  - 2.0/apps/dbchanges2/workflows/local-vs-prod-mysql-config-parity.md
+  - 1.0/apps/dbchanges/workflows/authoring-and-shipping-sql-files.md
+---
+
+# Deploy Instructions — lead with SQL, state exact order
+
+When a change is ready to deploy, Claude states the deploy steps **clearly and briefly** — an
+actionable checklist, never a prose paragraph. This applies to **every** developer and **both**
+frameworks (1.0 and 2.0).
+
+## The rule
+
+1. **Lead with the SQL.** State which `.sql` file(s) to run and in **exactly what order**, by
+   **exact filename** (e.g. `dbchanges2/Logs/2026-08-05a - Issue status baseline and
+   auto-resolution.sql`) — never "run the migration".
+2. **Then the deploys.** List which repos/apps to deploy, in order.
+3. **Flag the order-critical step in one line, with why.** Schema-before-code is load-bearing:
+   deploying code before its migration crashes on the missing columns (in 2.0 a missing column in
+   a working-set SELECT is a runtime exception, not a null). Say which single step cannot be
+   reordered and the one-line consequence of getting it wrong.
+4. **Plain and non-verbose.** No narrative. A developer should be able to execute it top to bottom
+   without re-reading.
+
+## Example (shape to follow)
+
+> Deploy order:
+> 1. Run `dbchanges2/Logs/2026-08-05a - Issue status baseline and auto-resolution.sql` on the Logs
+>    DB **first**.
+> 2. Then deploy `_underscore`, `worker2`, `tools`.
+>
+> Order-critical: step 1 before step 2 — code before the migration crashes `loadWorkingSet` on the
+> missing `status`/baseline columns.
+
+## Why
+
+Developers need an executable checklist, not prose, to deploy safely and fast. Naming exact files
+and flagging the one order-critical step is what prevents the schema-before-code failure that takes
+down a running app.
+
+## Change history
+- 2026-08-05 — Standard recorded: deploy instructions lead with the exact SQL file(s) and order,
+  then the repos, and flag the one order-critical step and why. Cross-framework (1.0 + 2.0).
+  (jcardinal)
+</content>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.533",
+  "version": "1.0.535",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",