toga-ai 1.0.235 → 1.0.236

package/knowledge/1.0/standards/framework-rules.md

@@ -99,6 +99,19 @@ Before creating a new class in a 1.0 repo:
 3. Follow the naming convention exactly, including the type segment.
 4. If you are adding a class to the `library` core repo, be aware it affects all 1.0 apps — review `knowledge/1.0/apps/library/architecture.md` first.
 
+## Schema migrations — always in `dbchanges`
+
+**Application repos (`worker`, `togadesk`, `togaview`, `tools`, and any other 1.0 app)
+contain no standalone `.sql` migration or schema files.** All schema changes for any
+1.0 database — table creation, `ALTER` statements, index changes, seed data — go in the
+**`dbchanges`** repo.
+
+This rule applies regardless of which application repo the feature lives in. Even if you
+are adding a column that only `worker` reads, the `.sql` file goes in `dbchanges`.
+
+Never create a `.sql` file inside a 1.0 application repo. The SQL that belongs in those
+repos is only query strings embedded in PHP code — not standalone migration files.
+
 ## Error handling in controllers
 
 Controllers must not let exceptions bubble up to the framework unhandled. Catch specific exceptions, log them, and return an appropriate response.

package/knowledge/2.0/apps/worker2/architecture.md

@@ -39,6 +39,13 @@ processes background jobs. It's a `_underscore` 2.0 app (`index.php` is just
 | S3 `agilant-worker-fallback` | Failed webhook payloads (`webhook-fallback/{uuid}.json`, 7-day lifecycle). |
 | API Gateway `WorkerWebhookIngestion` | `webhook.togahub.com` → Lambda. Lambda Function URLs are blocked by an AWS Org SCP, so API Gateway is the only public entry point. |
 
+## Critical repo rule — no SQL migration files
+
+**This repo contains PHP and Python only. Never create `.sql` schema-migration files here.**
+All table creation, `ALTER` statements, index changes, and seed data — including for
+`Core.WorkerJobs` and `Core.CronJobs` — go in the `dbchanges2` repo using its
+`YYYY-MM-DD<letter> - <Description>.sql` naming convention.
+
 ## MySQL tables
 
 **`Core.WorkerJobs`** — unified execution record. Key columns: `uuid`,

package/knowledge/2.0/standards/backend-php.md

@@ -22,6 +22,14 @@ related:
 
 ## Database/SQL
 
+### Migration files belong in `dbchanges2`
+
+SQL query strings embedded in PHP code (SELECTs, INSERTs, UPDATEs) live in this repo as
+part of normal PHP files. **Standalone `.sql` migration files do not.** Any schema change
+— CREATE TABLE, ALTER TABLE, new index, seed rows — must be placed in the `dbchanges2`
+repo, not here. See `2.0/standards/framework-rules.md` § Schema migrations for naming
+conventions.
+
 ### Table Design
 
 #### **Order of Fields**

package/knowledge/2.0/standards/framework-rules.md

@@ -86,6 +86,22 @@ return [
 ];
 ```
 
+## Schema migrations — always in `dbchanges2`
+
+**Application repos (`worker2`, `api2`, `_underscore`) contain no standalone `.sql`
+migration or schema files.** All schema changes for any 2.0 database — table creation,
+`ALTER` statements, index changes, seed data — go in the **`dbchanges2`** repo.
+
+File naming in `dbchanges2`: `YYYY-MM-DD<letter> - <Description>.sql`
+(e.g. `2026-06-30a - Add WorkerJobs failureCode column.sql`).
+
+This rule applies regardless of which application repo the feature lives in. Even if you
+are adding a column that only `worker2` reads, the `.sql` file goes in `dbchanges2`.
+
+Never create a `.sql` file inside `worker2`, `api2`, `_underscore`, or any other 2.0
+application repo. The SQL that belongs in those repos is only query strings embedded in
+PHP code — not standalone migration files.
+
 ## Checking dependencies before touching shared code
 
 `dependsOn` in `knowledge/registry.json` means a repo extends or depends on another repo's classes. Before modifying a class in a dependency repo (e.g. `_underscore` core):

package/package.json

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