4 Commits

Include renames

Author	SHA1	Message	Date
weichen	add1fbb045	Add project-level surface aggregation and task-phase guidance (U6) ... Why: U6 extends pages from conversations into the task/project workspace - surfaces aggregate across conversations under the owner's project scope (project resolved authoritatively from the conversation row, never self-reported by the model), and the catalog guidance now organizes pages by task phase (requirements/execution/acceptance) while stating that task facts come only from real task records. Evidence: build/vet clean; surfacesvc suite green incl. the new project-aggregation test (owner isolation, cross-owner zero, history retained post-disable); genui/store suites green. Impact: New endpoint GET /api/projects/{id}/surfaces; Submit resolves project from conversation; catalog text guidance. Existing endpoints unchanged. Refs: proposal r2 U6; Dev task feature/generative-ui-u6	2026-10-12 02:12:42 +00:00
weichen	f5eb27df86	Add the surface action pipeline: ledger, guards, dispatch, submit (U5) ... Why: The approved U5 scope needs the action half of the loop: an idempotent ledger (migration v24), a single-choke SubmitAction (plugin activation, current-revision, action whitelist, params-hash idempotency), dispatch through the command bus so DangerHigh lands on the existing inline confirm card with no Confirmed passthrough (the endpoint does not even bind the field), the button-only generative-ui.submit storing form data in the plugin KV ledger, and catalog discipline rejecting unknown action ids at present time. Evidence: go build/vet clean; full go test ./... green; surfacesvc/ genui/store suites also green under AGENT_PG_TEST_DSN; red matrix covers disabled/stale-revision/cross-owner/unknown-action/idempotent same-and-different-params/danger-high-await-confirm and the endpoint forged-confirmed case. Impact: Additive migration v24 + new endpoint/command; existing endpoints and command semantics untouched (B-class whitelist starts empty per the approved scope). Refs: U5 action-scope r2 (approved, Documents #71); UI #46/#47; Frontend #56; Dev task feature/generative-ui-u5	2026-10-11 14:24:31 +00:00
weichen	75829fa442	Add the Surface store, activation guard, and EXT-17 host capability ... Why: Generative UI proposal U2 needs the host side of the contract: owner-isolated surface storage with revision CAS, an execution-level enable/disable ledger (default-off, epoch bumped on every transition so in-flight submits after a disable are rejected), a single-choke-point service that validates specs (strict decode + catalog rules) before saving, event publish with pending recovery, the optional SurfaceHost extension capability, and direct API endpoints that share the same guard (no bypass by entrance). Evidence: go build/vet clean; full go test ./... passes (SQLite); surface store tests also pass under AGENT_PG_TEST_DSN (PostgreSQL); surface.txt regenerated via the AST snapshot test. Impact: Additive migration v22 (new tables only); existing endpoints and plugin_grants semantics untouched; old consumers unaffected. U3+ (data binding, actions, frontend) deliberately out of scope. Refs: Documents proposal 2026-10-10-generative-ui-plugin.md (r2 U2); Core PR #25; Dev task feature/generative-ui-u2	2026-10-11 08:26:24 +00:00
weichenandCursor	cd5b82186d	Add the public extension surface and platform services ... Why: Downstream products must extend the base through a public package and host API instead of editing internal code. Evidence: go test ./... passed, including plugin v2 assets, sidecar startup, migration v13, pending confirms, HITL timeout, hash embedder, command pairs, and the extension surface snapshot. Impact: apiVersion 2.0-experimental rejects empty network allowlists for declarative HTTP. Hash embeddings stay opt-in via models.embedding.provider=hash. Plugin secrets resolve per owner at execution time. Refs: docs/proposals/2026-10-01-plugin-contract-v2.md Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-01 10:35:02 +00:00