webmcpify v0.6.0

webmcpify v0.6.0

Resume an integration with evidence about what changed. The skill now records
app, contract, runtime and browser inputs, retains still-valid checks and asks
for fresh verification when those inputs change or dependencies are unknown.
Interrupted mutations require read-path reconciliation before any retry.
Execution-capable runners serialize that journal through a stable sidecar OS lock
that remains valid while atomic manifest writes replace the manifest inode.

What changed

• Removed automatic unpinned guidance-package execution. Official docs are read
  directly; optional package execution needs an exact reviewed version and approval.
• Scoped browser work to dedicated test contexts, approved origins and fixtures,
  with local redacted evidence and explicit untrusted-content boundaries.
• Added independent effect checks and unchanged-neighbor/invariant assertions.
• Bounded optional model evals by runner version, data approval, steps, time and spend.
• Added React remount/Strict Mode and Svelte cleanup acceptance guidance.
• Defined stable manifest-lock ownership and fail-closed stale-owner recovery;
  added a two-runner atomic-replacement concurrency regression.

Compatibility and evidence

This is a backward-compatible skill workflow expansion from v0.5.1. Manifest v4
remains supported; missing input provenance requires new verification evidence.
No runtime dependency or TS/JS API changes are introduced. The v0.5.1 browser
input capability probe remains in place.

Repository tests and the prepared native Chrome fixture check different layers.
The fixture does not run the full agent skill. Framework recipes are not a
framework certification; optional model evals have not been run for this release.
Security text addresses reported audit causes; fresh directory verdicts depend on
re-indexing and must be checked after shipment. No new PASS badge is claimed.

Compare: v0.5.1...v0.6.0