fsanyoto commited on
Commit
fedd33c
Β·
verified Β·
1 Parent(s): 4872c31

Deploy AIOS web (React glide grid + FastAPI slice)

Browse files
RELEASES.json CHANGED
@@ -1,6 +1,12 @@
1
  {
2
- "current": "9f6cfed",
3
  "releases": [
 
 
 
 
 
 
4
  {
5
  "version": "v64",
6
  "sha": "bb8985c",
 
1
  {
2
+ "current": "73c94f0",
3
  "releases": [
4
+ {
5
+ "version": "v65",
6
+ "sha": "9f6cfed",
7
+ "date": "2026-08-31",
8
+ "subject": "release v65"
9
+ },
10
  {
11
  "version": "v64",
12
  "sha": "bb8985c",
VERSION CHANGED
@@ -1 +1 @@
1
- 9f6cfed
 
1
+ 73c94f0
web/src/customer-grid/CustomerGrid.tsx CHANGED
@@ -8109,20 +8109,22 @@ function CustomerGridSurface({
8109
  // `formula` alone (D-114's deliberate narrowness β€” every other kind holds real values). Booked
8110
  // as pending work rather than fixed by handing a type-blind delete to a panel.
8111
  /**
8112
- * ⭐ OWNER, 2026-08-23 β€” A ROUTE COLUMN IS DELETABLE FROM **HERE** TOO, not only from the
8113
- * column menu. Owner: *"I can't even delete the Field route now?"* The column menu has carried
8114
- * the route branch since owner item 3, but a route order carries no `custom` flag (see
8115
- * `route_order_write`'s definition), so this set never held one and the Hide-fields panel β€”
8116
- * the surface a person opens when a column is missing β€” showed no delete affordance at all.
8117
- * ⚠ MATCHED ON THE DECLARED `kind`, never on the `route_` prefix, exactly as the column menu's
8118
- * branch and the server door both are.
 
 
8119
  */
8120
  const deletableKeys = new Set(
8121
  fields
8122
  .filter(
8123
  (f) =>
8124
  !((f as Field & { deletionLocked?: boolean }).deletionLocked) &&
8125
- (f.custom || (f.shared && f.kind === "route_order")) && f.key !== lockedKey
8126
  )
8127
  .map((f) => f.key)
8128
  );
 
8109
  // `formula` alone (D-114's deliberate narrowness β€” every other kind holds real values). Booked
8110
  // as pending work rather than fixed by handing a type-blind delete to a panel.
8111
  /**
8112
+ * ⭐ The second arm here was `(f.shared && f.kind === "route_order")`, added 2026-08-23 for the
8113
+ * owner's *"I can't even delete the Field route now?"*: a legacy route column carried no `custom`
8114
+ * flag, so this set never held one and the Hide-fields panel offered no delete for it. The legacy
8115
+ * column-per-route scheme is retired and no field the client is served carries that kind any more
8116
+ * β€” the only `route_order` definitions left are the invisible share bridges of normalized Routes,
8117
+ * which the server never serves as columns β€” so the arm could only ever be false.
8118
+ * ⚠ D-542 IS NOT CLOSED BY THIS. Its defect is the OTHER arm: a SHARED custom field still lands
8119
+ * in this set and its trash routes to `deleteField`, whose `!f?.custom` guard passes, emitting a
8120
+ * per-user `field_delete` against a shared definition. That is still live.
8121
  */
8122
  const deletableKeys = new Set(
8123
  fields
8124
  .filter(
8125
  (f) =>
8126
  !((f as Field & { deletionLocked?: boolean }).deletionLocked) &&
8127
+ f.custom && f.key !== lockedKey
8128
  )
8129
  .map((f) => f.key)
8130
  );