toga-ai 1.0.1063 → 1.0.1065

package/knowledge/2.0/apps/_underscore/INDEX.md

@@ -23,6 +23,7 @@
 | [_Config group access — the two-argument "optional" form does NOT rescue a missing GROUP](features/config-group-access.md) | `_Config::<group>('prop', false)` does NOT rescue a MISSING GROUP (only a missing prop) — guard with `_Config::isGroupSet()`; open before reading per-environmen |
 | [Contacts require a customerId — the Internal customer & every contact-creation path](features/contact-customer-required-internal-customer.md) | Every `Client_<Tenant>.Contacts` row must have a `customerId`; with no real customer, use the shared Internal customer (fixed uuid in every tenant). |
 | [Core.Domains — the app host registry (and why you cannot derive a host)](features/core-domains-app-host-registry.md) | `Core.Domains` is the authoritative host↔client↔app↔env registry; a host is NOT derivable from env slug or api host — read the table. |
+| [Customer related records — primary location, Locations_Customers, files, notes](features/customer-locations-files-notes.md) | Shared Client-DB data model around a Customer (locations, files, notes, contact count); open before linking anything to a customer or listing a customer's locat |
 | [Re-pointing a DB alias mid-request (_Database::register park/restore)](features/database-alias-repointing.md) | `_Database` keys **all live per-database runtime state by the connection ALIAS** (`Client` / `_underscore::DB_CLIENT`, `ClientLogs`, `Archive`), **not** by the |
 | [Effective persona resolution (_Model_Client_User::_personaIds) — the three sources and the sector hop](features/effective-persona-resolution.md) | A user's EFFECTIVE persona set = UNION of three sources (`Users_Personas` + own-location + 5-hop sector `Locations_Personas`), owned by `_personaIds()`; open be |
 | [2.0 Email Send Pipeline (queue + Send worker)](features/email-send-pipeline.md) | In 2.0, `_Email::send()` **does not transmit** — it queues the message. |
