Completes t2db.8's remaining UI half. Mirrors ui/src/mappings/ exactly: bindings.jsx (list + editor), binding-editor.jsx (pure StatusPill/ BindingRow), bindings.css, wired into main.jsx's route table with a new icon. API helpers (bindingCreate/Update/Delete/Approve) added to api.jsx following the existing mapping* pattern. CRITICAL FIX, found via real browser verification (AGENTS.md's UI rule), not by inspection: every JSX-based page in this app -- dashboard, tasks, logs, captures, mappings, skills, workflows, memory, curators, channels, settings, and now bindings -- silently rendered the literal text "[object Object]" instead of its content. Root cause: main.jsx's router passed each page's Preact VNode into dom.jsx's mount()/append(), which only knows how to append real DOM Nodes or stringify everything else -- so a VNode object became exactly that string. Confirmed this predates tonight's work entirely: extracted and served the already-committed ui/dist bundle in isolation and reproduced the identical failure on the stock dashboard, unrelated to any change here. Fix: main.jsx's show() now detects a Preact VNode vs. a real DOM Node (the unused `soon: true`/comingSoon() fallback) and calls Preact's own render() for the former, leaving the generic mount() helper and its other four vanilla-DOM call sites untouched. Verified every single page renders correctly post-fix via a throwaway, fully-isolated webui.Server harness (temp SQLite, no real config/forge/network calls) driven by Playwright -- not assumed from the source diff alone. Also found and fixed a second real bug the same way: editing a binding without retyping its secret (the intended "leave blank to keep the current one" UX, matching UpdateBinding's own documented COALESCE contract) was rejected with 400, because the API handler validated edits with the create-time Validate(), which unconditionally required a full-length secret. Root-cause fix: split Binding.Validate() (create, unchanged) from a new ValidateForUpdate() (skips the length floor only when the secret is empty -- preserving the existing one -- still enforces it on a genuinely-supplied new secret). Full state machine (draft -> edit -> pending_approval -> approve -> armed -> delete) verified end-to-end in the browser afterward. Filed archie-core-mlro separately for the Pill component's pre-existing duplication across 11 files -- not fixed here, out of scope for this ticket, following this session's established discipline.
33 lines
700 B
CSS
33 lines
700 B
CSS
/* Playbook binding editor: tie a matcher, a field mapping, and a
|
|
workflow together, gated by an explicit approval state machine. */
|
|
|
|
.binding-form {
|
|
margin-bottom: var(--sp-4);
|
|
padding: var(--sp-4);
|
|
}
|
|
|
|
.binding-form-row {
|
|
display: flex;
|
|
flex-direction: column;
|
|
gap: var(--sp-1);
|
|
margin-bottom: var(--sp-3);
|
|
font-size: var(--text-sm);
|
|
color: var(--fg-subtle);
|
|
}
|
|
|
|
.binding-input,
|
|
.binding-select {
|
|
padding: var(--sp-2);
|
|
border: 1px solid var(--border-strong);
|
|
border-radius: var(--radius-sm);
|
|
background: var(--bg-raised);
|
|
color: var(--fg);
|
|
font: inherit;
|
|
}
|
|
|
|
.binding-error {
|
|
color: var(--danger, #e5484d);
|
|
font-size: var(--text-sm);
|
|
margin-bottom: var(--sp-3);
|
|
}
|