Skip to content

Add real published Waterline entry-refusal and selected-run repair acceptance - #192

Merged
rmcdaniel merged 5 commits into
mainfrom
test/221-waterline-entry-recovery
Oct 22, 2026
Merged

rmcdaniel merged 5 commits into
mainfrom
test/221-waterline-entry-recovery

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Refs durable-workflow/.github#221 and durable-workflow/waterline#229.

Add the retained installed-package entry-recovery fixture and extend its two required-signature cases with actual Waterline interaction. The browser displays the replay refusal, invokes selected-run Repair and lets compatible code complete the same original with unchanged input, history prefix and exact deadlines. No API or UI response is mocked.

API, viewer and browser readiness precede business admission. Normal PyPI wheel hashes are checked before and after execution. The independent stopped-state audit opens a disposable read-only copy and preserves source database bytes. The earlier five-original HTTP cohort remains historical evidence; this GUI extension is a separate two-original cohort.

Actual qualification: published Waterline 2.12.1 initially hid Server's entry diagnostic, so that browser original failed and remains unrepaired. With exact Waterline frontend 685dfa84, fresh desktop/dark and mobile/light originals pass visible refusal and selected-run Repair; both same originals complete and independent cold readers preserve int64/null/Unicode. Stopped SQL agrees on 3 tasks / 13 events / 2 explicit repairs, original 30-second run / 60-second execution deadlines and six Worker exits 0. This qualifies the frontend component, not a newly published Waterline image. Full receipt: durable-workflow/.github#221, comment 6329444127.

The initial missing-ensurepip setup failed before business; the corrected normal installation passes. All phase runtimes, dependencies, data/raw/browser captures and task image pulls were removed at 00:10:53 UTC, ahead of 00:30. Only pushed source remains. No SDK implementation, package version/release, native/shared/frozen or Cloud change.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel marked this pull request as ready for review October 22, 2026 00:37
@rmcdaniel
rmcdaniel merged commit 81d8686 into main Oct 22, 2026
17 checks passed
@rmcdaniel
rmcdaniel deleted the test/221-waterline-entry-recovery branch October 22, 2026 01:24
@rmcdaniel

Copy link
Copy Markdown
Member Author

Merged normally as 81d8686877a3325a02f1eebd3cef090b0062885c at 01:24:02 UTC. The merged whole tree f5892f641524c0e00688a63bae495afd0d71a6b1 exactly matches qualified candidate d1d61572.

All candidate checks pass, including Python 3.10/3.11/3.12, corpus, lint, package, actual integration and final target-branch qualification. Sonar workflow/app pass, with a direct API review showing zero OPEN/CONFIRMED findings. CodeQL and boundary/policy checks pass. The merged remote head is removed.

The fixture's two actual candidate-asset Waterline originals and stopped audit remain scoped to their recorded tuple. This merge changes no SDK runtime or package version and does not complete shared #221: Waterline #229, its compatible publication and actual installed-image acceptance remain pending. Earlier failed source lint and published-UI observations remain recorded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants