v0.16.1 - Browser-Agent Validation And Readiness Explanations

Phase 16 adds standard-neutral browser-agent validation output for measuring whether Descuff materially improves how agents use a site.\n\nHighlights:\n- Browser-agent scenario evidence and before/after effort summaries.\n- Readiness explanations tied to concrete validation evidence.\n- Scenario boundary enforcement for allowed routes and origins.\n- Typed validation failures for safer automation and clearer reports.\n\nValidation:\n- CI passed.\n- Release checks passed.\n- Packed install smoke passed.\n- npm registry verification passed for 0.16.1.

v0.15.2 - Apache 2.0 License Metadata

Descuff 0.15.2 republishes the Phase 15 package set with Apache-2.0 license metadata on npm.

Highlights:

• Repository and public package manifests now declare Apache-2.0.
• README license badge now points to Apache-2.0.
• Contribution guidance documents Apache-2.0 inbound contribution terms.
• npm package pages now reflect the updated license metadata.

Validation before release:

• pnpm run ci
• pnpm run release:check
• pnpm run release:install-smoke
• GitHub Actions trusted publish and registry verification passed.

npm: https://www.npmjs.com/package/descuff/v/0.15.2

v0.15.1 - Real WebMCP Execution Improvements

Descuff 0.15.1 adds the Phase 15 WebMCP runtime validation work published to npm.

Highlights:

• Explicit WebMCP runtime execution scenarios for safe read-only browser validation.
• Framework-neutral browser-agent task benchmark evidence.
• Browser-agent benchmark JSON and Markdown artifacts.
• Optional .descuff/runtime.json support for real browser/runtime evidence.
• Runtime proof summaries in scan, start, validate, and finish output.
• Validator checks for inconclusive or regressed browser-agent benchmark evidence.

Validation before release:

• pnpm run ci
• pnpm run release:check
• pnpm run release:install-smoke
• GitHub Actions trusted publish and registry verification passed.

npm: https://www.npmjs.com/package/descuff/v/0.15.1