CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[2.10.1] - 2026-05-22

Added

• Build Pipeline Visuals: Upgraded the rollup.config.js build output with high-visibility, color-coded ANSI banners to clearly distinguish between PREMIUM and COMMUNITY build targets.

Changed

• Discovery Architecture: Deprecated and purged the legacy __TEMPO_DISCOVERY__ global discovery approach in favor of a strict TEMPO_LICENSE_KEY and Symbol-based registry pipeline.
• Security Hardening: Redacted the raw JWT key from the public Tempo.license snapshot to prevent accidental exposure of credentials in debug logs.

Fixed

• License Snapshot Resilience: Implemented a safety guard in Tempo.license to normalize raw.scopes before iteration, eliminating potential runtime exceptions when scopes are absent.
• Cross-Platform Build Stability: Updated the resolve-types.ts build script to utilize Node's native fileURLToPath for deterministic __dirname resolution across all operating systems.
• Local Dev Extensibility: Allowed LIC_SRC_DIR to be overridden via environment variables in the type resolution script, supporting customized development workflows while maintaining strict production fallbacks.

[2.10.0] - 2026-05-11

Added

• Licensing Architecture: Implemented a standalone "No-Op" licensing engine (support.license.ts) in the public core. This ensures the repository is 100% buildable and testable by the community without private dependencies.
• Automatic Premium Injection: Optimized the build pipeline (Rollup/Vitest) to automatically detect and inject the proprietary licensing engine from a side-by-side repository during official builds.
• Portable Encoding: Migrated base64Encode to the shared library for universal, environment-agnostic token handling.

Changed

• Hardened Licensing Resolution: Updated the term resolution pipeline with a dual-identity race-condition guard (JTI + Key) and a late-binding resolution guard to securely handle Pending to Revoked state transitions.
• Decoupled CI Resolution: Eliminated the need for private registries or stubs in GitHub Actions by utilizing the internal No-Op engine for standard test runs.
• Term Collision Enforcement: Term plugin registration now throws a fatal error on naming collisions (key/scope) to prevent silent configuration failures.

[2.9.3] - 2026-05-11

Added

• Generalized Fractional Resolution: Numeric inputs (Number, BigInt) now support fractional components across all units (ss, ms, us, ns) with nanosecond precision. The resolution engine now utilizes absolute BigInt math to ensure deterministic results regardless of sign.
• Hardened AliasContext Interface: Introduced a strongly-typed, chainable context (this) for functional aliases, providing API parity with the Tempo class. This includes full support for yy, mm, dd, hh, mi, ss, tz, cal, and config properties.
• ISOString Branded Type: Added a branded ISOString type for clearer representation of ZonedDateTime ISO-8601 strings, improving type safety across the library's internal and public APIs.
• Shorter Epoch Support: Numeric strings with 9-10 digits are now correctly classified as Epoch timestamps when a non-default unit (e.g., 'ss') is configured. This enables parsing of second-based timestamps like 946684800 without requiring manual padding.

Changed

• Dependency Refresh: Updated Temporal Polyfill to 0.2.1, ensuring a more stable and secure development environment.
• Unit Preference Enforcement: Consolidated numeric resolution logic in engine.composer.ts to strictly enforce configured unit preferences ('ss', 'ms', 'us', 'ns') for both Number and BigInt types.
• Lexer Prefix Reliability: Optimized and hardened the prefix() helper in engine.lexer.ts to provide faster, type-safe string transformations for weekday and month formatting.

Fixed