@@ -49,6 +50,7 @@
 | [Persona nav-visibility gate + user nav pins (keyed by Core.SurfaceElements uuid)](features/persona-nav-visibility-gate.md) | Sidebar-nav persona gate in `_Model_Core_Surface` (`Client.PersonaNavVisibility`) and user nav pins (`Client.UserNavPreferences`), both keyed by Core `SurfaceEl |
 | [Record activity timeline (GET /v2/record-logs/timeline, _Component_RecordActivity)](features/record-activity-timeline.md) | Generic per-record activity feed built from Logs_<Tenant>; open when adding a new timeline root, hiding noise fields, or debugging a missing activity row. |
 | [Record Change Audit Log (Logs_<Client>.Record / RecordField) — reading a field's history](features/record-change-audit-log.md) | Field-level change audit trail per tenant; open to answer "who changed this field, to what, when" or to tell a direct SQL edit from an in-app change. |
+| [Record hard delete (_Component_RecordDelete + PRE DELETE interceptor)](features/record-hard-delete.md) | Map-driven hard delete of everything hanging off one record (block / detach / delete children / orphan Files); open before making a record deletable or adding a |
 | [Records meta endpoint (GET /v2/records/meta) — record names, label fields, translated field labels](features/record-meta-endpoint.md) | Per-route record meta (names, label/sublabel field, per-field display labels); open when a screen needs a record's or a field's visible name, or when adding a f |
 | [Recursive Item Fulfillments (upstream mirroring)](features/recursive-item-fulfillments.md) | Engine that mirrors a downstream ItemFulfillment up the SO→PO→SO chain onto every customer-facing SO; open when touching IF creation, bundle scaling, or upstrea |
 | [Sales-order denial reason (`ApprovalDecisions.note`) — capture, the denial-details card, and the read-only workflow mode](features/sales-order-denial-reason.md) | Map of the SO approval denial reason (`ApprovalDecisions.note`) — where it is written, read, and displayed; open when building any denial-reason display, banner |

package/knowledge/2.0/apps/_underscore/features/customer-locations-files-notes.md

@@ -0,0 +1,71 @@
+---
+title: Customer related records — primary location, Locations_Customers, files, notes
+framework: "2.0"
+repo: _underscore
+project: _Underscore
+client: shared
+type: feature
+status: active
+updated: 2026-10-17
+owners: [jcardinal]
+files:
+  - _underscore/Model/Client/Customer.php
+  - _underscore/Model/Client/Locations/Customer.php
+  - _underscore/Model/Client/Customers/File.php
+  - _underscore/Model/Client/CustomerNote.php
+  - dbchanges2/Core/2026-10-17b - CustomerLocationsFilesNotesActivity.sql
+  - dbchanges2/Client/2026-10-17b - CustomerLocationsFilesNotes.sql
+related:
+  - ./record-hard-delete.md
+  - ./record-activity-timeline.md
+  - ./note-record-authorship.md
+  - ./tableview-joins.md
+  - ./model-save-parent-cascade-stored-field-deadlock.md
+  - ./contact-customer-required-internal-customer.md
+  - ./acl-permission-chain.md
+---
+Shared Client-DB data model around a Customer (locations, files, notes, contact count); open before linking anything to a customer or listing a customer's locations.
+
+## Summary
+
+Added 2026-10-17 (TRUE-82870, built for TOGa Desk, usable by any app). All tables live in every `Client_*` DB.
+
+| Piece | Shape | Core ids |
+|---|---|---|
+| `Customers.primaryLocationId` | FK → Locations, standard field | RecordFields 2799 |
+| `Customers._contactCount` | non-stored `FIELD_SQL` COUNT of Contacts by `customerId` | RecordFields 2800 |
+| `Locations_Customers` | many-to-many bridge, `UNIQUE (locationId, customerId)` | Records 382 `location-customers` |
+| `Customers_Files` | copy of `Cases_Files`, `UNIQUE (customerId, fileId)` | Records 383 `customer-files` |
+| `CustomerNotes` | copy of `CaseNotes` minus stage: write-once, internal | Records 384 `customer-notes` |
+
+RecordFields 2801-2814 cover the three new records.
+
+## How it works
+
+- **Location of a customer:** use `primaryLocationId` (a real join). `_location` (city, state from the bill-to
+  Address) is kept for its existing readers — do not build new features on it.
+- **Bridge, not `Locations.customerId`:** a location may belong to many customers (developer decision).
+- **Inherent children:** `customers → location-customers` and `locations → location-customers` (isParentTouched 0),
+  `customers → customer-files` and `customers → customer-notes` (isParentTouched 1). Child keys:
+  `locationCustomers[]`, `customerFiles[]`, `customerNotes[]`.
+- **CustomerNotes author:** `authorUserId` stamped in `save()` from `_Model::getRequestUserId()`, never from the
+  payload (nested creates skip the child's PRE POST interceptor, so it cannot live there). No client user
+  (API key, worker) → 400. Updates refused.
+- **Client ACL:** full 4-piece chain, granted to every role with a global read on customers (Base locally).
+  382/383: CRUD. 384: create + read only, only `note` writable.
+- **Delete:** see [record hard delete](./record-hard-delete.md). **Activity:** root `customers` →
+  surface `customer-activity` (see [record activity timeline](./record-activity-timeline.md)).
+- **Listing a customer's locations:** separate parent-scoped TableView `desk-customer-locations` (Locations base,
+  OUTER joins → Locations_Customers → Customers, filtered by `Customers.uuid`). See gotchas.
+
+## Gotchas
+
+- **Never OUTER-join a many-to-many bridge into a shared TableView.** blox sends every join of a view on every
+  request (`buildJoinOptions`), so the general listing repeats each row once per bridge match. Make a
+  separate parent-scoped view instead (rule lives in [tableview-joins](./tableview-joins.md)).
+- **`_contactCount` must stay non-stored** — a stored self-aggregate deadlocks the save cascade
+  ([details](./model-save-parent-cascade-stored-field-deadlock.md)).
+- **Assets link to a customer through Contacts** (`Units.contactId → Contacts.customerId`), not directly.
+
+## Change history
+- 2026-10-17 — Created: primaryLocationId, _contactCount, Locations_Customers, Customers_Files, CustomerNotes (TRUE-82870). (jcardinal)

package/knowledge/2.0/apps/_underscore/features/note-record-authorship.md

@@ -63,10 +63,11 @@ Before building anything that shows or filters by note author:
 
 - **`contactId` on a `*Notes` model is an unwritten FK — treat it as always NULL.** Seven models, zero writers.
 - **A notes list UI has no author to show.** Design for it, or the field silently renders blank for every row.
-- **Exception — `CaseNotes` (2026-10-15) has a real author:** `authorUserId` stamped in `_Model_Client_CaseNote::save()` from `_Model::getRequestUserId()`. Copy that pattern for the real fix. See [Case status + stage gate](./case-status-and-stage-gate.md).
+- **Exception — `CaseNotes` (2026-10-15) and `CustomerNotes` (2026-10-17) have a real author:** `authorUserId` stamped in `::save()` from `_Model::getRequestUserId()`. Copy that pattern for the real fix. See [Case status + stage gate](./case-status-and-stage-gate.md), [Customer related records](./customer-locations-files-notes.md).
 - **`dtStamp` is `FIELD_DATETIME_CREATED`** — stamped by the ORM on insert, the only provenance a note actually carries.
 
 ## Change history
+- 2026-10-17 — CustomerNotes added as a second server-stamped-author note model (TRUE-82870). (jcardinal)
 - 2026-10-15 — Noted CaseNotes as the first note model with a server-stamped author. (jcardinal)
 
 ## Related

package/knowledge/2.0/apps/_underscore/features/record-activity-timeline.md

@@ -32,7 +32,7 @@ client `AclRecordScripts`. Data source: [record change audit log](record-change-
 
 - **Roots** = `ROOT_ACTIVITY_SURFACE_SLUGS` (route → activity Surface slug): `tickets` →
   `ticket-activity`, `units` → `asset-activity`, `cases` → `case-activity`, `service-requests` →
-  `service-request-activity`. Any other route → 400. **A new root = one map entry + its Surface
+  `service-request-activity`, `customers` → `customer-activity`. Any other route → 400. **A new root = one map entry + its Surface
   (`dbchanges2` `Core/`).** Engine (`Source` reads Logs, `Reader` checks as the reader through api2)
   is generic; no new client ACL needed for a new root.
 - **Children:** `Logs.RecordParent`, level by level, max `Source::MAX_DEPTH` (3) levels and
@@ -45,7 +45,7 @@ client `AclRecordScripts`. Data source: [record change audit log](record-change-
      `isVisible = 0`). An UPDATE with no visible field is dropped. Secrets → `{redacted:true}`.
   4. FK values → `{uuid, label[, slug]}`, `{missing:true}`, or `{value:null}` — never a raw id.
 - **CREATE rows of `CREATE_HIDDEN_ROUTES`** (`ticket-notes`, `ticket-note-files`, `unit-notes`,
-  `case-notes`, `service-request-notes`) are dropped — the host screen merges the notes feed.
+  `case-notes`, `service-request-notes`, `customer-notes`) are dropped — the host screen merges the notes feed.
   Note edits/deletes still show.
 - **Paging:** cursor = `Logs.Record` id; `nextCursor` null at the end. Scan bounded
   (`MAX_SCAN_BATCHES` × `SCAN_BATCH_SIZE`); a page cut by the bound still returns a `nextCursor`.
@@ -69,5 +69,6 @@ client `AclRecordScripts`. Data source: [record change audit log](record-change-
   (schema + api2 change) — not built.
 
 ## Change history
+- 2026-10-17 — Added root `customers` + `customer-notes` to `CREATE_HIDDEN_ROUTES` (TRUE-82870). (jcardinal)
 - 2026-10-17 — One-FK rule for parent links; no request id for grouping (TRUE-82889). (jcardinal)
 - 2026-10-15 — Added roots `units`, `cases`, `service-requests` + their note routes to `CREATE_HIDDEN_ROUTES` (TRUE-82836). (jcardinal)

package/knowledge/2.0/apps/_underscore/features/record-hard-delete.md

@@ -0,0 +1,60 @@
+---
+title: Record hard delete (_Component_RecordDelete + PRE DELETE interceptor)
+framework: "2.0"
+repo: _underscore
+project: _Underscore
+client: shared
+type: feature
+status: active
+updated: 2026-10-17
+owners: [jcardinal]
+files:
+  - _underscore/Component/RecordDelete/RecordDelete.php
+  - _underscore/Model/Client/Customer.php
+  - _underscore/Model/Client/Ticket.php
+  - _underscore/Model/Client/Case.php
+  - _underscore/Model/Client/ServiceRequest.php
+related:
+  - ../../api2/features/api-payload-interceptors.md
+  - ./customer-locations-files-notes.md
+  - ./record-activity-timeline.md
+---
+Map-driven hard delete of everything hanging off one record (block / detach / delete children / orphan Files); open before making a record deletable or adding a table with a Files FK.
+
+## Summary
+
+`DELETE /v2/<route>/{uuid}` on an opted-in record runs a PRE DELETE interceptor that calls
+`_Component_RecordDelete::purge(['model' => static::class, 'id' => $id])`. `purge()` cleans the related
+rows from a map the model declares in `relatedRows()`; api2 then deletes the record row itself. Used by
+Tickets, Cases, ServiceRequests, Customers. The class DocBlock is the full contract — read it before editing.
+
+## How it works
+
+- **Opt in (3 steps):** `public static function relatedRows(): array` on the model; `preDelete(&$api, &$payload)`
+  that calls `purge()` for a route-uuid delete; a `Core.ApiPayloadInterceptors` row (recordId, `PRE`, `DELETE`).
+  Cleanup must be PRE — a POST DELETE interceptor never runs (see api-payload-interceptors).
+- **Map keys** (all optional): `blockers` (any match → 400 `_Exception_Validation`, nothing deleted), `detach`
+  (`UPDATE … SET col = NULL`, column must be nullable), `files` (collect file ids first), `polymorphic` (run
+  before children), `children` (ordered set-based DELETEs; grandchildren first). Entries: `{table, column, via?, where?}`.
+- **Run order:** lock record row → blockers → collect file ids → detach → polymorphic → children → orphan Files.
+- **Files:** a `Files` row is deleted only if no table in `FILE_REFERENCE_TABLES` still points at it. Storage
+  objects (S3) are never touched.
+- **Transaction:** first statement is a no-op UPDATE on the record row — it opens api2's request transaction and
+  takes the lock; any failure rolls the whole request back. All statements on the write connection, one DB.
+- **Customer rule (Records 113, 2026-10-17):** block on Contacts / SalesOrders / PurchaseOrders; detach Tickets /
+  ServiceRequests / Cases `customerId`; delete Customers_Catalogs, Customers_Subscriptions, Locations_Customers,
+  Customers_Files, CustomerNotes rows; orphan Files from Customers_Files.
+
+## Gotchas
+
+- **New table with a `fileId` FK → add it to `FILE_REFERENCE_TABLES`.** Missing it makes the Files DELETE fail on
+  the FK and roll back every delete that touches a shared file (loud, not silent).
+- **Client override of `relatedRows()` must merge `parent::relatedRows()` key by key;** a client `preDelete`
+  replaces the shared one and must call `parent::preDelete()`.
+- **Use `$api->recordUuid ?? null`, never `isset($api->recordUuid)`** — `_Component` has `__get` but no `__isset`.
+- **Load the record on the write connection** (read host off) — the read replica can lag this request's writes.
+- **`detach` is for business records that outlive the parent** (e.g. Tickets.customerId); use `blockers` when
+  losing the link would lose meaning (orders, required FKs like `Contacts.customerId`).
+
+## Change history
+- 2026-10-17 — Created; Customers opted in, Customers_Files added to FILE_REFERENCE_TABLES (TRUE-82870). (jcardinal)

package/knowledge/2.0/apps/_underscore/features/tableview-joins.md

@@ -6,7 +6,7 @@ project: _Underscore
 client: shared
 type: feature
 status: active
-updated: 2026-09-16
+updated: 2026-10-17
 owners: [bala, apeterson, jcardinal]
 files:
   - _underscore/Model/Client/TableView.php
@@ -31,6 +31,7 @@ related:
   - ./acl-permission-chain.md
   - ../../toga25-supply/features/transfer-orders-page.md
   - ../../toga25-supply/features/record-modals-and-nested-tables.md
+  - ./customer-locations-files-notes.md
 ---
 
 How `TableViewJoins` rows become a view's join SQL — aliasing, chained multi-hop joins, ACL gating, and the three ways a view breaks; open before adding/rebasing a join or debugging a view 500 / empty grid.
@@ -188,6 +189,15 @@ Cause: an **INNER** `TableViewJoins` on a foreign-key column that is **unpopulat
 - **Fix / avoid:** for an **optional / possibly-empty** FK, use **LEFT OUTER** (rows survive with nulls in the joined columns) or omit the column entirely. Only use INNER when the FK is guaranteed populated for the tenant.
 - **Check before you add:** verify FK population in the target tenant (`SELECT COUNT(*) ... WHERE <fk> IS NOT NULL`) before choosing INNER. NYCHH's `purchase-orders` ultimately **dropped** the Location (and Ship To) column rather than switch to OUTER.
 
+### A many-to-many join in a SHARED view duplicates rows in every listing that uses it
+
+blox sends **every** join of a view on **every** request (`buildJoinOptions`), filtered or not. So an OUTER join to a
+many-to-many bridge added "only for the parent-scoped tab" also runs in the plain listing, and each row repeats once
+per bridge match. Fix: a **separate parent-scoped TableView** that carries the bridge joins; leave the general view
+alone. Example (2026-10-17): `desk-customer-locations` (Locations → Locations_Customers → Customers, read only with
+`Customers.uuid = <customer>`) beside the unchanged `desk-locations` (`dbchanges2/Client/2026-10-17b`). A 1:0..1 join
+(single FK each hop) is safe to add to a shared view.
+
 ### Context RecordFieldSettings are OPTIONAL for a joined column to render
 
 `meta()` looks up `contextRecordFieldId`-scoped settings (`DefaultRecordFieldSettings` plus the Client / Persona / User / Language `RecordFieldSettings` tables) only to decide **which settings row supplies the column label**. When no context row exists for `(recordFieldId, contextRecordFieldId)`, it nulls `contextTable` / `contextField` and falls back to the field's own settings. A new joined column therefore does **not** require adding `RecordFieldSettings` rows just to appear — those rows are only needed to control the **header text** (see [page-meta-context-field-settings](./page-meta-context-field-settings.md), which is also where the "header renders as a camelCase slug" fallback is explained).
@@ -214,6 +224,10 @@ Core-level reference ids used (identical across all clients and environments): *
 - **An unused join can already exist.** Confirm before inserting; a duplicate join of the same table is what breaks chained joins.
 - **An INNER join to an EMPTY FK empties the whole grid with NO error.** Third failure mode: an inner join on an FK that is unpopulated for the tenant drops every row (meta looks fine, data returns 0). Use LEFT OUTER for an optional FK, or verify FK population before choosing INNER.
 - **`PurchaseOrderItems` has no `itemId` — it reaches the catalog via `vendorItemId → VendorItems → Items`.** Converting a sales-order-item view (which joins Items directly) to purchase-order-items needs an extra **VendorItems** hop inserted before Items, with the Items join repointed to `VendorItems.itemId`. Don't just recolumn.
+- **Never add a many-to-many (bridge) OUTER join to a shared view** — every listing on that view gets duplicate rows. Use a separate parent-scoped view.
+
+## Change history
+- 2026-10-17 — Many-to-many join in a shared view duplicates rows; use a parent-scoped view (TRUE-82870). (jcardinal)
 
 ## Related
 

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/knowledge/INDEX.md

@@ -21,7 +21,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 
 ## 2.0 framework
 
-- **_underscore** (_Underscore) _(framework core)_ — 101 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
+- **_underscore** (_Underscore) _(framework core)_ — 103 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
 - **worker2** (Worker) — 90 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 26 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 22 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.1063",
+  "version": "1.0.1065",
   "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>`.