Repository navigation
Add Agent Plugins Conformance — Core - #1
Merged
Merged
Conversation
jonathanhefner
force-pushed
the
agent/initial-conformance-suite
branch
2 times, most recently
from
September 15, 2026 22:40
e702282 to
342188f
Compare
jonathanhefner
force-pushed
the
main
branch
from
September 15, 2026 23:17
147707e to
527dbf9
Compare
jonathanhefner
force-pushed
the
agent/initial-conformance-suite
branch
from
September 15, 2026 23:17
342188f to
9edcda3
Compare
Organize installable packages under plugins/ so additional fixtures can be introduced without relocating the initial plugin. Keep development tooling at the repository root and verify MCP and CLI reporting from an isolated installed copy. Exercise skill discovery and stdio MCP launch behavior through observable fixtures. Derive stable pass, fail, and not_verified outcomes from collected evidence, keep developer expectations separate, and preserve evidence and specification references in JSON. Bundle the official MCP SDK to avoid dependency installation at runtime. Apply the site licensing policy and include license notices inside the installable package.
jonathanhefner
force-pushed
the
agent/initial-conformance-suite
branch
from
September 15, 2026 23:22
9edcda3 to
7582916
Compare
consumers Group human results by capability and missing observations, and show expected and observed values for failures. Preserve flat JSON results with explicit categories and readable labels so consumers can evaluate complete capability groups or individual cases. Remove expectedPasses and unmetExpectations from the report contract. Successful report generation exits zero regardless of case outcomes; consumers enforce their own acceptance policy with the documented jq queries.
Record the unchanged plugin revision, isolated loading setup, native skill and MCP sequence, and independently checked report transfer. The observed failures exercise path and placeholder requirements without treating selected coverage as a whole-client verdict. Keep the deterministic reporter output distinct from the collecting model summary, which reversed one failure explanation. Clarify that the earlier adapted Codex run does not establish the behavior of its native plugin loader.
Remove collection metadata and duplicate result categories. Scope stdio MCP checks under mcp.stdio and name their working-directory scenarios so consumers can select behavior groups directly by ID prefix. Place the run identifier below the client and omit the evidence-source and scope footer. Preserve observation payloads and case outcomes while updating the guide, jq examples, and missing-evidence rendering tests.
Use `mcp-stdio` to select the subprocess evidence schema directly. Evaluate the three immediate child skill observations as one discovery result while retaining individual evidence and missing or incorrect marker diagnostics. An incorrect supplied marker fails the aggregate even when another skill is missing.
jonathanhefner
commented
Sep 16, 2026
Keep the collection procedure in the guiding skill and document installation, report interpretation, and consumer queries in the README. Preserve a brief automated-test boundary in the development instructions; keep historical native-run evidence with the PR validation records.
jonathanhefner
force-pushed
the
agent/initial-conformance-suite
branch
from
September 16, 2026 16:12
d9e0ac4 to
4187f6a
Compare
jonathanhefner
commented
Sep 16, 2026
Let the guiding skill initialize an explicit output path and update it after each observation. Starting a run clears prior evidence; later submissions replace the complete observation for that component. Keep collection state in the report itself, create missing parent directories, and replace the file atomically so rejected writes preserve prior evidence. Keep collection output terse and move human presentation to a read-only summarizer of saved verdicts. Remove the unused run ID contract, reporting MCP tool, and batch CLI so programmatic consumers can read the requested artifact without extracting agent output. Cover resets, replacement, validation and write failures, copied-plugin execution, and saved-report rendering. All 41 tests and syntax/distributable checks pass.
jonathanhefner
commented
Sep 17, 2026
Keep validation tied to observation structure and identity so the evaluator can assess client evidence independently of its size. Exercise the current reporting contract in tests. Align the plugin directory and manifest as agent-plugins-conformance-core. Document the prompt, report shape, status meanings, complete acceptance queries, and plugin-relative summarizer invocation. Associate coverage limits with the behaviors the fixtures exercise. Classify the upstream schemas and license as vendored and generated for GitHub review. Verified all 40 tests, the committed distributable, the JSON example, and all documented jq queries.
jonathanhefner
commented
Sep 17, 2026
Require only the report destination to initialize collection. Client identity is not reliably available to the collecting agent and does not affect evaluation; keep the saved report and summary focused on the recorded evidence and outcomes. Introduce the report through an abbreviated JSON example before explaining its fields and statuses. Keep coverage prose tied to the behaviors exercised by the fixtures. All 40 tests and syntax/distributable checks pass. Verified the JSON example against evaluator output and executed all four documented jq queries.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Agent Plugins Conformance — Core, an installable plugin at
plugins/agent-plugins-conformance-core, for selected Agent Plugins 1.0.0 client checks.The user asks the agent to run the
conformance-guideskill and save a JSON report to an absolute path. The guide collects skill markers and MCP launch observations, and its reporting script evaluates the evidence and writes the report directly to that destination.Behavior
not_verified; consumers choose the results they require.Validation
jqqueries were executed against it.Native client exercise
GitHub Copilot CLI 1.0.83 loaded an unchanged copy of commit
3601a9ethrough native--plugin-dirsupport on 2026-09-17. The plugin tree is2c43d53ac8d6d73074a2b7b62c341ebd99e96862. The run used an isolated workspace and client configuration, with the prompt supplying the skill request and report destination.All three skills loaded and all four MCP tools returned observations. Initialization used exactly
{"action":"start"}, followed by six successful sequential recording calls. The agent recorded the two probe skills and four MCP observations, but omitted the guide observation. The saved evidence matched the submitted observations, and the report matched deterministic evaluation. All 18 plugin files remained unchanged. Separate summarization preserved the report bytes.The report contained 11 pass, 2 fail, 1 not verified. Skill discovery remained
not_verifiedbecause the guide observation was missing. The two failures were:mcp.stdio.args.preservation-and-expansion$APC_VALUEexpanded in an argument although it is not a specified placeholder.mcp.stdio.env.expansion${PLUGIN_DATA}remained literal inside a configured environment value.The client batched the four independent observation calls before recording them sequentially. Its final prose incorrectly claimed that every expected observation had been recorded; the JSON accurately preserved the missing guide evidence. This run verifies report delivery and evaluation, while also recording incomplete execution of the collection procedure. Every report write completed before the next began. The reporter requires sequential writes to a destination.
The PR remains draft. Coverage is limited to the documented fixtures, and skill discovery relies on the collecting agent's account of how the client exposed each skill.