Files
OpenMAIC/app
wyucandClaude Fable 5 8cc8845a2c feat(document): derived assets with lineage and an extraction cache (#1153 part 1) (#1164)
* feat(document): cache extraction as derived pool assets with lineage (#1153 part 1)

* fix(document): harden the extraction cache keys and write path (#1153 part 1)

* fix(document): bound alias trust and unblock the extract path from cache writes (#1153 part 1)

* fix(document): keep every extraction-cache failure inside the degrade-to-miss net (#1153 part 1)

Move the lookup's key construction (config fingerprinting included) inside
its guarded region so a fingerprint failure degrades to a cache miss instead
of rejecting the caller's extraction; guard the page-side dedupe fingerprint
the same way (falls back to un-deduped extraction). Pin the remaining review
coverage: malformed/missing createdAt treated stale, the documented
future-dated residual, fingerprint-throw degradation on lookup/write/dedupe,
and supersede leaving the superseded record's assets untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(document): keep server-only extractor implementations out of the client bundle (#1153 part 1)

* fix(document): fall back to the localized message for non-JSON extraction responses (#1153 part 1)

A proxy error page (or any non-JSON body) on either the error or the success
read now surfaces parseFailedMessage instead of a raw SyntaxError, making the
docblock's fallback promise universal. Review nit from #1164.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-24 15:08:08 +08:00
..