Clearer contracts, faster feedback

Thursday combined practical engineering changes with decisions about product boundaries. Scout gained deployed persistence safeguards and a faster client-test command; DOM Studio gained a desktop workspace layout. The db3 homepage and Neon review clarified what each product should own, with their implementation limits kept explicit.

• GrowthScout · preserve outcomes when bookkeeping fails. Deployed changes make AI reservation release idempotent, retry recognised SQL lock failures within a bound and preserve provider outcomes. A local captured-page crawl also reproduced a separate foreign-key snapshot conflict; adjusted transaction isolation retains the website lock and atomic writes. The release passed 186 affected Scout tests, package checks and live dashboard verification. The historical deadlock participant remained unknown. An old health scan was still draining at the recorded check, so promotion was live without complete worker retirement.
• GrowthScout · faster independent client tests. A new client-test command runs component and utility tests on two isolated workers while database-backed tests remain serial. The same 260 tests across 29 files completed in 16.5 seconds instead of 33.4 seconds, with assertions unchanged. The combined client command, including types and conventions, passed in 44.6 seconds. These are local measured runs, not a guarantee for every machine or the full database suite.
• DOM Studio · a reusable desktop workspace. DomDesktopLayout adds pinned app icons, hover/focus submenus, left or right navigation, independent scrolling, mobile navigation and a full-workspace focus mode. Assistant, pages, code and calendar demos exercise pinning and reordering; an isolated Electron demo runs the same UI in a native window. Build, types, package output, browser interactions and Electron launch were checked locally. A final resize refinement keeps one visible 1px divider with an invisible 6px drag target. Installation and AI replies remain demo behaviour; the work was not published.
• db3.ai · separate the company story from the framework. A local company homepage introduces Cloud, Studio, product sections and a human-led Concierge offering, while the framework landing page moves to /framework. Seventy-five tests, the production build, runtime checks and desktop/mobile theme checks passed. The page was not deployed, and the descriptions do not establish that planned Cloud and Test Engineer capabilities are available services. Concierge pricing remained open.
• GrowthScout · prepare proof without inventing testimonials. The local homepage gained a responsive social-proof section below its hero and a reusable quote template. Sample quotes are explicitly labelled as awaiting approval, with relationship disclosures; approved wording and named speakers are still required before advertising. Fifteen marketing tests, builds and desktop/mobile checks passed. Separate authenticated AI-visibility captures supplied real product imagery, while the proposed short video remained a storyboard, not a produced or published ad.
• Neon · retain the field contract, reconsider the runtime. The source review recommended keeping Fields as a portable schema and data engine, with Laravel as the initial application framework. A field already describes editing, validation, storage, relationships and filtering; the proposal separates that definition from mutable form and widget state. Local reproduction found zero bypassing a minimum-value validator and old validation errors surviving correction. A shared validation boundary and transactional storage were identified as prerequisites. This was an architecture assessment, not a completed port or a claim about the deployed database engine.