You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Catalog refreshes now prune up to 16 retired generations per workspace after a one-hour grace
period, including unchanged refreshes. Current generations and unexpired query references are
protected. Auxiliary retirement metadata preserves index schema 3 compatibility, including
replacements/reactivations by older publishers through database triggers. Existing inactive
generations receive a fresh grace period. The known pre-release schema 4 layout is recovered
without dropping catalog data; unknown future schemas remain rejected. Durable receipts remain.
Query snapshot writes now atomically prune up to 64 expired result sets and their items across
catalog, workspace search, data queries, and record pagination. Existing expiry cleanup was
never invoked in production. Unexpired cursors and durable memory remain intact; freed SQLite
pages are reusable without automatically shrinking the database file.
Windows Runner now rejects direct Python .py executable references during preparation,
instead of failing later at process start. MCP errors explain the Python interpreter,
argument template, and working directory required for correct registration.
The repo-memory skill now explains registered execution: Python scripts use a verified
interpreter in executable_ref and the script path/arguments in argv_template, with the
working directory checked before execution and existing approval gates preserved.
The bundled repo-memory skill now retains verified reusable changes before completion and
explains write recovery. It skips already-retained content, merges revision/topic conflicts,
creates successors for kind/schema or topic identity changes, and reads back uncertain writes
before retrying. Time warnings do not trigger retries; permission denials are not bypassed.
Memo title and summary validation now counts Unicode characters, matching the published schema.
Oversize discovery fields and combined record text/reference budgets report the offending
field or budget, observed length, and maximum instead of a generic limit error.
Host fact service and path lists now follow their separate schema limits, including Unicode
character lengths. Record write and report import size failures identify the relevant input
and its limit.