I3308 — Zed validates and completes .ai files against the repository's own schemas

○READY wave 0 · p3 · implementation profile · parallel safe

Part of a-provider-carries-the-contract-natively — Each agent client carries the contract through its own extension points, generated once and checked for drift.

Objective

Project YAML and JSON schema associations from share/schemas onto .zed/settings.json through the existing Zed adapter, so .ai records get validation and hover in the editor.

Why

The Zed adapter projects skills and workflows (ADR 0140) but not the schema associations the owner's design asked for (10-11). Rebound to the new intent criterion #editor-validates-the-layer (Zed validates .ai records against the layer's schemas through generated associations). It does not serve #one-plugin, which it cannot make true. Proposed in ADR 0214 (A provider's native extension points carry the contract as generated projections; Majordomus neither embeds nor patches the worker's runtime) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c222#2.

Current state

apps/majordomus-cli/src/editors/zed.rs has no schema association.

Desired state

Associations derived from share/kinds.yaml; generate --check holds them.

Scope

• apps/majordomus-cli/src/editors/zed.rs

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• Every kind with a schema has an association
• A new kind gains one with no edit to the adapter

Validation

• majordomus generate --check
• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --lib editors::zed

Evidence required

• test_zed_schema_associations

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3308.yaml. Read it back with majordomus plan show I3308.