docs(investigations): retry-serial #676 smoke-test — static path + HOLD rationale - #680
Merged
Merged
Conversation
…LD rationale Dispatch #98vo07 primary (smoke-test retry path #676). Delivers static path analysis (3 config guards + seam data-flow with exact line refs), the trigger conditions (including the non-deterministic timeout-under-parallelism), the rationale for why a runtime smoke-test is HOLD pre-tag (régén HOLD + non-determinism), the deterministic coverage via RetryAsync unit tests (companion PR #678), and a post-tag runtime validation plan (capture [HARVEST-RETRY] logs at next release regen). Signal, not a verdict — po-2023 reports metrics, ai-01 verdicts runtime. Refs #613. Companion to #676 (merged) and #678 (RetryAsync unit tests). Co-Authored-By: Claude-Code <noreply@anthropic.com>
jsboige
added a commit
that referenced
this pull request
Jul 4, 2026
… review entry) (#688) Dispatch lev5ct secondary (jsboige wants to verify ALL docs before tagging). One index → one link + one "à vérifier" line per doc, so the whole release documentation can be eyeball-reviewed in a single pass. Grouped in 9 sections: - §1 TAG GATE: RELEASE-VALIDATION-v0.9.0.md (v4 fresh, 80 PDFs, verdicts #140/#632) - §2 Release notes: consolidated #659 (paste-ready) + CHANGELOG gap flag - §3 CMYK (PdfCmykPostProcess README + GDrive CMYK_COLOR_PROOF note) - §4 Pipeline resilience (retry smoke #680) - §5 DNN i18n / go-live (#669 mechanism, #681 schema export, #662 coverage) - §6 Coverage audits (Rules #661, polish sweep #667, taxonomy coherence, scanner-fp #642, prod hygiene) - §7 Mindmaps/OWL (#499 Phase2 confirm, FR-frozen mechanism, OWL EN+FR-only scope) - §8 Polish/misc (#654 mnemonics, #629 CardPen, #415 repo, #141 crossLink) - §9 Stale framework docs flagged (64-PDF superseded — NOT tag-gate) Key flags surfaced for jsboige: - CHANGELOG.md is the single biggest gap — predates bundle v3 entirely (no CMYK/80-PDF/P&P Standard/Light/Ghostscript/deadlock/logger). Needs an update pass before tag. - 5 framework docs still assert "64 PDFs" (superseded by dossier v4) — flagged to avoid cold-read confusion, none is the tag-gate. - OWL scope = EN+FR only (not 8-lang) — release notes must reflect this honest scoping. All paths verified on master 7590dfb (post cycle-3 batch merges). Co-authored-by: Claude-Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Delivers the smoke-test investigation for the retry-serial fix #676 (issue #613 Option C), per dispatch #98vo07 primary. Closes the primary item with a static path analysis + HOLD rationale + post-tag validation plan.
Why a doc, not a runtime run
The retry path fires only when (1)
ContinueOnHarvestSetFailure=true, (2)HarvestSetRetryAttempts>0, and (3) at least one set actually failed in the parallel loop. Condition (3) is non-deterministic (depends on a real timeout under parallelism) — a clean run fires zero retries, proving nothing about the retry path itself. Forcing a deterministic timeout requires either a full release regen (HOLD until tag) or a synthetic-timeout harness (out of smoke-test scope). The doc is the honest deliverable pre-tag.Contents
ContinueOnHarvestSetFailureL45,HarvestSetRetryAttemptsL55,HarvestSetRetryBackoffSecondsL62) + the seamHarvestImagesL88–L128 with exact line refs.ContainsKeyguard inProcessLocalizedHarvest), so the retry re-renders from scratch; successful sets keep their key → skipped.RetryAsyncunit tests, green) covering the retry/backoff contract.[HARVEST-RETRY]logs at the next release regen; metrics to report (sets entering retry, recovered, residual, timing).Scope
Pure documentation (
.md), no code/runtime/2sxc/DNN surface — not subject to the #596 runtime-pending gate. Companion to #678 (RetryAsync unit tests) and #676 (the merged fix).🤖 Generated with Claude Code