Changelog
All notable changes to VhyxSeal packages. Most recent release first.
1.0.0-rc.1
2026-05-26LatestAdded
- Complete semantic contract layer for web UI components
@vhyxseal/coreโ zero-dependency foundation with contract schema, inference engine, security layer, manifest generator, relationship/capability registries, action tokens, key management@vhyxseal/reactโ React 18+ adapter with SealProvider,withAgentContractHOC,useContract/useCapability/useAgentActionhooks@vhyxseal/vueโ Vue 3 adapter with VhyxSealPlugin and composables@vhyxseal/vanillaโ Web Components adapter (SealButton, SealInput, SealForm, SealNav, SealDisplay, SealConfirmation)@vhyxseal/nextjsโ Next.js integration withvhyxsealPlugin(),handleManifestRoute(),handleDashboardRoute()@vhyxseal/devtoolsโ Development panel and contract overlay@vhyxseal/cliโ CLI tools: simulate, verify, audit, init@vhyxseal/testingโ Test utilities: matchers and drift detection@vhyxseal/styleโ CSS design tokens for VhyxSeal tooling- HMAC-SHA256 manifest signing with key management
- Single-use action tokens with 6-step verification
- Domain verification with HMAC-signed tokens
- Injection detection across 14 pattern categories
- DevTools audit dashboard at
/__agent__/dashboard.json - Chrome DevTools extension (Manifest V3)
- RFC-0001 open for community comment
Security
- Default agent policy is deny (
allowedAgents: []) - Timing-safe HMAC comparison throughout
crypto.randomBytesfor all token generation
Known Limitations
- Rate limit enforcement: schema defined,
AgentPolicy.rateLimitsmiddleware pending (1.1.0) - Registry backend: local only, hosted registry planned for future release
- Multi-framework contract inheritance: planned โ cross-framework registry not yet available
VhyxSeal follows semantic versioning. Within a major version, changes are additive only โ fields are never removed or renamed. Breaking changes require a major version bump and the RFC process with a 12-month migration window. See RFC-0001 ยง7 Versioning Commitment for the full policy.