Livingui redesign - #399
Merged
Merged
Conversation
…kit platform - New standalone living-ui-v2/ workspace: versioned React kit (realtime PB hooks, theme packs, console relay), project blueprint, and `lui` CLI (create/validate/dev/kit-sync/pb/ops/run/data/verify/probe) - Validation gate: types, build, migrations-on-fresh-db, ops manifest, ownership hashes — with source-annotated errors and a same-error breaker - walk_verify sub-agent: drives the running app in a real browser (playwright MCP) and blocks launch on observed defects (PR #388 contract) - Manager/actions rewritten for single-process PB apps; V1 template, importer, and sidecar removed; ZIP import is deterministic code - Creation wizard (layout/theme/reference files), option-chip QnA, session handoff, spec suite under living-ui-v2/spec/
…aftbot into livingui-redesign
…aftbot into livingui-redesign
… error formatting and cataloguing. Add immediate aborting of AUTH/CREDIT/QUOTA/MODEL/BLOCKED/BAD_REQUEST errors instead of silent retries.
An agent asked to "add a todo for tomorrow" wrote due_date: "tomorrow". PocketBase returned 200, stored an empty string, and the agent told the user it was scheduled. It had to guess what the app contained, the write silently failed, and nothing stopped it claiming otherwise. All three are now handled in the app, so any agent benefits — verified by driving an app with curl alone, after deleting .superuser. In the app (new pb_hooks, adapter 1.6.0): - describe: entities, protocol types, conventions, from the live schema - identity: PocketBase answers 200 for unknown paths, so an "a2app" marker is the only reliable probe - write guard as router middleware, not a record hook — PocketBase coerces first, after which "tomorrow" and "" are indistinguishable - read-back backstop; errors carry a code and list every violation - origin guard, agent token, ops auth, rate limits, idempotency In the CLI: - reads describe, not PocketBase's superuser-only admin endpoint, so it holds no privilege an outside agent lacks - resolves dates and labels client-side, where a clock and Intl exist - adapter-sync ships hooks without re-vendoring the kit - a valueless --flag now errors instead of becoming `true` - gate rejects e.app inside runInTransaction, which deadlocks the process while /api/health still returns 200 In CraftBot: - the system reports what changed, from the stored record; a false claim is withheld and handed back rather than corrected in front of the user - the data model is inlined into the prompt — three attempts became one - skills load per run, so operating an app no longer carries the build recipe that rebuilt a live app after one row insert - integration bridge: capability gate, destination allowlist, no redirects adapter-sync runs at create, install, import and launch — launch is the only path reaching an app a user already had. Adds spec/OVERVIEW.md and scripts/a2app-selfcheck.sh (21 checks).
…tant + Fix Chat persistency
…ge gen, video gen, factory + plan migration to actions, browser_adapter, CLI commands
Weak models write code well but manage themselves badly: 26 logged builds, and every failure was self-management — churning on one dead end, fabricating causes where evidence was blank, shrinking "email me" into "logs it", announcing success after failed verification, or quitting unnoticed. The model keeps the hands; this takes away the clipboard. - app/factory: stdlib-pure Machine (persisted arc, 3×/12 retry caps, escalation, redispatch-on-surrender, honest stuck reports), defect cards (cause = quoted evidence or "unknown" — theories unrepresentable), build graph as a pure transition (only a parsed PASS reaches done), distiller, cookbooks (one generic callAction pattern + dry-run param discovery, email as the proven worked example), CraftBot host adapter; layering lint + 3 test suites incl. replays of two real incidents. - Fix missions are fresh runs carrying cards; ready/stuck messages are machine-composed — agent-authored status is retired. - Evidence everywhere the platform was silent: gate stderr, response bodies, refused-request URLs, boot-log excerpts, handler exceptions, migrate-hang kills, pre-boot migration-rename check, CLI error.cause unwrapping. - Integrations: bridge action endpoint runs CraftBot's own implementations (send_gmail, semantic params), grants derived from code by the gate, irreversible-confirm + dry-run; omitted `to` = account owner — apps never hold identity. Wizard offers marketplace matches; capability map injected. - Verifier: full spec coverage required, value plausibility, fail-closed verdict parsing.
… into livingui-third-party-fix
Add the Factory — supervision for weak-model app builds
First Error Message Expansion Catalogue: Provider Interfaces
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.