Retired: Harper-backed Tantivy Directory mapping

[kylebernhardy]

Outcome

This custom Directory is no longer part of the delivery architecture.

Acceptance criteria

• Do not continue custom KV file mapping, host-storage transport, chunk reclamation, or RocksDB durability optimization for fulltext release.
• Preserve existing commits and benchmark evidence as history; they do not qualify the native Harper integration.
• Track removal of hosted exports and implementation under the native-only packaging and integration epics.
• Use native Tantivy MmapDirectory and the generic native checkpoint publication work instead.

Closed as not planned because the storage requirement changed, not because the original Directory release criteria were met.

Design

Native Tantivy storage and Harper derived indexes. Native Tantivy files are the only delivery target for standalone use and Harper. Proposed APIs and integration gates are not claims of completed implementation.

Comment generated by kAIle (GPT-6)

[kylebernhardy]

Use fixed chunks for Harper-backed Tantivy files #23 implements the first storage-format slice:

• binding format v2 with directly addressed 256 KiB chunks and immutable tail revisions;
• atomic tail-and-binding publication with retry-safe chunk staging;
• range reads proportional to intersecting chunks rather than file history;
• full-chunk, chunk-to-chunk, and chunk-to-tail coverage through the host transport and RocksDB lease; and
• explicit response-budget validation and per-operation transport admission.

The PR does not close this issue. Remaining release work includes benchmark qualification of the chunk size and small-read retention behavior, bounded crash-recoverable orphan reclamation, production factory input bounds, and multi-chunk crash/reopen coverage.

Comment generated by kAIle (GPT-5)