sys_page_schema standard layer had two runtime writers: the converter import CLI and AiLocalReleaseExecutor's raw JDBC INSERT (the critic-flagged net-new bypass). Introduce PageSchemaWriter as the single runtime write function (typed-recipe validation warn-not-block + etag + UPSERT), and route both a new admin-gated PUT /api/page/schema/{id}/standard endpoint (net-new producer for the design-center 'new feature' path) and AiLocalReleaseExecutor.applyPageSchema through it. No remaining raw INSERT into sys_page_schema in the AI runtime write path.
Scope: page_schema runtime write only. The deployment-package SQL-text generator (AiAgentService.pageSchemaSql, offline human-apply artifact) and SchemaImportCli (batch converter import) are separate legitimate paths. AiLocalReleaseExecutor sys_serviceflow/sys_menu raw writes remain (follow-on). Completion = code-complete, integration-pending (end-to-end render proof env-gated).
Tests: PageSchemaWriterTest (4) + PageSchemaControllerTest putStandard success/403/split (27 total) + AiLocalReleaseExecutorTest/AiAgentApiPipelineTest unchanged-green. TDD.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Per the architecture-review redline (EIP3 决策会纪要: AI claims limited to 'AI-assisted, human-reviewed'; never promise 'AI full-auto development'), soften endpoint @Operation summaries, the default task objective, and AI docs that read as committed full-automation. Endpoint paths/method names unchanged (API contract). Added a capability-boundary disclaimer at the top of AI_AGENT_AUTO_DEVELOPMENT.md. 33 platform-ai tests green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
AiAgentController's endpoints relied only on the SecurityFilterChain (prod: /api/** authenticated; dev: permitAll), so any authenticated user could trigger AI writes/actions (auto-develop, local-apply, change-sets, deployment packages) - a lower bar than the comparable overlay/standard-page write endpoints which require admin.
Gate the 14 mutating/action POST endpoints with requireAdmin() (UserSession CURRENTUSER == ADMIN), aligned with PageSchemaController.requireAdmin / AdminWriteController. Read GETs and the pure validate-schema/access-check endpoints stay open. Actual three-truth writes are now admin + localhost double-gated.
Tests: AiAgentControllerTest + AiAgentApiPipelineTest run under an ADMIN session (+ AfterEach clear); added a 403 test for non-admin. 61 platform-ai tests green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>