Render Studio saved results directly by ID #4
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Zayden-Jung/probably-rendering-one-more-pixel-tonight#4
Reference in New Issue
Block a user
Delete Branch "codex/studio-result-page"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Saved Studio URLs currently load LayoutWorkbench and expose editor controls. The intended flow is API → saved ID → final result: a coding agent chooses the template and submits images/text through HTTP, then the user directly opens /studio/template-layout?id=.
Add a separate server-loaded result page and NativeResult artwork renderer with no editor imports, controls or editing handlers. Both standard and fixed templates are resolved from the saved record. Missing, invalid, duplicate, nonexistent and archived IDs return 404. Existing saved-layout and /designs links redirect to the result URL; template previews render artwork without editor controls. API url/renderUrl and new linked Wiki posts use the canonical result URL.
Update agent documentation and the idempotent Wiki publication script (preserving the original toolbox appendix). Extend remote smoke and production checks to cover ID-only results, redirects, absence of editing controls, double-click/context-menu behavior and rendering with JavaScript disabled. Remove PR checks against the old deployed baseline; PR code is validated by the isolated remote build/runtime smoke. Strict public-server acceptance remains a post-deployment gate.
Validation: staged diff check passed. Latest head
b550c15passed remote ces-control Studio CI 452 (type checking, 7 tests, production build and server-loaded result/redirect smoke checks) and Wiki CI 453 (type checking, 39 tests, production build/smoke, real PostgreSQL + S3 integration and authentication exercises). No local compilation or preview was run. The existing online Wiki post and deployed route will be updated and verified after the user manually merges; they are not claimed complete in this PR. Existing toolbox routes remain available.Waiting for the user to merge manually. No direct main push or automatic merge.