Zayden-Jung/Endoleap
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

test(canvas): verify retry deadlines across wall-clock shifts and recovery

Browse Source
This commit is contained in:
Codex Bot
2026-11-11 18:13:43 +08:00
parent 24c4592060
commit b34dc6089a
2 changed files with 69 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
headless/SERVICE_ACCEPTANCE.md
+24 -12
View File
@@ -1,21 +1,27 @@
# Foundry service integration evidence
Status: step 5 service scope audit completed; overall progress is 5/7.
This does not complete migration/delivery,
the complete Draft acceptance matrix, main integration or production deployment.
Status: steps 5 (service) and 6 (migration/delivery) completed; overall progress is 6/7.
The complete Draft acceptance matrix, main integration and production deployment
are not complete.
## Verified revisions and environment
- Endoleap consumer: `26da326c18bdf5363c646dff87756590b29433ea`.
- Foundry: `3268c57bc64cb85f9de80d5e04107d963ede963a`.
- Current delivered Endoleap consumer: `24c45920602378d52a42cda7e8ec2840864c8dbd`.
- Current Foundry: `5db2bf3c98f2627139cbb6d47afefa686b4c6547`.
- [Foundry CI #1182](https://gitea.entroia.com/Zayden-Jung/foundry-core/actions/runs/1182):
job 1279 completed successfully, all seven steps successful, pinned to the
current delivered consumer. Its report has all document/resource/AI and
migration flags true, `aiExecutionCount: 3`, and 75 transport calls.
Same-commit PR CI #1183/job 1280 was still running at this audit.
- [Foundry CI #1180](https://gitea.entroia.com/Zayden-Jung/foundry-core/actions/runs/1180)
and [PR CI #1181](https://gitea.entroia.com/Zayden-Jung/foundry-core/actions/runs/1181):
completed successfully; jobs 1277/1278, all seven steps successful. The original
service scope audit also passed CI #1178 and #1179.
completed successfully for consumer `26da326` and Foundry `3268c57`;
jobs 1277/1278, all seven steps successful. The original service scope audit
also passed CI #1178 and #1179.
- Existing `ces-control` runner executes Go checks/build, schema migration and
isolated PostgreSQL integration, then the pinned Node 24 consumer and HTTP smoke
checks. No local backend build or Docker execution was used.
- Local frontend: 800 Node tests and full TypeScript checking passed. Tests use
- Local frontend: 802 Node tests and full TypeScript checking passed. Tests use
the source modules; packaged SDK and application delivery remain separate gates.
## What the checks actually prove
@@ -92,8 +98,13 @@ webpack and Turbopack application regressions each passed 51 checks; the migrati
entry adds five scenarios and three lock-lifetime unit tests. Unknown
receipt/error states remain read-only with an export action. Unsupported Web
Locks prevents upgrading, while existing legacy editing remains available when
there is no pending migration. Stage 6 and the final requirement matrix still
require their delivery audit; passing these checks alone does not complete them.
there is no pending migration. The stage 6 audit also inspected source/package
exports, peer dependencies and documentation targets, then passed the actual
267-file unpacked package's Node/types, framework-peer, compiled browser storage
and Worker checks. Together with CI #1182 and both browser bundlers this closes
stage 6. The full requirement matrix remains stage 7; the two new scheduler
clock-shift checks cover backward/forward wall time, dependency/unknown claims,
stale timer callbacks and remaining wait calculation after recovery.
`canvas_headless_worker_integration_test.go` supplies deterministic generation
output over the actual worker HTTP protocol. Admission, claim, events, canonical
@@ -110,6 +121,7 @@ including subtests; that count is not 154 independent end-to-end scenarios.
The service audit covers the original stage requirements: target incremental and
idempotent protocols, frontend/runtime/resource adapters, explicit legacy
compatibility, identity mapping, source-version/permission/run admission barriers,
and rollback after writes have begun. Migration/delivery and the final requirement
matrix remain. A green feature-branch run does not merge or deploy
and rollback after writes have begun. Migration/delivery now has the separate
browser/package evidence above; the final requirement matrix remains. A green
feature-branch run does not merge or deploy
either repository. Foundry PR #19 remains open and Draft.