Update to Walla

Changed files

.codex-plugin/plugin.json →

skills/walla/SKILL.md →

skills/walla/references/custom-fields.md →

skills/walla/references/forms.md →

skills/walla/references/responses-and-automations.md →

skills/walla/SKILL.md

--- before
+++ after
@@ -39,17 +39,17 @@
 - Use the authenticated identity from the connection. Never ask the user for a user ID or token.
 - Keep read-only requests read-only. Do not create, edit, publish, enable an automation, or approve a custom-field build as a side effect.
 - Never imply that response values are unmasked. `list_responses` masks configured PII and omits file contents and download URLs.
-- Treat a protocol-level missing tool as a scope or deployment-feature gap. Ask the user to reconnect or re-authorize Walla for the missing capability; do not retry with fabricated arguments.
+- If a documented Walla tool is missing, the connection probably does not have that tool's OAuth scope. Ask the user to reconnect Walla and grant the capability. If the tool is still missing after reconnection, this Walla deployment does not offer the feature. Do not retry with fabricated arguments.
 - Expect some features to depend on the team's plan. Preserve the rest of the requested work when a paid feature can be cleanly omitted, but ask before changing the user's requested scope.
 
 ## Handle errors
 
-- On `forbidden`, stop retrying and explain the permission or OAuth-scope gap.
+- On `forbidden`, stop retrying. The user does not have permission on that team, workspace, or form, or a team admin disabled Walla MCP (or this capability) in the team's security settings. A team with MCP fully disabled does not appear in `list_teams`.
 - On `not_found`, re-run discovery and verify that the ID came from the correct team or workspace.
 - On `invalid_args`, read the actionable message and the relevant reference, correct the payload, and retry.
 - On `payment_required`, explain which feature needs an upgrade.
-- On `try_again`, wait briefly and retry the same call without changing its arguments.
-- On `internal`, do not guess at a fix or expose internal details; report that Walla could not complete the operation.
+- On `try_again`, wait briefly and repeat the call that returned it, with the same arguments.
+- On `internal`, do not guess at a fix or expose internal details; report that Walla could not complete the operation. If a write returned `internal`, re-read the object before you retry, because `form_apply_edits` is not idempotent. For `approve_custom_field_build`, call `get_custom_field_build` and then approve again; approval resumes safely.
 
 ## Deliver the result