Deploy AIOS web (React glide grid + FastAPI slice)
Browse files- RELEASES.json +1 -1
- VERSION +1 -1
- api/automation_engine.py +30 -9
- web/src/customer-grid/clipboard.ts +10 -1
RELEASES.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
| 1 |
{
|
| 2 |
-
"current": "
|
| 3 |
"releases": [
|
| 4 |
{
|
| 5 |
"version": "v13",
|
|
|
|
| 1 |
{
|
| 2 |
+
"current": "6c60d24",
|
| 3 |
"releases": [
|
| 4 |
{
|
| 5 |
"version": "v13",
|
VERSION
CHANGED
|
@@ -1 +1 @@
|
|
| 1 |
-
|
|
|
|
| 1 |
+
6c60d24
|
api/automation_engine.py
CHANGED
|
@@ -5382,21 +5382,42 @@ def stages_for(defn):
|
|
| 5382 |
routes.append({"from": rid, "to": oid, "label": nxt, "condition": None})
|
| 5383 |
if acfg.get("next"):
|
| 5384 |
col += 1
|
| 5385 |
-
#
|
| 5386 |
-
#
|
| 5387 |
-
|
| 5388 |
-
|
| 5389 |
-
|
| 5390 |
-
|
| 5391 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 5392 |
return stages, routes
|
| 5393 |
|
| 5394 |
|
| 5395 |
def terminal_stage_ids(stages, routes):
|
| 5396 |
"""Stages a record can REST at with nowhere further to go β the ends C5's `ending` acts on.
|
| 5397 |
Derived from the routes rather than declared, so a flow cannot gain an exit without this
|
| 5398 |
-
noticing (and a lane that stops being terminal stops being reset).
|
| 5399 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 5400 |
onward = {r["from"] for r in routes if r["to"] in assignable and r["to"] != r["from"]}
|
| 5401 |
return [sid for sid in assignable if sid not in onward]
|
| 5402 |
|
|
|
|
| 5382 |
routes.append({"from": rid, "to": oid, "label": nxt, "condition": None})
|
| 5383 |
if acfg.get("next"):
|
| 5384 |
col += 1
|
| 5385 |
+
# β NO AUTO-CHAINING ROUTES BETWEEN CONSECUTIVE STEPS, and the first version of this block had
|
| 5386 |
+
# them. Two things went wrong and both were invisible on nurilab's own automation (its flow has
|
| 5387 |
+
# only the pinned step, so no action stage exists to chain):
|
| 5388 |
+
#
|
| 5389 |
+
# 1. A ROUTE IS AN OFFER THE WRITE DOOR REFUSES. `_card_next` turns outgoing routes into the
|
| 5390 |
+
# board's "move this card on" buttons, but `ensure_stage_field` builds `humanMoves` from
|
| 5391 |
+
# REVIEW stages only β so every chained button would have been refused by `grid_events`.
|
| 5392 |
+
# A control that is drawn and cannot work is worse than one that is absent.
|
| 5393 |
+
# 2. IT MADE THE ASYMMETRY WORSE, not better: zipping a flat stage list pairs ADJACENT
|
| 5394 |
+
# entries, so of a review's two exits only the SECOND got an onward route and the first
|
| 5395 |
+
# silently became terminal. Two exits of one gate with different endings is not a thing
|
| 5396 |
+
# anybody chose.
|
| 5397 |
+
#
|
| 5398 |
+
# The path still reads left-to-right: `col` is assigned in flow order above, and the board
|
| 5399 |
+
# lays columns out by `col`. Order is what makes it a path; a drawn arrow was never the point.
|
| 5400 |
return stages, routes
|
| 5401 |
|
| 5402 |
|
| 5403 |
def terminal_stage_ids(stages, routes):
|
| 5404 |
"""Stages a record can REST at with nowhere further to go β the ends C5's `ending` acts on.
|
| 5405 |
Derived from the routes rather than declared, so a flow cannot gain an exit without this
|
| 5406 |
+
noticing (and a lane that stops being terminal stops being reset).
|
| 5407 |
+
|
| 5408 |
+
β AN ORDINARY STEP IS PASSED THROUGH, NEVER RESTED AT (2026-08-06, owner item 1). Making every
|
| 5409 |
+
action a board stage put a card at the LAST step of a completed run β and every one of those
|
| 5410 |
+
stages has no outgoing route, so `auto_reset` read "reached the end" and cleared the stamp
|
| 5411 |
+
while incrementing the cycle counter. MEASURED before this line existed: three runs of a
|
| 5412 |
+
two-action `auto_reset` flow left `stage=''` and `cycles` at 1, 2, 3 β a card that never rests
|
| 5413 |
+
anywhere and a counter climbing forever, silently, on every scheduled run.
|
| 5414 |
+
"Terminal" means *the flow is done with this record until somebody moves it*; a step the run
|
| 5415 |
+
walked straight through is the opposite of that. Only stages a card genuinely WAITS at β review
|
| 5416 |
+
gates, their declared exits, and lanes β can end a flow. Nurilab's own automation could not
|
| 5417 |
+
have shown this: its flow has only the pinned step, so it has no action stage at all.
|
| 5418 |
+
"""
|
| 5419 |
+
assignable = {s["id"] for s in stages
|
| 5420 |
+
if s.get("assignable") and s.get("panel") != "flow_action"}
|
| 5421 |
onward = {r["from"] for r in routes if r["to"] in assignable and r["to"] != r["from"]}
|
| 5422 |
return [sid for sid in assignable if sid not in onward]
|
| 5423 |
|
web/src/customer-grid/clipboard.ts
CHANGED
|
@@ -1,4 +1,4 @@
|
|
| 1 |
-
import { choiceOptions, ratingMax } from "./types";
|
| 2 |
import type { Field } from "./types";
|
| 3 |
|
| 4 |
function choiceMatch(raw: string, allowed: string[]): string | undefined {
|
|
@@ -23,6 +23,15 @@ export function coerceClipboardValue(
|
|
| 23 |
raw: string,
|
| 24 |
allowedChoices: string[] = choiceOptions(field)
|
| 25 |
): string | undefined {
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 26 |
const value = raw.replace(/\r/g, "");
|
| 27 |
const trimmed = value.trim();
|
| 28 |
switch (field.type) {
|
|
|
|
| 1 |
+
import { choiceOptions, isMachineWritten, ratingMax } from "./types";
|
| 2 |
import type { Field } from "./types";
|
| 3 |
|
| 4 |
function choiceMatch(raw: string, allowed: string[]): string | undefined {
|
|
|
|
| 23 |
raw: string,
|
| 24 |
allowedChoices: string[] = choiceOptions(field)
|
| 25 |
): string | undefined {
|
| 26 |
+
// β OWNER ITEM 4 (2026-08-06) β THE PASTE DOOR, which the type switch below structurally
|
| 27 |
+
// cannot cover. This module's own design note is that a paste never opens an editor, so a cell
|
| 28 |
+
// that is read-only by NATURE and absent from the switch is uneditable by keyboard and
|
| 29 |
+
// overwritable by Ctrl+V. Every case below is a TYPE; `isMachineWritten` is not type-based β an
|
| 30 |
+
// automation-filled column is an ordinary `text` field wearing a tag β so the Instagram preset
|
| 31 |
+
// columns fell straight through it. `grid_events` refuses the write either way, but a
|
| 32 |
+
// multi-cell paste would paint optimistically across them and then bounce, which reads to the
|
| 33 |
+
// person doing it as the app losing their data rather than as a wall.
|
| 34 |
+
if (isMachineWritten(field)) return undefined;
|
| 35 |
const value = raw.replace(/\r/g, "");
|
| 36 |
const trimmed = value.trim();
|
| 37 |
switch (field.type) {
|