toga-ai 1.0.533 → 1.0.534
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/knowledge/INDEX.md
CHANGED
|
@@ -39,7 +39,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
|
|
|
39
39
|
- **togatech** (TOGA Technology Website) — 4 doc(s) → [standalone/apps/togatech/INDEX.md](standalone/apps/togatech/INDEX.md)
|
|
40
40
|
- **websocket** (WebSocket Server) — 2 doc(s) → [standalone/apps/websocket/INDEX.md](standalone/apps/websocket/INDEX.md)
|
|
41
41
|
- **forward** (Forwarder) — 3 doc(s) → [standalone/apps/forward/INDEX.md](standalone/apps/forward/INDEX.md)
|
|
42
|
-
- **claude** (Claude Harness) —
|
|
42
|
+
- **claude** (Claude Harness) — 6 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
|
|
43
43
|
|
|
44
44
|
## Clients
|
|
45
45
|
|
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Deploy Instructions — lead with SQL, state exact order
|
|
3
|
+
framework: "standalone"
|
|
4
|
+
repo: claude
|
|
5
|
+
project: Claude Harness
|
|
6
|
+
client: shared
|
|
7
|
+
type: standard
|
|
8
|
+
status: active
|
|
9
|
+
updated: 2026-08-05
|
|
10
|
+
owners: ["jcardinal"]
|
|
11
|
+
files: []
|
|
12
|
+
related:
|
|
13
|
+
- 2.0/apps/dbchanges2/workflows/local-vs-prod-mysql-config-parity.md
|
|
14
|
+
- 1.0/apps/dbchanges/workflows/authoring-and-shipping-sql-files.md
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
# Deploy Instructions — lead with SQL, state exact order
|
|
18
|
+
|
|
19
|
+
When a change is ready to deploy, Claude states the deploy steps **clearly and briefly** — an
|
|
20
|
+
actionable checklist, never a prose paragraph. This applies to **every** developer and **both**
|
|
21
|
+
frameworks (1.0 and 2.0).
|
|
22
|
+
|
|
23
|
+
## The rule
|
|
24
|
+
|
|
25
|
+
1. **Lead with the SQL.** State which `.sql` file(s) to run and in **exactly what order**, by
|
|
26
|
+
**exact filename** (e.g. `dbchanges2/Logs/2026-08-05a - Issue status baseline and
|
|
27
|
+
auto-resolution.sql`) — never "run the migration".
|
|
28
|
+
2. **Then the deploys.** List which repos/apps to deploy, in order.
|
|
29
|
+
3. **Flag the order-critical step in one line, with why.** Schema-before-code is load-bearing:
|
|
30
|
+
deploying code before its migration crashes on the missing columns (in 2.0 a missing column in
|
|
31
|
+
a working-set SELECT is a runtime exception, not a null). Say which single step cannot be
|
|
32
|
+
reordered and the one-line consequence of getting it wrong.
|
|
33
|
+
4. **Plain and non-verbose.** No narrative. A developer should be able to execute it top to bottom
|
|
34
|
+
without re-reading.
|
|
35
|
+
|
|
36
|
+
## Example (shape to follow)
|
|
37
|
+
|
|
38
|
+
> Deploy order:
|
|
39
|
+
> 1. Run `dbchanges2/Logs/2026-08-05a - Issue status baseline and auto-resolution.sql` on the Logs
|
|
40
|
+
> DB **first**.
|
|
41
|
+
> 2. Then deploy `_underscore`, `worker2`, `tools`.
|
|
42
|
+
>
|
|
43
|
+
> Order-critical: step 1 before step 2 — code before the migration crashes `loadWorkingSet` on the
|
|
44
|
+
> missing `status`/baseline columns.
|
|
45
|
+
|
|
46
|
+
## Why
|
|
47
|
+
|
|
48
|
+
Developers need an executable checklist, not prose, to deploy safely and fast. Naming exact files
|
|
49
|
+
and flagging the one order-critical step is what prevents the schema-before-code failure that takes
|
|
50
|
+
down a running app.
|
|
51
|
+
|
|
52
|
+
## Change history
|
|
53
|
+
- 2026-08-05 — Standard recorded: deploy instructions lead with the exact SQL file(s) and order,
|
|
54
|
+
then the repos, and flag the one order-critical step and why. Cross-framework (1.0 + 2.0).
|
|
55
|
+
(jcardinal)
|
|
56
|
+
</content>
|
package/package.json
CHANGED