toga-ai 1.0.1063 → 1.0.1064

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

@@ -156,6 +156,8 @@ VALUES (4188, '<pre-generated v4 uuid>', 219, 'serviceAddressId');
 
 Because the `id`s must be reserved by a human, **this cannot be guessed or derived** — asking is mandatory. Record the assigned values in a comment at the top of the file so the next reader knows they were allocated, not invented.
 
+**`/finish` always reports the central ids** — every `Records` / `RecordFields` id the ticket inserted (id → route / route.field) plus the next free ids, or "none used by this ticket". Every time, never skipped: the developer copies the next ids into Tools → Developers → Central IDs.
+
 #### The next free `id` is NOT the same in every environment
 
 The rule above keeps *existing* ids aligned, but each environment's `Core` has drifted independently, so **the next free value differs**. Verified 2026-08-17: the same new `ServiceRequests._serialNumbers` recordField took id **2483 in production** and **2766 in dev-sandbox**. Consequences:
@@ -398,5 +400,6 @@ The extra `SELECT … FROM ( … ) existing` layer both dodges error 1093 and pi
 
 ## Change history
 
+- 2026-10-17 — /finish reports central ids used + next free (TRUE-82889). (jcardinal)
 - 2026-10-17 — Second same-folder file also allowed for interceptor rows that must run after the code deploy (TRUE-82889). (jcardinal)
 - 2026-10-13 — Added rule 15: no MySQL `CHECK` constraints (TRUE-82715). (jcardinal)

package/package.json

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

package/rules/common/communication.md

@@ -69,6 +69,9 @@ rows for the developer to write by hand.
 4. **Put verify SELECTs at the end of the file.** After the developer runs it, Claude runs
    those SELECTs itself (local DB, or `toga-db` read-only) and reports the result in plain
    words. Never ask the developer to read verify output.
+5. **Central ids at `/finish`** (team rule, 2026-10-17, jcardinal). When a ticket inserts
+   `Core.Records` / `Core.RecordFields` rows, the `/finish` report always lists the ids used
+   and the next free ids.
 
 ## No running commentary — one compiled report at the end (team rule, 2026-10-15)
 

package/skills/finish/SKILL.md

@@ -460,6 +460,8 @@ CU-<internalId>
 
 ## Migration steps
 - <dbchanges2 file + database + order, config changes, queue registration — or "None">
+- Central ids: <Records / RecordFields ids used, then "next free: Records <n>, RecordFields <n>"
+  — or "none used">   (dbchanges2 PRs only; same data as the Step 17 block)
 
 ## Review summary
 **Risk: <LEVEL>**
@@ -578,10 +580,27 @@ developer the list name and leave the status alone.
 Short list:
 
 1. KB: publish status (Step 5).
-2. Ticket fields changed: before → after with the reason, one line each (or "none").
-3. PRs: one url per repo, and which were created vs. updated.
-4. PM comment: posted (yes/no), with the posted text.
-5. Status: `development finished` (or why not).
-6. Anything manual the developer must still do — as a numbered list.
+2. **Central ids — REQUIRED, always present, never skipped** (team rule, 2026-10-17). Its own
+   block with a clear heading, right after the KB line: the developer must copy the next ids
+   into Tools → Developers → Central IDs.
+   - Source: grep the ticket branch's dbchanges2 `Core/` SQL files for `INSERT INTO Records` /
+     `INSERT INTO RecordFields` ids. Confirm on the local DB:
+     `SELECT id, … FROM Core.Records WHERE id IN (…)`, the same for `Core.RecordFields`, and
+     `SELECT MAX(id)` on both.
+   - List every id: `Records <id> → <route>`, `RecordFields <id> → <route>.<field>`.
+   - Then: `Next free: Records <n>, RecordFields <n>` — n = the higher of (this ticket's top
+     id, local `MAX(id)`) + 1. Central IDs stays the source of truth.
+   - None inserted → write `Central ids: none used by this ticket.`
+   ```
+   **Central ids**
+   - Records 412 → desk/tickets
+   - RecordFields 9031 → desk/tickets.priority
+   Next free: Records 413, RecordFields 9032
+   ```
+3. Ticket fields changed: before → after with the reason, one line each (or "none").
+4. PRs: one url per repo, and which were created vs. updated.
+5. PM comment: posted (yes/no), with the posted text.
+6. Status: `development finished` (or why not).
+7. Anything manual the developer must still do — as a numbered list.
 
 After that, if the thread may continue another day, suggest `/session-save <slug>`.