v0.1.18

New Features

• Support a local, uncommitted .agents/agents.local.md for user-specific agent instructions (#713)
• Lazy MemorySpool plus a faster spool load path: managing dataframes are built only when needed, directory reads go straight through the file's FiberIO, and merges stream into a pre-allocated array — much faster reading/merging of many (hundreds of) files with ~45% lower peak merge memory (#738)
• Lazily import matplotlib and scipy.signal so import dascore is faster and lighter (#740)

Bug Fixes

• Fix stable-docs GitHub Pages deploy (bump deploy-pages v4 → v5) (#714)
• Show the latest released version (not a dev version) in manually triggered stable-docs builds (#715)
• Fix NumPy 2.5 / Python 3.14 datetime64/timedelta64 unit and overflow failures (#716)
• Correct Patch.stalta docstring parameters and document the dimension keyword API (#717)
• Interpret value-bound selection on descending coordinates by coordinate value, not storage order (#719)
• Forward extra specplot keyword arguments to the underlying waterfall call (#727)
• Raise a clear CoordError when specplot is called on a non-2D spectral patch (#728)
• Use absolute coordinate spacing for kurtosis and raise on uneven/invalid coordinate steps (#730)
• Reject STA/LTA window tuples where the long-term window is not larger than the short-term window (#731)
• Fall back gracefully when the Pint disk cache is stale during import (#732)
• Load the correct DASDAE FileSpool patch when patch groups share coordinate extents but differ in attrs (#736)
• Fix assorted regression edge cases in aggregation, normalize, mute, decimation, integration, chunking, and moving windows (#737)
• Warn and skip unloadable FiberIO entry points, raise clearer filter/specplot errors, and standardize the kurtosis dim keyword (#742)

Breaking Changes

• #742 changes Patch.kurtosis to the standard dim keyword signature, which may affect callers relying on the previous parameter names.

Not included: #733 (Add DASDAE compression options) was reverted by #744 before this release, so no net user-facing change. The replacement compression API is expected via the storage-API work (#734).