WordPress ability source evidence

Review ability candidates in an exact GitHub snapshot.

Identify registration calls, classify load and viability evidence, and investigate statically observed callback branches—without running repository code.

Repository root or /pull/number. Public targets only.

No account, token, or server-side report storage.

WP-Admin relationship

Related, not a clone.

Ability Preflight borrows the investigation workflow—indexing ability candidates, inspecting metadata and callbacks, and explaining client exposure. The Abilities Explorer in an installed WordPress site can inspect that site's runtime registry; this tool instead classifies source candidates in an exact GitHub snapshot and never claims they registered at runtime.

Installed WP-Admin explorerLive runtime registryKnows what the active site exposes at that moment.
Ability PreflightExact source snapshotKnows only what bounded static evidence can establish.
01Exact snapshot

Default-branch or pull-request head resolved to a commit SHA.

02Broad identification

Real registration calls are retained, including invalid and dynamic candidates.

03Separate classifications

Discovery, load, hook, category, viability, REST, and MCP keep their own reasons.

04Bounded investigation

Repository code is never executed; static branches and stopping points stay visible.

Ready to inspect

Evidence from candidate call to analysis boundary.

The explorer parses PHP syntax, preserves source-level issues and ambiguity, connects only compatible static load roots, and reports exactly where proof stops. It is an investigation aid, never a safety or runtime certificate.