Implement ADR-0063/0064: split ask/build agents by surface; tool scoping

[xuyushun441-sys]

Implementation tracking for ADR-0063 (two agents bound by surface) and ADR-0064 (tool scoping). Decision PR: #2167. Landscape: docs/audits/2026-06-ask-build-agent-development-assessment.md.

Split the personas (reverse ADR-0040 unified assistant)

• Remove the unified ask-carries-all-skills definition + per-turn intent preamble (service-ai/src/agents/data-chat-agent.ts); ask carries only surface:'ask' skills.
• Delete the buildRegisterActive degradation shim (service-ai/src/agent-runtime.ts:179) — no longer needed once surfaces are separate.
• Bind agent → surface in ../objectui (data console → ask, Studio → build); keep the picker hidden/builder-only.

Naming (finish both sides of the rename)

• service-ai/src/agents/data-chat-agent.ts → ask-agent.ts; DEFAULT_DATA_AGENT_NAME → ASK_AGENT_NAME (keep LEGACY_DATA_AGENT_NAME='data_chat').
• ../cloud/service-ai-studio: make build the canonical id (currently still metadata_assistant); register metadata_assistant as the permanent alias.
• Prose sweep: "Data/Metadata Assistant" → ask/build; aliases live only in the alias table.

Skill ↔ agent affinity (ADR-0063 §3)

• Add surface: 'ask' | 'build' | 'both' to SkillSchema (spec/src/ai/skill.zod.ts); backfill the four built-in skills.

Tool scoping (ADR-0064)

• Remove the global fall-through in tool resolution; resolve wildcards against skill-claimed names only (kill the actions_executor empty-array + fall-through hack).
• Add a surface:'both' schema_reader skill owning describe_object/list_objects/query_data; stop dual-listing by comment.
• Make incompatible skill↔agent binding a fast load error in resolveActiveSkills.
• Tests: tools(ask) contains no create_*/*_metadata/blueprint tools (cloud + OSS); authoring tools present only under build.

Withdraw tenant custom agents (ADR-0063 §2)

• spec/src/kernel/metadata-plugin.zod.ts: set agent type allowRuntimeCreate:false, allowOrgOverride:false.
• Filter custom agents from the runtime catalog; drop the app.defaultAgent custom-agent guidance in the cloud plugin.

Deferred

• D4 deployment guardrail-floor schema — defer (no tenant agent to floor once the above lands).

[xuyushun441-sys]

Implemented and merged across framework + cloud:

• framework feat(ai): split ask/build agents by surface + tool scoping (ADR-0063/0064) #2181 (merged, main e411a8219) — surface on SkillSchema/AgentSchema; ask persona split (dropped the unified INTENT-FIRST classifier + buildRegisterActive shim); schema_reader (surface:'both') for the shared reads; affinity enforced as a load error in resolveActiveSkills; agent type allowRuntimeCreate:false, allowOrgOverride:false + catalog filtered to platform agents; data-chat-agent.ts→ask-agent.ts.
• cloud objectstack-ai/cloud#417 (merged, main 3d72d8790) — build agent surface:'build' + attaches schema_reader; metadata_authoring/solution_design → surface:'build'; stopped dual-listing the shared reads; dropped the custom-agent guidance.
• objectui — no change needed: surface binding (alias groups, isBuildAgent/isAskAgent, aiStudio gate, hidden picker) already in place.

Checklist: persona split ✅, naming ✅, surface field + backfill ✅, tool scoping (no global fall-through; tools(ask) carries no authoring tools — asserted) ✅, withdraw tenant agents ✅. D4 left deferred per the issue.

Note: several items were already done in main ahead of the ADR text (the ask rename; the resolver was already skill-scoped; build was already canonical+aliased). The cloud .framework-sha bump also required binding 18 control-plane script actions to satisfy framework's unrelated new action-script guard.

[xuyushun441-sys]

Keeping this as the single live tracker for ADR-0063/0064; closed #2165 (the near-duplicate follow-up) as superseded.

The code split is done (this issue's checklist + #2181 + cloud#417). The one tail this was reopened for — the prose sweep / surface documentation — was the third-party skill-authoring contract skills/objectstack-ai/SKILL.md, which still described the old ADR-0040 unified data_chat assistant. That's fixed in #2194:

• SKILL.md rewritten to the two surface-bound agents (ask/build); data_chat/metadata_assistant reduced to alias-table mentions only.
• surface: 'ask'|'build'|'both' field + built-in skill affinities documented; tools = union of surface-compatible skills' tools (no global fall-through).
• surface:'build' skills documented as inert on OSS — intentional tiering, with graceful build-intent degradation.
• docs/adr/PRIORITIZATION.md stale 0040 row reconciled.

After #2194 merges, the only outstanding item is D4 (deployment guardrail-floor), which remains deferred (no tenant agent to floor once withdrawal landed). Suggest closing this once #2194 is in and the D4 deferral is acknowledged.

[xuyushun441-sys]

All 13 checklist items are done; ticked above. Summary:

• Code (this repo): feat(ai): split ask/build agents by surface + tool scoping (ADR-0063/0064) #2181 — persona split, surface field + skill backfill, schema_reader (both), no global fall-through, affinity load error, agent type closed (allowRuntimeCreate:false), catalog filtered, ask-agent.ts rename. Alias ESM/CJS sharing follow-up in fix(service-ai): share agent-alias registry across ESM/CJS builds + decouple agent catalog from it #2190.
• Cloud: cloud#417 — build canonical + metadata_assistant permanent alias, build skills surface:'build', dropped app.defaultAgent guidance. (Cross-repo; please confirm from the cloud repo — not visible here.)
• objectui: surface binding / hidden picker / graceful build-agent absence already in place ([P0] Add native cross-object rollup/summary capability (parent aggregates of child rows) #1868, [P2] create_record outputVariable may not be referenceable in later flow nodes (needs confirm) #1873).
• Docs tail (what this was reopened for): the third-party skill-authoring contract skills/objectstack-ai/SKILL.md still described the old ADR-0040 unified data_chat assistant — fixed in docs(skills): sweep objectstack-ai SKILL.md to the ask/build two-agent model (ADR-0063/0064) #2194 (merged 9796cee4): rewritten to the ask/build two-surface model, surface field documented, surface:'build' documented as inert-on-OSS (intentional tiering), PRIORITIZATION.md 0040 row reconciled.

Duplicate follow-up #2165 closed as superseded by this issue.

D4 (deployment guardrail-floor schema) remains deferred — no tenant agent to floor once withdrawal landed; tracked in the audit (docs/audits/2026-06-ask-build-agent-development-assessment.md), not blocking.

Closing — ADR-0063/0064 fully landed bar the deferred D4.