• State Mutation Safety: Refactored the internal parsing engine to eliminate side-effect mutations on the global configuration state during resolution. This ensures that parse() results are deterministic and do not leak transient metadata into subsequent calls.
• Priority-Based Configuration: Hardened the configuration resolution in engine.composer.ts to strictly prioritize explicit caller overrides (e.g., timeZone, calendar) over metadata derived from input objects, ensuring that methods like .toDateTime(zdt, { timeZone: 'UTC' }) always honor the provided override.
• Registry Initialization Resilience: Updated the onRegistryReset hook in tempo.class.ts to automatically re-hydrate computed snippets (e.g., tomorrow, noon) after a registry reset. This resolves matching failures in testing environments where registries are cleared between runs.
• withState Wrapper Hardening: Fixed an unwrapping bug in the withState utility that caused standalone parse() calls to return internal TypeValue wrappers instead of raw ZonedDateTime results when passed an explicit state object.
• Numeric Validation Ordering: Reordered the resolution logic in engine.composer.ts to ensure NaN and non-finite numbers are caught before type conversion, preventing native RangeError crashes.
• Parser Epoch Short-circuit: Refined the epoch detection in module.parse.ts to correctly identify all fractional numbers as timestamps, bypassing the layout engine and preventing "Unknown Term" resolution errors.
• Functional Alias Property Parity: Added missing year, month, and day aliases to the AliasContext (mapped to yy, mm, dd) to ensure compatibility with standard Tempo getters.
• Timestamp Configuration Persistence: Fixed configuration propagation by ensuring timeStamp is explicitly handled within extendState in support.init.ts for consistent state persistence across Tempo instances.
• Epoch Parsing Precedence: Implemented a short-circuit in parseLayout to prioritize epoch interpretation for large numeric inputs, preventing their misidentification as layout patterns.
• Normalizer Memory Management: Resolved state leakage in engine.normalizer.ts by ensuring alias keys are correctly cleaned up in the resolvingKeys set via try/finally blocks.
• ZonedDateTime Mutation Order: Fixed ZonedDateTime mutation ordering in module.parse.ts to ensure time zone and calendar application precedes wall-clock property updates, preventing incorrect wall-clock values during zone shifts.
• Type Safety Hardening: Eliminated DOM interface collisions in tempo.type.ts by correcting PluginContainer inheritance, improving type safety and preventing namespace pollution.
• Documentation Build Stability: Stabilized the documentation build environment by resolving peer dependency resolution errors between VitePress and markdown-it-mathjax3.

[2.9.2] - 2026-05-08

Added

• Resilient ID Extraction: Unified timeZoneId and calendarId extraction into a single spec-resilient helper getTemporalIds. This ensures 100% compatibility across both spec-final and Node.js V8 harmony environments by resolving nested property drift (timeZone.id vs timeZoneId).
• Identity-Based Layout Resolution: Hardened resolveLayoutClassificationOrder to support identity-based symbol lookups. This ensures that tokens without descriptions or aliases (such as raw symbols) can be correctly prioritized in preferred layout ordering.
• Named Capture for Separators: Updated the default {sep} snippet to use a named capture group (?<sep>...), improving the inspectability of generated regex patterns.

Changed

• Non-Recursive Bootstrap: Hardened the toNow() lifecycle and today alias to safely access local configuration without triggering circular parsing dependencies.
• Modular Decompression: Removed the redundant parse.layout.ts re-export module and consolidated all layout resolution logic into engine.layout.ts. Updated internal Specifiers and test-aliases to point to the new canonical home.
• Node.js Harmony Support: Updated documentation to highlight native Temporal support in Node.js 20+ via the --harmony-temporal flag, reducing the need for external polyfills in modern server-side environments.

Fixed

• MasterGuard Validation: Improved the MasterGuard scanner to correctly identify and reject whitespace-only strings by implementing explicit match tracking.
• Symbol Mapping Safety: Fixed a potential TypeError in AliasEngine when mapping Symbols without descriptions by hardening the wordsList creation logic.
• Utility Security Hardening: Refactored the create<T> and setPatterns utilities with robust prototype-shadowing guards. These improvements prevent TypeError crashes when interacting with null-prototype objects and guarantee PatternCompiler state isolation across concurrent Tempo instances.
• PatternCompiler Isolation: Refactored Tempo.regexp() to guarantee PatternCompiler isolation per-state, preventing unintended cache leakage across inherited registries.
• UI Accessibility: Updated documentation button styles to use theme variables, ensuring WCAG 2.1 contrast compliance (4.5:1) for all brand elements.
• RegExp Preview Accuracy: Corrected the documentation example for Tempo.regexp() to accurately reflect the anchored outer capture group and unique named snippet expansions (sep, sep_1) produced by the engine.

