[milestone Milestone 4 ] Add `schemas/aep/artifact-attestation.schema.json` — produced-artifact provena...

[telleroutlook]

🤖 Auto-filed from milestone doc bullet.

Repo: WasmAgent/wasmagent-protocol
Milestone: Milestone 4 — Evidence types beyond execution
Bullet:

Add schemas/aep/artifact-attestation.schema.json — produced-artifact provenance (keys: artifact_uri, digest, produced_by_run_id, tool_name, signature); register in index + valid/invalid fixtures.

Relevant code context (from worktree)

new (does not exist yet): schemas/aep/artifact-attestation.schema.json
new (does not exist yet): valid/invalid
contains 'schemas': index.d.ts
contains 'schemas': src/wasmagent_protocol/cli.py
contains 'schemas': src/wasmagent_protocol/drift.py

Implementation note: Files marked "new (does not exist yet)" must be created from scratch. verify-first should return PROCEED (not NOT_YET) — there is no prerequisite blocking this work.

Acceptance criteria

• Command npm install && npm run build && npm test passes
• The specific work described in the bullet above is implemented in the smallest number of files required.
• No unrelated files touched (git status --short output limited to the intended change).

Notes for the implementer

This issue was auto-created by SweepMilestoneBulletToIssue. The bullet text is verbatim
from the milestone doc. If ambiguous or too large for a single implement cycle,
verify-first should return NEEDS_SPLIT with sub-issue proposals or NEEDS_HUMAN with the blocker.

---

Filed automatically.

Blocked-by #120

[telleroutlook]

🤖 Auto-analysis: this issue has been parked 2 times and needs human attention.

Analysis: failed to parse LLM response: {
"verdict": "needs_split",
"explanation": "Artifact attestation depends on 'produced_by_run_id'... [truncated]

[telleroutlook]

🤖 Auto-analysis: this issue has been parked 2 times. A prerequisite sub-issue has been filed: #140

Why: The verify-first gate expects all four artifacts (schema file, index entry, valid fixture, invalid fixture) to be present simultaneously before returning PROCEED, but a single issue creates an all-or-nothing deadlock: bots cannot commit partial work, yet the verification logic rejects incomplete states. The conformance test invariant requiring both fixture polarities to pass/fail validation means even a complete schema with index entry fails verify until fixtures exist.

This issue will be retried once the sub-issue is resolved.

[telleroutlook]

🤖 Auto-analysis: this issue has been parked 3 times. A prerequisite sub-issue has been filed: #147

Why: verify-first has a circular dependency: it cannot return PROCEED for creating new files from scratch if its precondition check requires those same files to exist.

This issue will be retried once the sub-issue is resolved.