34315ab7d7The stable Skills page missed the final SEP's Agent Skills compatibility clause, and its examples used abbreviated hashes and inconsistent byte sizes. Archived drafts also retained current-sounding source-of-truth guidance. This corrects the stable page directly to match already-established requirements: restores the compatibility clause, shows the resources capability and server/discover, explains omitted request metadata, and makes the example manifests and content consistent. It also labels archived documents as historical and fixes the SEP domain in AGENTS.md. This is an editorial alignment, not a new extension proposal; #142 remains separate. Validation: all JSON examples parsed; all 13 manifest entries checked against sample bytes for SHA-256 and size; the corrected specification builds with the VitePress publishing site; git diff --check passed. AI assistance: prepared with Codex.
1.9 KiB
Experimental Findings Template
Historical document. Frozen during development of SEP-2640; statements of current status and requirements below describe that draft-era context. See the stable specification for current requirements and the archive index for context.
Use this template when adding an entry to experimental-findings.md. Include enough evidence for another contributor to evaluate the result, and write "Not documented" rather than inferring missing details.
[Implementation or experiment name]
Date: YYYY-MM-DD or Not documented
Implementation:
- Repository: name
- Author: Name or handle
- Relevant artifacts: Links to skill files, server/client code, commits, or pull requests
Approach tested: Link to the relevant section of approaches.md, or describe the approach if it is not listed.
Setup:
- Clients tested: Names and versions
- Models tested: Names and versions
- Configuration notes: Relevant server, runtime, dependency, and operating-system details
What was tested: Describe the scenarios or behaviors evaluated.
Results:
- What worked: Observed successes
- What didn't: Observed failures
- What was surprising: Unexpected behavior
Requirements or design questions addressed: Link the finding to the current problem statement, use cases, or approaches.
Evidence and reproduction: Provide commands, configuration, logs, measurements, or links that let another contributor inspect or repeat the experiment.
Limitations: State what remains untested, uncertain, or specific to the recorded environment.
Sources and attribution: Link community input and identify contributors by name and handle where possible.