Prove the release, then reduce the work it does

Wednesday moved tested changes into live releases and addressed the work happening underneath them: database writes, runtime dependencies and optional integrations. Alongside that, Teamspace gained a clickable concept for people and AI colleagues working together.

• GrowthScout · consolidate and verify the release. The pending embedding-retry and worker-monitoring changes were merged with bounded sitemap discovery and the wider Scout changes, then deployed. Final Scout CI passed 3,195 tests; one opt-in Stripe sandbox rehearsal was skipped. Live dashboard, planner, release identity and health checks passed. Funding and page-URL hash migrations were applied, and a live query plan selected the new URL index. Legacy billing links and queue lease overlap remained unresolved; passing the release checks did not close those investigations.
• GrowthScout · batch crawler link writes. The crawler replaced sequential link saves under a website lock with validated upsert batches of at most 100 inside the same transaction. Existing link IDs and first-seen timestamps survive recrawls; stale links are removed atomically. A disposable MariaDB test reduced a 240-link snapshot from 240 write statements to three, including on recrawl. Twenty-seven focused tests and 3,196 Scout CI tests passed. The fix was deployed and worker progress checked; the statement-count result is a regression measurement, not a production latency claim.
• db3 · test the documentation’s installed runtime. A broad server import had pulled unavailable database dependencies into the slim documentation image. A narrow browser-JSON export and packed-consumer checks fixed that boundary, with a runtime smoke test inside the finished image. The framework suite passed 868 tests with MariaDB and Redis. The deployed website’s feature-app guide, syntax highlighting, search, Markdown and LLM context were checked live. Public framework source and CI were updated; no npm package or release tag was published.
• GrowthScout · optional support stays quietly disabled. Unconfigured Intercom support had returned HTTP 503 and triggered a warning toast in otherwise working screens. The deployed fix leaves support disabled without raising that warning. Live dashboard and planner checks passed alongside 3,199 tests. This corrects the unavailable-feature behaviour; Intercom chat still requires configuration.
• GrowthScout · publish clearer policy terms. Refund and traffic-guarantee wording was published with the correct cancellation path. Standard processing terms replaced the DPA placeholder, and the privacy policy gained active-account retention wording. Focused tests and live browser checks confirmed the updates. The liability amount and verification of operational deletion and provider safeguards remained unfinished; publication was not a legal sign-off.
• Teamspace · a separate, testable product concept. The brief and clickable prototype moved into their own repository. The concept supports project conversations, mentions of AI colleagues, team-building interactions, member profiles and a client view. Main flows and responsive layouts were checked. All actions use simulated local state: there is no backend, real AI execution, connected tooling or invitation delivery. db3 is the planned framework dependency, not an installed integration in this prototype.