{"version":"2.1.248","anchor":"design-rpc-replies-validated-against-a-per-method-schema","canonical_anchor":"design-rpc-replies-validated-against-a-per-method-schema","heading":"Design RPC replies validated against a per-method schema","tier":"internal","area":"Claude Design","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/design-rpc-replies-validated-against-a-per-method-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Design RPC replies validated against a per-method schema\n\nReplies from the design service are now validated against per-method schemas.\n\n**What**\n\nReplies from the design service are now checked against a schema chosen by the method name, covering listing and reading projects and files, finalising a plan, writing and deleting files, registering and unregistering assets, creating a project and reporting validation.\n\n**Details**\n\n- Writing without a plan token still hard-fails in non-interactive sessions, telling you to finalise a plan first.\n\n**Evidence**\n\n`writing without a plan_token requires a one-time interactive project approval`\n\n- Area: Claude Design\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}