[2.9.1] - 2026-05-07

Fixed

• Support Utility Consolidation: Completed the rename and migration of internal support utilities to the @packages/tempo/src/support/ directory.
• Pattern Compiler isolated test state: Fixed state-leakage in pattern_compiler_optimization.test.ts by implementing TempoRuntime.createScoped() and init({}, false) within beforeEach hooks.

[2.9.0] - 2026-05-06

Added

• Centralized Alias Architecture: Finalized the migration to a unified AliasEngine. All event and period aliases are now managed through a centralized registry, providing a single source of truth across global and local contexts.
• Rich Alias Results: Alias resolution now returns a structured AliasResult object containing exhaustive metadata, including the source (global/local), type (Event/Period), and specific resolution flags.
• Hardened Clock Snapping: Standardized the resolution path for clock-like aliases (e.g. 8:00). The engine now ensures absolute sub-second precision clearing (milliseconds, microseconds, and nanoseconds) when snapping to a time-string alias.
• Optimized Lifecycle Monitoring: Implemented a version counter in the AliasEngine. Mutation operations now trigger a version increment, allowing Tempo instances to efficiently detect registry changes and rebuild internal regex patterns without expensive deep-cloning.

Changed

• Parser Context Consolidation: Extracted the "host" facade construction from the main parsing loop into a dedicated getResolutionContext helper, improving maintainability and reducing Parser complexity.
• Decoupled Term Registration: Refactored Tempo.extend and term-based alias registration to bypass legacy raw registries, while maintaining backward compatibility via a mirrored metadata view.

Fixed

• Documentation Server Stability: Resolved VitePress 404 errors by correcting the srcDir configuration and implemented srcExclude to prevent build failures from dead links in non-documentation folders.

[2.8.0] - 2026-04-30

Changed

• Release D: Immutability System Refined: Continued improvements to the immutability system. The project evaluated mutation-throwing Proxies for all immutable objects, but reverted to using Object.freeze for stability and compatibility. See plan for architectural details.

Migration

• All objects remain frozen with Object.freeze. No mutation-throwing Proxies are used for core objects. Identity checks (===) behave as before.

Added

• Parse Planner Configuration: Introduced planner.layoutOrder for parsing precedence and planner.preFilter as a replacement for the legacy parsePrefilter option.

Fixed

• MonthDay Auto-Detection: Boolean shortcuts and manual overrides for the monthDay option are properly tracked and respected over heuristics.
• Sandbox Factory Stability: Resolved an issue where sandbox-specific period alias collisions were ignored. Added collision warnings.
• Symbol Discovery Isolation: Fixed the options resolution flow so global custom formats from discovery symbols merge correctly without getting wiped.

---

[2.7.0] - 2026-04-27

Added

• Grouped Configuration Options: Consolidated monthDay and relativeTime options into nested objects.
• Internal layout detection: Added isMonthDay detection for improved regional layout resolution.
• CI Benchmarks: Added performance benchmarking suite to CI.

Fixed

• Event Overrides: Fixed $setEvents logic to correctly handle custom event overrides.
• TimeZone Fallbacks: Improved and cleaned up the IANA TimeZone fallback list.
• Intl.Locale Debugging: Enhanced diagnostic logging for locale resolution.

[2.6.0] - 2026-04-25

Added

• Standardized UTC Offsets: Added normalizeUtcOffset utility for transforming informal UTC-offset strings.
• Custom Layout Order: Added layoutOrder option to customize parsing element precedence.

Changed

• Season Scope Simplification (Breaking): Removed Chinese-specific object from term.season scope.
• Refined TimeZone Normalization: Improved UTC offset handling during initialization.

