The prd step returns the PRD as structured fields and human.approve takes them as its document. The plan text every surface reads and the approval card's layout are both rendered from that one document, so what the human approves is what the implement workflow is handed. Replaces the separately generated OpenUI view, which could drift from the plan.
12 lines
474 B
SQL
12 lines
474 B
SQL
-- A task's plan as the structured document it was written as (JSON), which
|
|
-- the approval card lays out; plan holds the text rendered from it. Replaces
|
|
-- the generated view, which could say something other than the plan.
|
|
|
|
-- +goose Up
|
|
ALTER TABLE tasks DROP COLUMN plan_view;
|
|
ALTER TABLE tasks ADD COLUMN plan_document text NOT NULL DEFAULT '';
|
|
|
|
-- +goose Down
|
|
ALTER TABLE tasks DROP COLUMN plan_document;
|
|
ALTER TABLE tasks ADD COLUMN plan_view text NOT NULL DEFAULT '';
|