loopable / web /wiring_rows /wave43_shell_repair.py
fsanyoto's picture
Deploy AIOS web (React glide grid + FastAPI slice)
e85dc2a verified
Raw History Blame Contribute Delete
1.62 kB
"""Wave 43 continuation shell-repair — DatePicker consumer wiring.
The DatePicker implementation and CustomerGrid mount are owned by the grid lane. This module
records their completed cross-fence contract in the shared WIRINGS map, so the coverage ratchet
cannot mistake a mounted calendar for an unowned component again.
"""
from __future__ import annotations
ROWS: list[tuple[str, str, str, str, str]] = [
("W43C-T02 DatePicker is DECLARED and MOUNTED by the grid",
"customer-grid/DatePicker.tsx", r"export function DatePicker\(",
"customer-grid/CustomerGrid.tsx", r"<DatePicker"),
("W43C-T02 a picked date writes through the grid's ordinary record patch door",
"customer-grid/DatePicker.tsx", r"onChange: \(value: string\) => void;",
"customer-grid/CustomerGrid.tsx",
r'onChange=\{\(value\) => patchAndRecord\(datePicker\.pid, \{ \[dateField\.key\]: value \}, "a date"\)\}'),
# RE-AIMED 2026-08-31. The owner reversed wave 47's R1/R2 - *"Each ROW stores its own repeat
# rule"* - so the picker no longer persists the FIELD definition and `onRecurrence` is gone
# with the write it fed. The cross-fence fact this row exists to prove survives the reversal
# intact and is simply restated for the new contract: the picker cannot edit a repeat without
# being told WHICH RECORD, and the host is what tells it.
("W43C-T02 the repeat editor is per RECORD, so the host must name the record",
"customer-grid/DatePicker.tsx", r'pid: number;',
"customer-grid/CustomerGrid.tsx", r'pid=\{datePicker\.pid\}'),
]
DELETIONS: list[tuple[str, str, str, str]] = []