Fixed

• Layout Pattern Resolution: Fixed ordering to respect intended sequence.

[2.5.0] - 2026-04-24

Added

• Layout Order Resolver Module: Extracted layout-ordering decision logic from the Tempo class into a dedicated engine.layout module (src/engine/engine.layout.ts). This module provides deterministic functions for resolving parse layout order based on locale preference and maintains existing pair-swap semantics.
• Layout Controller Framework: Implemented a minimal controller-map infrastructure (LayoutController type, createLayoutController, resolveLayoutClassificationOrder) to enable future input-class pre-filtering and custom layout ordering without structural refactors. The framework currently has a single default classification that mirrors existing behavior.
• Debug Layout Order Visibility: Added optional debug output in Tempo.#swapLayout to emit the resolved layout order for diagnostics (when debug: true).

Changed

• Internal Layout Resolution: Refactored Tempo.#swapLayout to delegate ordering to the external resolver, improving separation of concerns and testability.
• Alias Precedence: User-defined event and period aliases now take precedence over built-in aliases when both patterns match.

Notes

• API Impact: No public API changes; layout-ordering behavior is byte-for-byte equivalent to prior releases.
• Performance: Layout resolution is still $O(n)$ where $n$ is the number of layout entries; controller infrastructure is optimized for future per-input classification without per-call overhead.
• Guidance: If needed, rename custom aliases to avoid overlap or remove the conflicting custom alias.

[2.4.0] - (Skipped)

Version 2.4.0 was not released; the project merged new functionality from 2.4.0 into 2.5.0.

[2.3.0] - 2026-04-22

Added

• Standalone Parse Support: Enhanced the ParseModule to support standalone parsing of textual dates (including names like "Jan") without requiring a bound host class instance.
• Backtracking Security: Implemented suspicious quantifier detection (Match.backtrack) in the snippet registry to prevent catastrophic backtracking and malicious regex patterns.
• Automatic Sphere Sync: The engine now automatically recalculates the config.sphere (hemisphere) state whenever the timeZone is updated in the configuration.

Changed

• Heading Hierarchy: Restructured the documentation and README headers to use a sequential H2-based hierarchy for improved accessibility and document flow.

Fixed

• Infinite Loop Protection: Added safety-valve logic to the term resolution engine to prevent infinite loops when traversing large date ranges.
• Parse Error Resilience: Hardened the resolution engine to explicitly detect and log undefined results from the parser, ensuring isValid correctly reflects the parse state and preventing silent UTC fallbacks.
• Standalone Resilience: Added optional chaining to all host class references in the term resolver to prevent TypeError in standalone contexts.
• Type-Safe Configuration: Updated the Options type to strictly isolate parse-time-only properties from runtime state.

[2.2.6] - 2026-04-20

Added

• Isomorphic Export Support: Enhanced the dist/tempo.bundle.esm.js to provide both a default export and a named { Tempo } export, ensuring the exact same import syntax works seamlessly across Node.js and browser environments.

Fixed

• JSBI Resolution: Explicitly added jsbi to all documentation import maps to resolve bare-specifier errors in @js-temporal/polyfill when running in strict browser environments.
• Documentation Formatting: Corrected orphaned script blocks and added missing headers to the Tempo.md guide for better readability.

[2.2.5] - 2026-04-20

Added

• Cross-Bundle Singleton Stability: Implemented a symbol-based brand check for TempoRuntime to ensure reliable singleton resolution even when multiple versions of the library are loaded.

Changed

• Consolidated Internal Storage: Merged redundant internal term/plugin arrays into a unified, validated pluginsDb within TempoRuntime.
• Refined Year Semantics: Normalized the year component in term templates to intelligently distinguish between relative offsets and absolute historical years.

Fixed

• Term Resolution Accuracy: Fixed a sorting bug in the yearly-cycle resolution engine.
• Documentation Integrity: Updated architecture and README guides with provided functional, complete importmap examples for browser environments.
• HTML Standards Compliance: Wrapped library demonstration and test pages in proper HTML5 skeletons.

