Skip to content

Exercise core skill discovery with additional directory layouts - #8

Merged
jonathanhefner merged 1 commit into
mainfrom
agent/core-discovery-launch
Sep 18, 2026
Merged

jonathanhefner merged 1 commit into
mainfrom
agent/core-discovery-launch

Conversation

@jonathanhefner

@jonathanhefner jonathanhefner commented Sep 18, 2026 •

Copy link
Copy Markdown
Member

Core now includes a README-only directory under skills/ and a nested reference SKILL.md inside an existing skill. The existing discovery check continues to require the two valid immediate-child skills, exercising their availability alongside these additional directory layouts.

This keeps the measured property focused on valid-skill availability. It adds no rejection or exclusion judgment, observation type, installation, or guide step.

Validation:

  • All 64 tests pass; committed distributable and syntax checks pass.
  • CI passes on Linux and Windows with Node 22 and 24.
  • Native runs of unchanged packages at 2858b98: Codex reports 19 pass; Copilot reports 15 pass, 2 fail, and 2 not_verified. Both advertise and load alpha/beta. Neither advertises the new surrounding entries; that absence is unscored.
  • Copilot retains its argument/environment expansion failures and unavailable recovery MCP evidence. It also batches observation collection before serial recording despite the guide requiring immediate recording. Codex follows the required sequence. Saved observations match native evidence, and both reports match deterministic reevaluation.

Both clients were launched with APC_VALUE=ambient conflict. Copilot's unconfigured probes received that value while the configured probe received its fixture value, exercising environment precedence. Codex's unconfigured probes omitted it, so that conflict was not exercised there. This is native-run evidence; the PR adds no new environment case or setup requirement.

Include a README-only child and a nested reference SKILL.md beside the
existing immediate-child witnesses. This exercises valid-skill
availability with ordinary surrounding package content while retaining
the existing observation and reporting workflow.

Keep the measured property focused on the availability of alpha and
beta; these fixtures do not add an exclusion or rejection claim.
@jonathanhefner
jonathanhefner marked this pull request as ready for review September 18, 2026 23:09
@jonathanhefner
jonathanhefner merged commit 1e3f16e into main Sep 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant