Wesper v0.4.1

Wesper 0.4.1 adds package attribution and a richer content model, and improves collection across WordPress environments.

Changes

• Link blocks to package metadata and discover nested MU-plugin entry files that PHP actually loaded.
• Observe post-type and taxonomy registration callers, including taxonomy-to-post-type associations. Ambiguous or unmapped owners remain explicitly unknown.
• Warn when binding or context declarations refer to attributes missing from the block registry, preserving the original evidence.
• Improve REST handling for subdirectory, query-route and plain-permalink installations, permission-limited requests and malformed slices.
• Strengthen credential redaction and replace CLI output files atomically so a failed write preserves the previous manifest.

Compatibility and verification

The manifest remains contextVersion: 1; collector semantics are 0.2.3. Ownership and taxonomy additions are optional and currently WP-CLI-only. Metadata matches and registration callers do not prove rendering behavior or a package's complete footprint.

Release preparation passed 186 tests, typecheck, build and installed-package checks. The implementation also passed WordPress 6.5.5/7.1.0 integration and Node 20/24 CI, plus a read-only collection and focused rendering proof on a running Docker site.

Node.js 20 or later is required.

Wesper v0.0.4

Wesper 0.0.4 expands the read-only WordPress capability manifest with more runtime registry evidence.

• Collect block relationships, context, registered styles, asset handles, and dynamic-render status through WP-CLI and overlapping core REST fields.
• Report must-use plugins and post-type hierarchy and supports through WP-CLI, with overlapping post-type fields over REST.
• Clarify that the legacy plugin block classification means a non-core namespace, not verified implementation ownership.
• Extend the optional manifest schema fields and deterministic normalization; collector semantics version is now 0.2.0.

These facts describe registered capabilities; they do not prove front-end behavior or identify repository ownership. Collection remains read-only.

Wesper v0.0.3

Wesper 0.0.3 adds native WordPress references and evidence-aware helpers for downstream consumers.

• Read-only collection through WP-CLI and core WordPress REST endpoints, with bounded requests and cancellation.
• Native colour, typography and spacing references, exact token/block/field lookups, focused context, and explicit compatibility checks.
• More accurate binding fields, partial-evidence handling, credential redaction and reproducible manifest hashes.
• Packaged consumer examples and a reproducible Block Runner comparison that preserves native references and intentional literals.

Requires Node.js 20 or later. Core REST evidence remains partial and cannot satisfy strict collection. Wesper does not modify WordPress content.

Validation: package checks on Node 20 and 24, collector conformance on WordPress 6.5.5 and 7.1.0, and packaged consumer proof passed on the preceding code-identical commit; the release workflow reruns package verification before publication.

Install with npm install wesper@0.0.3 after the release workflow completes.

v0.0.2

Wesper v0.0.2 release.