[2.2.4] - 2026-04-19

Fixed

• Ticker Redefinition: Added safety guards to TickerModule.install to prevent TypeError: Cannot redefine property: ticker when extending an already-initialized or @Immutable class.
• Granular ESM Resolution: Bundled tslib into granular ESM distribution files to resolve browser-side "Failed to resolve module specifier" errors.
• Documentation Build: Resolved dead links in Tempo.md to ensure successful VitePress production builds.
• Verification Dashboard: Synchronized the browser verification dashboard with current build artifacts.

[2.2.3] - 2026-04-19

Added

• Dual-Bundle Strategy: Modernized the Rollup configuration to produce both a "batteries-included" ESM bundle (tempo.bundle.esm.js) and a classic IIFE bundle (tempo.bundle.js).
• Global Export Map: Added ./bundle (ESM) and ./global (IIFE) export mappings to package.json for better consumer clarity.
• Modular Parse Engine: Successfully decoupled internal parsing logic into ParseModule, enabling standalone parsing support and reducing core class complexity.
• Carousel Accessibility: Added ARIA roles, labels, and keyboard controls (Arrow keys) to the documentation carousel to improve accessibility.

Changed

• Parsing Priority: Reordered ParseEngine.result validation to ensure isTempo instances are converted to Temporal.ZonedDateTime before primitive-type validation occurs.
• Registry Error Hints: Improved module-resolution error messages to suggest cleaner import specifiers (e.g., #tempo/parse instead of #tempo/parsemodule).
• HMR Resilience: Hardened the development-mode registry workaround to prevent "read only property" errors during hot reloads.

Fixed

• Version Synchronization: Unified versions across the monorepo root, tempo, and library packages.
• Test Infrastructure: Updated vitest.workspace.ts to use the renamed temporal-polyfill.ts setup file.
• Resource Management: Fixed interval leaks in the documentation clock during unmounting and visibility changes.
• Initialization Stability: Added a sentinel guard and optimized initPromise handling to prevent redundant error logging and failed awaits during page visibility transitions.
• Mutation Engine Hardening: Corrected preserves state.options and the mutateDepth recursion guard across all instance creation paths in MutateModule.
• Fluent Chaining Fallbacks: Hardened until() and since() calls with explicit host-instance fallbacks to preserve fluent chaining when modules are missing in "catch" mode.

[2.2.2] - 2026-04-18

Fixed

• Plugin Infrastructure Preservation: Refactored the Rollup configuration to treat all library files as public entry points. This prevents critical utilities (like defineExtension) from being tree-shaken during the build process, ensuring that modular plugins can register correctly.
• API Surface Hardening: Explicitly exported all registration and utility helpers (defineModule, defineTerm, etc.) from the main entry point to guarantee their availability for third-party extensions.
• Documentation Build Stability: Updated the documentation configuration to utilize pre-compiled dist/ assets. This resolves runtime SyntaxError issues in the browser caused by the presence of modern TC39 decorators in the raw TypeScript source files.
• Decorator Transpilation: Refactored utility functions to ensure standard function declarations are used where appropriate, improving the reliability of the transpilation phase.

[2.1.2] - 2026-04-14

Added

• Slick Shorthand Engine: Finalized and stabilized the high-performance term-shorthand syntax (#namespace.modifier). Advanced temporal navigation (e.g. #qtr.>2q1) is now fully supported across .set(), .add(), .until(), and .since().
• Inclusive Range Shifters: Introduced >= and <= modifiers to the "Slick" engine. These shifters are strictly inclusive, allowing the current term to be matched if it contains the cursor, providing a deterministic "current or next" resolution pattern.
• Advanced Terminology Docs: Published a comprehensive documentation suite (doc/tempo.advanced_term.html) detailing lexer constraints, modifier priority, and bifurcated resolution logic for high-performance term cycles.

Changed

• Boundary Performance: Optimized the term resolution loop to utilize BigInt nanosecond comparisons for all shifter logic (>, <, next, prev), ensuring deterministic behavior across complex fiscal and calendar boundaries.
• Fail-Fast Constructor: Hardened the constructor guard to explicitly throw an Error when term-based mutation keys (#) are detected. This replaces the previous silent "invalid instance" return, ensuring developers catch improper syntax immediately.
• Config Merge Priority: Refactored Tempo.#setConfig to read from persistent storage before applying provided options, ensuring that stored values are not unintentionally overwritten by transient defaults.
• Centralized Patterns: Integrated the numeric string detection regex into the central Match registry in tempo.default.ts, removing hardcoded duplicates from the mutation module.

Fixed

• Infinite Loop Resolution: Resolved a critical regression where shorthand modifiers were leaking into range-keys, triggering infinite recursion during term mutation.
• Hemisphere Inference: Fixed an initialization bug in Tempo.init() where the sphere configuration could be incorrectly overwritten or ignored during system-timezone evaluation.
• Shorthand Lexer Safety: Hardened the lexer to strictly enforce Range-Key constraints (no reserved characters or leading digits), eliminating collisions between direction modifiers and repeat counts.
• Zone-Shift Visibility: Fixed a bug in .set() where relative term resolution was ignoring timeZone or calendar overrides passed in the same mutation object. The engine now shifts context before resolving terms.
• Numeric String Mutations: Corrected a logic error that misidentified numeric-looking strings (e.g. "2") as term keywords; these are now correctly handled as numeric offsets.
• Documentation Integrity: Consolidated fragmented shorthand guides, fixed conflicting CDN links in import-map examples, and corrected the description of Tempo.init() to accurately reflect prototype persistence.

[2.1.1] - 2026-04-12

Added

• Constructor Protection: Implemented a strict guard against passing term-based mutation objects (#) directly to the Tempo constructor. The engine now explicitly rejects these inputs and directs users to the appropriate .set() or .add() methods for instance transformation.
• Unified Term Errors: Centralized term-resolution error logic into a shared static helper, ensuring consistent "Helpful Hint" messaging for missing plugins across the constructor, mutation engine, and parser.

Changed

• Modular Hardening: Hardened the core engine to strictly enforce ZonedDateTime types for all internal states. This prevents "Ghost Date" leaks and silent fallbacks to "Today" when input resolution fails in Core mode.
• Singular Path Refactor: Standardized all internal and external paths, directories, and documentation to use the singular plugin and term form (e.g., #tempo/plugin, @magmacomputing/tempo/term).
• Auto-Lazy Precision: Refined the "Zero-Cost" auto-lazy trigger to only fire for String inputs, ensuring that malformed Objects fail-fast during construction rather than deferring failures.
• Bulk Extension DX: Rebuilt Tempo.extend() with intelligent rest-parameter support and restored high-level type overloads for improved IDE autocompletion and type-safety.

Fixed

• Build Stability: Resolved type errors in the test suite (specifically tempo_guard.test.ts) that were triggering failures during project-referenced builds (tsc -b).
• Sync Normalization: Fixed a regression where early-resolving inputs (like ISO strings) were bypassing final timezone and calendar normalization.

---

[2.1.0] - 2026-04-11

Added

• TimeZone Offset Support: Formally verified and documented support for +HH:MM and -HH:MM ISO-8601 fixed-offset strings in the timeZone configuration.
• Browser Reference Map: Included a comprehensive importmap.json in the package root to provide a standard mapping for bare module specifiers in browser environments.

Changed

• Modular Import Refactor: Cleaned up the public API by removing the required plugin/ component from sub-path imports. Plugins are now accessible directly via @magmacomputing/tempo/ticker, @magmacomputing/tempo/duration, etc.
• Configuration Mode: Refactored the lazy: boolean option into a more semantic mode: 'auto' | 'strict' | 'defer' setting, offering better control over the Zero-Cost Constructor hydration strategy.
• Export Alignment: Synchronized package.json exports with the recommended import-map and documentation snippets to ensure 1:1 parity between Node.js and Browser environments.

Fixed

• Documentation Clarity: Updated all markdown guides (Ticker, Terms, Layout, etc.) to use verified import patterns and corrected various outdated configuration references.

---

[2.0.1] - 2026-04-03

Added

• Ticker Stability Guard: Implemented a 10,000-iteration safety break in resolveTermShift to prevent infinite loops when resolving malformed or non-advancing custom terms.
• Unified Diagnostics (Logify): Integrated the Logify utility into core internal classes for standardized debug, catch, and silent mode support.

Changed

• High-Precision Ticker: Migrated TickerPlugin from Date.now() to instant().epochMilliseconds, ensuring consistent use of high-precision timing without legacy Date object dependencies.
• Test Performance: Standardized the test suite on vitest --pool=forks to ensure deterministic execution of asynchronous ticker and generator tests.

Fixed

• Ticker Async Stability: Resolved hangs in async generators (for await...of) by implementing a Pledge-based waiter resolution mechanism that guarantees immediate termination upon stop(), return(), or throw().
• Ticker Pulse Synchronization: Corrected pulse counts for both listeners and generators ($N$ pulses for limit: N); ensured limit: 0 is strictly honored as zero pulses.
• Ticker Cold-Start: Fixed an issue where tickers created without an initial callback would remain idle even after listeners were attached; extracted #bootstrap() to ensure the scheduler starts correctly on the first listener registration.
• Parsing Engine Optimization: Refactored Tempo.#setPatterns to optimize pattern generation and avoid redundant global guard rebuilds, significantly improving performance for local/one-off parser instances.
• Local Layout Stability: Fixed a bug where custom layout literals in local instances were being destroyed during state synchronization.
• Registry Protection: Hardened registryUpdate to safely handle non-proxied or missing targets, preventing potential crashes during late-import plugin registration.
• Term Plugin Resolution: Corrected package export mappings for term-based plugins in package.json, resolving module resolution errors in development and test environments.
• Numeric Word Parsing: Fixed regressions in numeric word resolution (e.g., "eleven days hence") by ensuring registry synchronization during late-import scenarios.

---

[2.0.0] - 2026-03-30

Added

• Zero-Cost Constructor: Optimized the instantiation path to $O(1)$ by deferring all parsing and property registration until the first property access.
• Generic Lazy Delegator: Introduced getLazyDelegator in proxy.library.ts to standardize on-demand property discovery for fmt and term objects.
• Improved Immutability: Enhanced @Immutable and secure() protections that safely handle lazy evaluation on frozen instances via a defensive prototype-shadowing fallback.
• Registry Security: Refactored global registries (FORMAT, NUMBER, TIMEZONE) to use registryUpdate with core protection, preventing accidental overrides of built-in tokens.
• Anchor-Aware Parsing: Added native support for anchoring relative date strings (e.g., "next Friday") to a specific reference date via the anchor option.
• Timezone Safety: Implemented graceful fallback to UTC (with a warning) for invalid IANA TimeZone IDs when catch: true is enabled.

Changed

• Internal State Management: Migrated from a static #pending accumulator to an instance-local #matches buffer, guaranteeing thread-safety for concurrent Tempo instances.
• Temporal Integration: Unified the Temporal polyfill location to #library/temporal.polyfill.js.
• Typing Refactor: Relocated Internal and Tempo namespaces to the top of tempo.class.ts for improved IDE type visibility and lint performance.

Fixed

• Resolved 299/299 regressions in the core and plugin test suites.
• Fixed TypeError: [object Object] is not extensible during lazy discovery on secured instances.
• Fixed relative calculation drift where "one Wednesday ago" used the system clock instead of the provided anchor.
• Fixed a race condition in TickerPlugin that caused double-clicks on initialization.