From e13e60c365f00fceae0bc1510bd2838e9150395e Mon Sep 17 00:00:00 2001 From: DevBehindYou Date: Thu, 29 Oct 2026 16:41:17 +0530 Subject: [PATCH] Record verified Excel and assembly memory release --- docs/LLMISER_EXCEL_ASSEMBLY_MEMORY.md | 16 ++++++++++++---- docs/LLMISER_OPTIMIZATION_PLAN.md | 8 ++++---- docs/START_HERE.md | 10 +++++----- docs/ai-handover/HANDOVER.md | 10 +++++----- docs/ai-handover/PROGRESS.md | 15 ++++++++------- 5 files changed, 34 insertions(+), 25 deletions(-) diff --git a/docs/LLMISER_EXCEL_ASSEMBLY_MEMORY.md b/docs/LLMISER_EXCEL_ASSEMBLY_MEMORY.md index 76e0d96..e334df6 100644 --- a/docs/LLMISER_EXCEL_ASSEMBLY_MEMORY.md +++ b/docs/LLMISER_EXCEL_ASSEMBLY_MEMORY.md @@ -1,6 +1,6 @@ # Excel and final-result memory -Updated 29 October 2026. Candidate implementation on `codex/excel-assembly-memory`; production release is not yet claimed. This follows the released [CSV capacity work](LLMISER_PARSER_CAPACITY.md). +Updated 29 October 2026. Released in [PR #15](https://github.com/DevBehindYou/LLMiser/pull/15) at runtime revision `3db41140521d5cfb1bb3bfd12865feca5a8cc95b`. This follows the released [CSV capacity work](LLMISER_PARSER_CAPACITY.md). Later documentation-only commits do not change this verified source snapshot. ## Changes and fidelity @@ -56,8 +56,16 @@ Local MarkItDown 0.1.9 suites: 144 normal tests and 101 archive tests passed, wi MarkItDown 0.1.8 passed all 24 Excel/count checks. With the original local 0.1.7 installation, 13 fallback/count/integrity checks passed and 11 deliberately disabled adapter cases skipped. Small generated authenticated multipart probes passed before release: three workbooks on each normal worker and a ZIP containing all three on each archive worker (eight requests total). All four reported MarkItDown 0.1.9; complete expected tables and word counts matched. These direct probes created no Storage jobs. -Local OCR validation initially lacked `pytesseract`; a no-dependency copy of 0.3.13 was installed only in the ignored audit folder. The full Windows suite then recorded 69 passes, eight orientation skips and one readiness failure claiming the configured binary was unavailable. Isolated readiness and a real text-image conversion both passed with the installed Tesseract 5.4.0. The suite failure remains recorded rather than hidden by weakening assertions. Linux/Python 3.12 OCR CI is required before merge; production Render uses Tesseract 5.5.0. +Local OCR validation initially lacked `pytesseract`; a no-dependency copy of 0.3.13 was installed only in the ignored audit folder. The full Windows suite then recorded 69 passes, eight orientation skips and one readiness failure claiming the configured binary was unavailable. Isolated readiness and a real text-image conversion both passed with the installed Tesseract 5.4.0. The suite failure remains recorded; assertions were not weakened. Linux/Python 3.12 OCR CI passed before merge and again on merged main. Production Render reports Tesseract 5.5.0, `eng` and `osd`. -Before release, the actual public frontend transport also passed generated XLSX and three-workbook ZIP conversions through create/upload/start/advance, Storage downloads and fresh-link retrieval. The single document output and all three ZIP objects downloaded successfully; table bytes, declared object lengths, final Unicode markers and exact recovered Markdown passed. This created two real jobs under normal retention. It validates the preceding production behavior; repeat after deployment to validate the candidate's Storage path. +Before release, the actual public frontend transport also passed generated XLSX and three-workbook ZIP conversions through create/upload/start/advance, Storage downloads and fresh-link retrieval. The single document output and all three ZIP objects downloaded successfully; table bytes, declared object lengths, final Unicode markers and exact recovered Markdown passed. This created two real jobs under normal retention and supplied the baseline for the post-release comparisons below. -CI, deployment and post-release checks are still pending. Do not treat local checks as production release evidence. No blogs/visuals, database schema, retention policy, queue/concurrency settings, supported formats or limits change in this slice. Native parser peaks, retained archive entries, whole-result normalization/serialization, concurrent requests and real Storage/network buffers remain separate boundaries. +PR #15 and merged main passed all seven CI jobs, including 261 frontend tests, normal/OCR/archive regressions, PostgreSQL, edge and extension checks. All six production Vercel status contexts succeeded. A first health sample overlapped rollout and saw three document workers still without the new revision field; after rollout, all six N1/N2/Z1/Z2/O1/O2 health responses reported exactly `3db41140521d5cfb1bb3bfd12865feca5a8cc95b`, with ready responses. Render therefore picked up the shared counting code too. + +Post-release generated acceptance on 29 October: + +- Eight authenticated multipart workbook/ZIP requests passed on all four document workers, still using MarkItDown 0.1.9. Complete Markdown hashes, character counts, word counts and engines matched the pre-release observations exactly. These requests created no Storage jobs. +- The actual public frontend transport passed generated XLSX and ZIP create/upload/start/advance, all four output-object downloads and fresh-link recovery. The document and combined ZIP Markdown hashes/counts matched before release; the project index hash matched too. Manifests had the same shape/length and three nodes, with different per-job IDs as expected. Before/after Storage tests created four real jobs in total, subject to existing retention; no cleanup was manually invoked. +- All 20 public-page/discovery/health and path/query-preserving 308 redirect checks passed. An uncached wake returned normal/OCR/archive each 2/2 ready. Existing legacy API/unknown-path behavior was unchanged; no new de-indexing action was needed. + +No blogs/visuals, database schema, retention policy, queue/concurrency settings, supported formats or limits changed. This acceptance used small generated workbooks and does not certify maximum-size/concurrent production capacity. Native parser peaks, retained archive entries, whole-result normalization/serialization, real HTTP buffers, native browser input and representative devices remain separate boundaries. Live OCR-image/scanned-PDF/admin/cleanup execution was outside this slice. Raw operator evidence, logs and private probes remain ignored in `project-docs/excel-audit/`; no signed URLs or credentials are published. diff --git a/docs/LLMISER_OPTIMIZATION_PLAN.md b/docs/LLMISER_OPTIMIZATION_PLAN.md index 8590445..ea15a0b 100644 --- a/docs/LLMISER_OPTIMIZATION_PLAN.md +++ b/docs/LLMISER_OPTIMIZATION_PLAN.md @@ -1,10 +1,10 @@ # LLMiser optimization continuation -Updated 28 October 2026. Work only in LLMiser. This is the current continuation map; copied MDify analysis is historical evidence and proposals, not live deployment instructions. Blog rebranding is complete and blog sources/visuals are outside this implementation slice. +Updated 29 October 2026. Work only in LLMiser. This is the current continuation map; copied MDify analysis is historical evidence and proposals, not live deployment instructions. Blog rebranding is complete and blog sources/visuals are outside this implementation slice. ## Current continuation state -PRs #1–#13 are merged. Retained-result recovery, cron cutover, wake coalescing, shared reader statistics, large-preview control and CSV allocation reduction are released; the old frontend is now the static LLMiser fallback and public migration redirects remain live. The 22 October branch/review statements below are historical evidence for that earlier slice, not current release blockers. Use [START_HERE](START_HERE.md) and [PROGRESS](ai-handover/PROGRESS.md) for deployment state. +PRs #1–#15 are merged. Retained-result recovery, cron cutover, wake coalescing, shared reader statistics, large-preview control, CSV allocation reduction and Excel/final-result memory changes are released; the old frontend remains the static LLMiser fallback and public migration redirects remain live. The 22 October branch/review statements below are historical evidence for that earlier slice, not current release blockers. Use [START_HERE](START_HERE.md) and [PROGRESS](ai-handover/PROGRESS.md) for deployment state. Shared reader statistics shipped in PR #9 at `84e510db62ea41f31c131771eb7d32b5e92515f4`: one allocation-bounded helper, one memoized result for reader line/status displays, preserved counting semantics and reproducible before/after measurements. See [reader statistics](LLMISER_READER_STATISTICS.md) for 259-test CI and live verification. Browser profiling follows below; the rest of the queue remains separate. No new production SQL or service retirement was part of this slice. @@ -14,7 +14,7 @@ PR #13 released [a source capacity audit and CSV allocation reduction](LLMISER_P ## Verified starting point -Current implementation: [Excel and final-result assembly memory](LLMISER_EXCEL_ASSEMBLY_MEMORY.md), branch `codex/excel-assembly-memory`. Sequential sheet processing, exact bounded word counts and delayed archive output encoding are under measurement/validation. Keep production status separate until the release checks finish. +Released [Excel and final-result assembly memory](LLMISER_EXCEL_ASSEMBLY_MEMORY.md), PR #15 at `3db41140521d5cfb1bb3bfd12865feca5a8cc95b`: sequential sheet processing, exact bounded word counts and delayed archive output encoding. Three fresh-process trials per mode preserve complete hashes; local peak reductions are qualified by timing variability/XLS regression. All seven CI jobs passed before/after merge; six production Vercel statuses succeeded; all six N/O/Z workers report the exact revision and readiness. Eight generated multipart probes, two production Storage conversion/recovery checks and 20 HTTP checks passed; all pools are 2/2 ready. No SQL, concurrency, retention or blog changes. The copied source already contains atomic job startup/finalization, cleanup recovery, upload/active-job/storage-reservation admission, shared archive container checks, bounded PDF page uploads/OCR preparation, lazy Markdown/highlighter loading and current-edit export snapshots. Do not reimplement these based on old “proposed” checklist rows. Their deployment/capacity evidence is distinct from source tests. @@ -44,7 +44,7 @@ Acceptance: expired link, later-part failure, complete Unicode assembly, restart | Work | Next bounded change / dependency | | --- | --- | | Shared statistics and large previews | Counting released in PR #9; browser profiling and large-preview control released in PR #11; measure native input/devices before deeper editor/worker changes | -| Backend parser capacity | Source audit and synchronized CSV memory slice released in PR #13. Next measure workbook/native and response/merge memory; preserve fidelity before tuning concurrency | +| Backend parser capacity | CSV released in PR #13; Excel/final-result memory released in PR #15 with production XLSX/ZIP Storage acceptance. Profile native/concurrent parsing and whole-result normalization/serialization on representative hosts before queue tuning | | Shared deadline | Add an optional, backward-compatible remaining-budget protocol, reserving finalization time; test slow failures/cold starts | | Controller detail pagination | Top-level lists already paginate; bound files/tree/events/work-items with stable cursors and truthful totals; query-plan evidence before new indexes | | Replay-stable object identities | Fence attempt-specific writes before deterministic IDs; SQL attempt guards alone do not prevent a stale Storage overwrite; additive rollout for new roots only | diff --git a/docs/START_HERE.md b/docs/START_HERE.md index d2ec417..4014ecf 100644 --- a/docs/START_HERE.md +++ b/docs/START_HERE.md @@ -1,18 +1,18 @@ # LLMiser — start here -Updated 28 October 2026. **LLMiser is the sole working repository and the source for future releases.** Do not depend on an MDify or MDify-Pro checkout: the owner plans to delete those repositories. +Updated 29 October 2026. **LLMiser is the sole working repository and the source for future releases.** Do not depend on an MDify or MDify-Pro checkout: the owner plans to delete those repositories. ## Current state -The app is live at https://llmiser.devbehindyou.com. PRs #1–#13 are merged; the latest verified runtime change is revision `165d2b01ce8e30dfa09d32292ac911264f18e60d`. PR #13 passed all seven CI jobs, including the 261-test frontend suite; all six production Vercel deployment statuses succeeded. Generated live CSV/ZIP probes passed on all four document workers, and 20 public HTTP checks passed. An initial OCR wake check returned 0/2; direct readiness and a subsequent uncached wake check confirmed all three pools 2/2 ready. See [parser-capacity release evidence](LLMISER_PARSER_CAPACITY.md), [large previews](LLMISER_LARGE_PREVIEWS.md), [reader statistics](LLMISER_READER_STATISTICS.md) and [retirement evidence](LLMISER_LEGACY_RETIREMENT.md). +The app is live at https://llmiser.devbehindyou.com. PRs #1–#15 are merged; the latest verified runtime revision is `3db41140521d5cfb1bb3bfd12865feca5a8cc95b` from PR #15. All seven CI jobs passed before and after merge, including 261 frontend tests; all six production Vercel statuses succeeded. Every N/O/Z worker reports that exact revision and readiness. Eight generated workbook/ZIP multipart checks, two Storage-backed conversion/recovery checks and 20 public HTTP/redirect checks passed after release; all pools are 2/2 ready. See [Excel/assembly release evidence](LLMISER_EXCEL_ASSEMBLY_MEMORY.md), [CSV capacity](LLMISER_PARSER_CAPACITY.md), [large previews](LLMISER_LARGE_PREVIEWS.md) and [retirement evidence](LLMISER_LEGACY_RETIREMENT.md). The full app supports English (US), German, Japanese, Spanish, Russian and Simplified Chinese. The browser remembers the interface language; documents are not translated and OCR languages are unchanged. Blogs remain English. Eight articles, eight banners and forty figures are complete. The Chrome extension source is merged, but native acceptance and store publication remain pending. -Released [large-preview control](LLMISER_LARGE_PREVIEWS.md) pauses automatic formatting above 50,000 characters while retaining complete raw text and exports. Full formatting is available on request. Local/generated browser checks cover editing, document switching and exact full downloads; representative-device/native textarea profiling and the backend parser-capacity audit remain next boundaries. The six interface dictionaries now contain 631 messages each. +Released [large-preview control](LLMISER_LARGE_PREVIEWS.md) pauses automatic formatting above 50,000 characters while retaining complete raw text and exports. Full formatting is available on request. Local/generated browser checks cover editing, document switching and exact full downloads; representative-device/native textarea profiling and deeper native/concurrent parser measurements remain next boundaries. The six interface dictionaries now contain 631 messages each. -Released [parser capacity and CSV memory reduction](LLMISER_PARSER_CAPACITY.md) preserves verified upstream CSV output while reducing retained row allocations in both document pools. The audit distinguishes source limits, local generated measurements and live multipart acceptance. No concurrency increase follows from the benchmark. Workbook/native parser and final response/merge memory remain the next backend investigation. +Released [parser capacity and CSV memory reduction](LLMISER_PARSER_CAPACITY.md) preserves verified upstream CSV output while reducing retained row allocations in both document pools. The audit distinguishes source limits, local generated measurements and live multipart acceptance. Neither it nor the subsequent workbook work justifies a concurrency increase. -Current candidate: [Excel and final-result memory](LLMISER_EXCEL_ASSEMBLY_MEMORY.md) is being measured on `codex/excel-assembly-memory`. It processes workbook sheets sequentially, bounds temporary word-count allocations and defers ZIP output encoding to the existing upload workers. The runtime revision above remains the last verified release until CI/deployment and live checks are recorded. +Released [Excel and final-result memory](LLMISER_EXCEL_ASSEMBLY_MEMORY.md) processes workbook sheets sequentially, bounds temporary word-count allocations and defers ZIP output encoding to the existing upload workers. Local untraced peaks fell about 2% for XLSX, 5% for XLS, 15% for ZIP assembly and 17% for profile finalization, with identical output; timing varies and the XLS median regressed. Production output/recovery equivalence passed. Native/concurrent parser peaks, full normalization/serialization, representative-device input behavior and the shared-deadline queue remain separate work. ## Legacy frontend replacement is deployed diff --git a/docs/ai-handover/HANDOVER.md b/docs/ai-handover/HANDOVER.md index 21e6017..d402e7b 100644 --- a/docs/ai-handover/HANDOVER.md +++ b/docs/ai-handover/HANDOVER.md @@ -1,10 +1,10 @@ # LLMiser AI handover -Updated 28 October 2026. Start with [START_HERE](../START_HERE.md). This replaces the earlier deployment-phase handover; historical evidence remains in the linked reports and Git history. +Updated 29 October 2026. Start with [START_HERE](../START_HERE.md). This replaces the earlier deployment-phase handover; historical evidence remains in the linked reports and Git history. ## What the owner wants now -LLMiser must remain independently maintainable after MDify and MDify-Pro are deleted. Update the documentation, preserve necessary private materials and replace the old frontend converter with a minimal LLMiser-only fallback. The owner explicitly chose **immediate permanent redirects on the old public hosts**, with the banner only as fallback. Repository deletion itself is not being executed in this task. +The owner selected Excel conversion and final-result assembly memory optimization after the retirement handover. That slice is now released in PR #15; use its evidence and the remaining optimization queue below. LLMiser must also remain independently maintainable after MDify and MDify-Pro are deleted. Keep immediate permanent redirects on the old public hosts and the minimal LLMiser-only fallback; repository/service deletion is not being executed here. ## Work already shipped @@ -16,7 +16,7 @@ LLMiser must remain independently maintainable after MDify and MDify-Pro are del - Product-focused README with screenshots, recorded language demo, steps, format limits and measured-versus-unmeasured keyword notes. - Chrome extension 0.2.0 source: one Converter toolbar popup, file picker/drop, manual Paste into detected AI sites, uploaded-job recovery. No public store release or completed native acceptance is claimed. -PRs #1–#13 merged. Latest verified runtime revision: `165d2b01ce8e30dfa09d32292ac911264f18e60d`. [PR #13](https://github.com/DevBehindYou/LLMiser/pull/13) shipped CSV allocation reduction after all seven CI jobs passed, including the 261-test frontend suite. All six production Vercel statuses succeeded; generated multipart CSV/ZIP probes passed on N1/N2/Z1/Z2, and a fresh 20-check HTTP audit passed. OCR initially returned 0/2 in the bounded wake check; direct readiness and a later uncached wake confirmed all pools 2/2. See [parser release evidence](../LLMISER_PARSER_CAPACITY.md), [large previews](../LLMISER_LARGE_PREVIEWS.md), [shared statistics](../LLMISER_READER_STATISTICS.md) and [retirement acceptance](../LLMISER_LEGACY_RETIREMENT.md). +PRs #1–#15 merged. Latest verified runtime revision: `3db41140521d5cfb1bb3bfd12865feca5a8cc95b`. [PR #15](https://github.com/DevBehindYou/LLMiser/pull/15) released Excel/assembly memory changes after all seven CI jobs passed, including 261 frontend tests and Linux OCR. Main CI passed all seven again. All six production Vercel statuses succeeded, and every N/O/Z worker reported the same revision and readiness. Eight generated multipart workbook/ZIP checks, two production Storage conversion/recovery checks and 20 HTTP/redirect checks passed; all pools were 2/2 ready. See [Excel/assembly evidence](../LLMISER_EXCEL_ASSEMBLY_MEMORY.md), [CSV capacity](../LLMISER_PARSER_CAPACITY.md), [large previews](../LLMISER_LARGE_PREVIEWS.md) and [retirement acceptance](../LLMISER_LEGACY_RETIREMENT.md). ## Repository and private-material boundaries @@ -54,13 +54,13 @@ Active local tooling now has zero absolute references to either old checkout. LL ## Verification commands -Active optimization: [Excel and final-result memory](../LLMISER_EXCEL_ASSEMBLY_MEMORY.md), branch `codex/excel-assembly-memory`. Read that report before changing Excel adapters, word counting or archive writes. Current candidate validation is distinct from the deployed CSV release. Preserve the verified-version fallback, upstream per-sheet formatting, complete results and preflight-before-write behavior; no concurrency increase is authorized by local memory measurements. +Released optimization: [Excel and final-result memory](../LLMISER_EXCEL_ASSEMBLY_MEMORY.md), PR #15 at 3db4114. N/Z Excel adapters use verified MarkItDown 0.1.8/0.1.9, the same per-sheet pandas/HTML formatting, sequential frame release and XLS on-demand sheet unloading. Shared 64 Ki-character word counting preserves Python whitespace/token semantics across N/O/Z. Archive writes retain text/byte counts and encode within the existing four upload workers after full preflight. Preserve unknown-version/image-hook fallback, complete results and preflight-before-write behavior. Local measurements are not hosting/concurrency guarantees; the small production Storage fixtures do not establish large-job capacity. The owner asked to continue the optimization plan after the retirement handover. PR #8 completed that handover; PR #9 released [shared reader statistics](../LLMISER_READER_STATISTICS.md). PR #11 released [large-preview control and reproducible browser profiling](../LLMISER_LARGE_PREVIEWS.md): above 50,000 UTF-16 characters, formatting waits for an explicit request. Editing/document switching resets the request; complete raw text/copy/exports remain available. All six packs contain 631 messages. Local evidence: 261 full tests, final 20 focused tests, lint/consistency checks and production build passed; generated browser fixtures verify full rendering, edit re-pause, identical-text document switching, manual pause and exact current-edit download. CI passed all seven jobs, production deployed revision 0501cd0, the 20-check HTTP audit passed, and normal/OCR/archive were each 2/2 ready. No fresh production conversion/admin/cleanup acceptance is implied by that audit. PR #13 released [a parser-capacity audit and bounded CSV memory reduction](../LLMISER_PARSER_CAPACITY.md) at 165d2b0. N/Z use identical `app/csv_converter.py` modules, outside the three-pool shared `common/` package so OCR gains no MarkItDown dependency. Enable only on verified upstream 0.1.8/0.1.9; unknown versions/missing helper retain the original converter. Never expand the version allowlist without output-equivalence tests. Generated before/after hashes match, including synchronized conversions; queue limits and all other parsers stay unchanged. Local suites passed 118 normal/98 archive tests, 25 tests on 0.1.8, and the expected 0.1.7 fallback checks. CI/deployment and post-release generated multipart probes passed. These direct worker probes created no Storage jobs and do not replace browser/Storage-backed acceptance. -Next investigate native textarea/input behavior and representative devices before workers/editor virtualization, or measure XLSX/native parser and response/merge memory from [the optimization queue](../LLMISER_OPTIMIZATION_PLAN.md). Do not repeat the shipped preview work, silently truncate source/exports, or mistake local parser measurements/multipart probes for Storage-backed acceptance. The optimization plan's 22 October unmerged-branch statements are historical. +Next investigate native textarea/input behavior and representative devices before editor virtualization, profile native/concurrent parser and normalization/serialization peaks, or take the shared-deadline item from [the optimization queue](../LLMISER_OPTIMIZATION_PLAN.md). Do not repeat released Excel/preview changes or truncate outputs. The 29 October generated XLSX/ZIP acceptance includes actual production Storage downloads/recovery; scanned-PDF, live OCR-image, authenticated admin and cleanup execution were outside that acceptance. The optimization plan's 22 October unmerged-branch statements are historical. Use Node.js 22. From `frontend`: diff --git a/docs/ai-handover/PROGRESS.md b/docs/ai-handover/PROGRESS.md index ba47bef..2ba0661 100644 --- a/docs/ai-handover/PROGRESS.md +++ b/docs/ai-handover/PROGRESS.md @@ -1,6 +1,6 @@ # LLMiser progress and remaining work -Updated 28 October 2026. This is the current tracker. Earlier phase-specific numbers remain in their reports; they are not the current deployment state. +Updated 29 October 2026. This is the current tracker. Earlier phase-specific numbers remain in their reports; they are not the current deployment state. ## Completed and released @@ -15,14 +15,15 @@ Updated 28 October 2026. This is the current tracker. Earlier phase-specific num | Six-language web app | PR #5 released; English US, German, Japanese, Spanish, Russian, Simplified Chinese; now 631 messages each after PR #11 | | Final display-label fixes | PR #6 merged/deployed; preview labels/tooltips, mobile theme and retention labels | | Public README | Screenshots, recorded demo, steps, formats, profiles, privacy and FAQs; separate keyword evidence | -| Final frontend CI | PR #13: 261 tests passed; lint, dictionaries, SQL/blog consistency and production build passed | +| Final frontend CI | PR #15 and merged main: 261 tests passed; lint, dictionaries, SQL/blog consistency and production build passed | | Other CI | Backend N/O/Z, PostgreSQL, edge and extension jobs passed | -| Production deployment | Latest runtime change `165d2b01ce8e30dfa09d32292ac911264f18e60d`; all six Vercel statuses successful, including the legacy static shell | +| Production deployment | Latest runtime change `3db41140521d5cfb1bb3bfd12865feca5a8cc95b`; all six Vercel statuses successful; exact revision/readiness confirmed on N1/N2/Z1/Z2/O1/O2 | | Shared reader statistics | PR #9 merged/deployed; allocation-bounded counting and shared reader line/status metrics; preserved count semantics; synthetic benchmark and limits documented | | Large-preview control | PR #11 merged/deployed; generated browser profiling, explicit formatting above 50,000 characters, complete raw/copy/download acceptance, six-language notices | | CSV parser memory | PR #13 merged/deployed; verified-version output preservation in N/Z, synchronized generated measurements, and successful pre/post-release multipart CSV/ZIP probes on all four document workers | -| Production HTTP audit | 40 passing checks during the integrated release; all 13 sitemap pages; permanent legacy redirects; API noindex/auth boundary | -| Backend readiness | Normal/OCR/archive each 2/2 ready after final release | +| Excel and final-result memory | PR #15 merged/deployed; sequential sheets, exact bounded word counts and bounded output encoding; generated multipart and actual Storage/download/recovery acceptance passed | +| Production HTTP audit | 29 October: 20 public-page/discovery/health and permanent-redirect checks passed; documented legacy API routing unchanged | +| Backend readiness | 29 October: all six workers report the released revision and ready; uncached public wake shows normal/OCR/archive each 2/2 | | Browser acceptance | All six languages, persistence, English-only blogs, translated policy/controller login; German 390px viewport had no horizontal overflow | | Search migration | Google accepted Change of Address and canonical sitemap on 21 October; ongoing recrawl/indexing monitoring remains open | @@ -49,7 +50,7 @@ See [release record](../LLMISER_RELEASE_2026-10-26.md), [localization](../LLMISE ## Remaining work -In progress: [Excel conversion and final-result assembly memory](../LLMISER_EXCEL_ASSEMBLY_MEMORY.md), explicitly selected by the owner. Candidate code/tests are on `codex/excel-assembly-memory`; repeated measurements, compatibility checks and release evidence are pending. The shipped-state table above still describes the preceding release. +Released: [Excel conversion and final-result assembly memory](../LLMISER_EXCEL_ASSEMBLY_MEMORY.md), explicitly selected by the owner, PR #15 at 3db4114. Local suites: 144 normal/101 archive tests; installed-version checks passed. All seven Linux CI jobs and six Vercel production statuses passed, with exact revision/readiness verified on all six workers including Render. Eight post-release generated multipart probes and two Storage-backed XLSX/ZIP conversions passed, including all four output objects and exact saved-result recovery. Before/after Markdown, counts and index hashes match; manifest job IDs correctly differ. All 20 HTTP checks passed and all pools were 2/2 ready. Four real jobs across before/after tests follow normal retention; cleanup execution itself was not tested. Local Windows OCR readiness-suite failure is preserved in the report; Linux OCR CI passed. The owner resumed the implementation plan after the handover was merged in PR #8. [Shared reader statistics](../LLMISER_READER_STATISTICS.md) shipped in PR #9. [Large-preview control](../LLMISER_LARGE_PREVIEWS.md) shipped in PR #11 at 0501cd0 after 261 frontend CI tests/all seven jobs passed. All six production deployments succeeded; the 28 October 20-check HTTP audit passed and all three pools were 2/2 ready. Actual-component generated browser measurements and exact raw/download acceptance support the preview boundary. Representative-device/native textarea profiling and deeper parser-capacity work remain separate. @@ -61,7 +62,7 @@ The owner resumed the implementation plan after the handover was merged in PR #8 - Audit provider Git connections and all consumers before retiring old backend services or deleting their source repositories. Do not delete shared data, bucket, Vault entries, cleanup functions or compatibility contracts. - Complete native Chrome 0.2.0 acceptance and store publication; source merge does not publish the extension. - Native-language review and broader device testing remain useful; UI localization does not expand OCR languages. -- A new full production upload/scanned-PDF/admin/actual-cleanup acceptance run was not part of the 26 October release. Prior generated-file conversion checks remain dated evidence. +- The 29 October slice freshly accepted generated XLSX/ZIP production uploads, all output downloads and recovery. Scanned-PDF/live OCR-image/admin/actual-cleanup acceptance was outside this slice; prior evidence for those remains dated. - Continue Search Console/Bing monitoring and old-domain redirect retention. Do not claim Google has completely replaced old results without current evidence. ## Blog maintenance