Spaces:
Running
Running
Commit History
20 days ago
-
docs(settings): AgentSpot DP Settings agent document; the sender is that agent, not Agent Q
Paste-ready agent instructions, the settings document, the one tool it calls today (config_check), the phase-2 get_settings / save_settings scope, examples and connector setup. Wording in the inventory, flag registry, example document and sprint entry corrected: any caller of build_demo_from_brief passes the document; Agent Q is not the owner of it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>57c47f4 -
feat(mcp): settings document on build_demo_from_brief replaces per-run Supabase settings reads
A separate TSE app owns an SE's DemoPrep settings and Agent Q hands them to the build as one JSON document (schema 1.0, the `settings` keyword argument). When present, the build takes model, data size, column naming style, object prefix, liveboard name, tag, share-with and geo scope from it and reads nothing from the SE's Supabase settings: the controller skips its startup read and the three mid-run re-reads are guarded. Explicit owner_email / ts_url still win; a blank ts_url falls back to the document's URL, then its environment label through the TS_ENV table. A bad document is refused before a slot is taken, naming the key. - demoprep_app/settings/payload.py: the one parser and apply step (the data-size presets live here now) - chat_interface: ChatDemoInterface(settings_from_supabase=...), _settings_source - run record carries settings_source and settings_schema_version - docs: settings inventory with decisions and the phase-2 Supabase scope, the example document, the brief for …0d02061
