@ai-matrx/records-ui 0.63.0 → 0.66.0

package/CHANGELOG.md

@@ -1,5 +1,119 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.66.0
+
+**A screen stops talking to a developer.** (lane TAILS-6.)
+
+Two sightings on ONE table's rail, watched from the admin seat by the GUIDE lane on 2026-09-21:
+
+> Checklists — "Something went wrong at our end" ·
+> `@ai-matrx/records did not recognise SQLSTATE from checklistTemplates`
+>
+> Dashboards — "… bind `openRecords` on `<RecordsUiProvider>` …"
+
+Both are the same defect in two coats: a sentence written for whoever maintains the code,
+printed to the person who owns the business.
+
+* **`refusalForAPerson` no longer promotes an engineer's hint to the person's remedy.** It
+  prefers the door's own hint over its table, which is right — but it assumed every hint came
+  from the store, and the machine-identity filter only catches a five-character SQLSTATE.
+  New `isEngineerText` / `ENGINEER_TEXT` judge a sentence by SHAPE — a package name, the word
+  SQLSTATE, a `<Component>`, a camelCase identifier, a backticked token, "bind X on …" — and
+  send it to `forEngineers` wherever it came from. `error.diagnostic` from
+  `@ai-matrx/records` 0.47.0 joins the same line.
+* **Titles and remedies for `unreachable`, `needs_approval`, `stale_read` and `timed_out`,**
+  which had none and fell through to "Something went wrong at our end". A call that never
+  reached the store now says so and says nothing was changed.
+* **Every unbound-port sentence rewritten for the person it is shown to** — the nine of them,
+  not the two that were caught: `NO_OPEN_RECORDS_REASON`, `NO_REASK_REASON`,
+  `NO_SAVED_VIEWS_REASON`, `NO_MEMBERS_REASON`, `NO_SHARE_REASON`, `NO_UPLOAD_REASON`,
+  `NO_CHAT_REASON`, `NO_ENRICH_REASON`, `IN_MEMORY_QUEUE_REASON`. Each still says what is
+  missing and now says what to do instead; the instruction for whoever maintains the app moved
+  into the TSDoc above it, where it always belonged.
+* **`TablePage` gains `activeGroupField` and `cameFrom`,** so a host CAN bind `openRecords`.
+  The store has no door that returns the rows behind an aggregate filter, so a click cannot
+  promise a narrowed list — what it can do is open this table's board with its columns set to
+  the field the chart grouped by, and `cameFromLine` says plainly that this is every record
+  grouped that way rather than only the ones the number counted.
+* **Guard:** `src/no-developer-sentences.test.tsx` — shown failing on the pre-fix bytes with
+  the exact sentence the GUIDE lane read, then passing. It needs no server.
+
+**Consumer action:** bind `openRecords` on your `RecordsUiProvider` and pass `activeGroupField`
+/ `cameFrom` through from the address, or leave it unbound and the canvas says so in plain
+English. `matrx-frontend`'s `/data-v2/[tableId]` route is the worked example.
+
+## 0.65.0
+
+**A condition about a relation column stops asking a person to type a uuid.**
+(lane RELATION-DISPLAY-2.)
+
+* **`ConditionField` carried no type, so the ONE condition builder could not know a
+  column points at another record.** It drew the same plain text box every other
+  clause gets — and a relation's stored value is the other record's id (FLD-6 /
+  REL-1), so the only way to write a true clause was to find and TYPE a uuid. The
+  dispatcher's actual house rule, *"a job for Harborview Property Group cannot
+  leave Scheduled without a purchase order"*, was unwritable by exactly the person
+  the builder exists for. A box that accepts anything and can only produce a rule
+  matching nothing is law 4's dead control.
+* `ConditionField` now carries an OPTIONAL `field`. When it is a relation, the value
+  control is **`RelationPicker`** — the same picker the cell uses, on the same
+  `relation_words_many` the cell reads — so a filter offers the column's own joined
+  words ("Harborview Property Group, Carpinteria") and writes the ID. A filter and
+  the column it filters can no longer disagree about what a record is called.
+* It is asked for ONE record even when the column holds several: a clause compares
+  against one value, and a picker that let somebody choose three would write an
+  expression this row cannot draw back.
+* Both callers in this package already held the whole `Field` and were throwing it
+  away one line before handing it over — `StageRules` and `FormBuilder`. In the form
+  builder this is the OWNER's screen; a stranger is still never asked a relation
+  question (`publicQuestions.ts` is untouched).
+
+**Consumer action:** none — `field` is optional and a caller passing only
+`{id, key, label}` gets exactly the old behaviour, which has its own clause. A host
+that wants the picker passes the `Field` it already has.
+
+*Numbered 0.65.0, not 0.64.0: a peer lane claimed 0.64.0 for the coercion primitive
+while this work was in flight and tagged it first. Two lanes bumping one package in
+one afternoon is the cost of a shared checkout; the fix is to move, never to take a
+version somebody else's tag already names.*
+
+## 0.64.0
+
+> 🚨 **0.64.0 NEVER PUBLISHED, AND EVERYTHING IN IT SHIPPED INSIDE 0.65.0.** Its publish run
+> (35638062219) was **cancelled — not failed** — because `npm/records/*` and `npm/records-ui/*`
+> share ONE concurrency slot that keeps only the newest pending run, and `npm/records-ui/v0.65.0`
+> displaced it. Nothing was lost: 0.65.0 is built from `origin/main`, which contains this
+> commit, and the tarball carries `fieldKindFor`, `coerceTypedAnswer`, `valueFromPastedText`
+> and `enumLabels` — verified by `npm pack`, not by version number. `npm view` goes
+> 0.63.0 → 0.65.0 with no 0.64.0 in between. The entry is kept as written so the work is
+> still findable by what it did. *(Recorded by lane RELATION-DISPLAY-2, whose tag did the
+> displacing.)*
+
+**The paste and the editor stop owning their own opinion of a column, and the capture sheet
+stops minting NaN.**
+
+- **`editorKindFor` is `fieldKindFor`** (`@ai-matrx/records` 0.45.0) with this package's
+  kernel File/Person ids bound. The classifier body lived here and was the only one.
+- **`valueFromPastedText` is one call to `coerceTypedAnswer`**, keeping this package's label
+  so a refusal names the column the way the grid's header does. Its 150-line body WAS the
+  coercion — and while it sat here, the public booking page was unbookable over any table
+  with a number field.
+- **`ChoiceOptions`** is re-exported from the core instead of declared twice.
+- **`CaptureRun`** used `Number(raw)`, which answers NaN for "about twelve" — and a NaN
+  becomes null on the wire, so a reading taken in a yard could silently record nothing. It
+  coerces through the one body now and KEEPS the typed text when the value is refused.
+- **`ViewSwitcher`**'s calendar offer tested `kind === "datetime" || kind === "date"`. FLD-11
+  has no "date" kind; it compiled only because the old `EditorKind` union carried two words
+  nothing produced.
+- **`BuildOrAsk`** (landed 0.63.x→here): "Ask an agent" is ABSENT when `mayBuild` is false —
+  asking an agent is the same act as building by hand, through the same doors.
+- **One label map per enum** (`enumLabels.ts`): no panel keeps its own copy, and the
+  "Done"/"Finished" split between `ChecklistRunner` and `ActionInbox` is gone.
+
+*Consumer action:* none. `EditorKind` is now an alias of `FieldKind`; a host that compared a
+kind against `"date"` or `"boolean"` was comparing against a value the classifier never
+returned.
+
 ## 0.63.0
 
 **A relation cell finally SHOWS what its column was configured to show, and the