PubLedge v0.1.1-pre

Released: 2026-05-30
Commit: c1f51aa

Summary

Security hardening and release-readiness patch for the PubLedge prerelease line.

Verification allowlist for relationship-only instruments that preserve amendment and supersession chains without standalone obligation mappings.
Evals for MCP URL boundaries, MCP parser lockstep, verification allowlist semantics, generated-output normalization, and manifest scope coverage.

MCP fetch_by_url now accepts only canonical https://publedge.org/ URLs and root-relative canonical paths.
MCP fetch_by_url now rejects cross-origin, non-HTTPS, protocol-relative, encoded-slash, backslash, whitespace/control-character, query-string, fragment, default-port, and spoof-host URL forms.
MCP record loading now uses the shared parser/content loader instead of duplicated YAML and container parsing logic.
Generated-output comparisons normalize sitemap lastmod timestamp churn while keeping public timestamps in generated files.
CI now invokes the clean-build eval for generated docs consistency.
Manifest coverage now includes canonical source, tooling, MCP, schema, template, CI, and vendored ontology files, with docs and generated outputs excluded by policy.

npm run build: passed
npm run validate: passed
npm run evals: passed
./scripts/validate-hashes.sh: passed, 117 files checked
npm run verify: passed
Direct MCP URL PoCs: canonical absolute and root-relative paths accepted; rejected URL classes covered by eval-mcp-contract

No blocking residuals for this release. The build still emits a non-blocking recommendation that us-ut-oaip-rma-2026-001 is missing an effective date.