everjust-website-infra-views

Connect to the tenant's /xmlrpc/2 endpoint with xmlrpc.client, authenticate as the admin user, and call execute_kw write on ir.ui.view with the new arch. The generic MCP update tool blocks ir.ui.view as a security model, so XML-RPC is the only remote write lane without SSH.

A website-specific fork with active=False shadows and disables the active base view for that site. Search ir.ui.view by key for both base and fork rows, then reactivate the fork and write your arch into it rather than the base view.

No. Writes over the MCP/XML-RPC lane hot-invalidate the compiled-template cache immediately, so the change is live on the next request. The restart requirement only applies to the box odoo shell lane over SSH.

Write to the website.robots_txt field, which is a regular field writable via generic update or XML-RPC, not an ir.ui.view. Its contents are appended to Odoo's generated robots.txt under a '# custom #' marker block.

The tenant origin returns 503 under concurrent request load. Run reads, writes, and verification curls sequentially one at a time with backoff between calls, and retry a 503 after a pause instead of fanning out parallel requests.

Use website_edit_page for ordinary page content, the SEO skill for per-page metadata and auto JSON-LD, and the box odoo shell lane when you have SSH access. This lane is only for sitewide chrome and infra views the MCP refuses to write.