Repository navigation
feat(bpmn): deliver direct and embedded production hosting - #3410
elsa-workflows-codex[bot] wants to merge 251 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Specification review complete — spec1017 Reviewed specification head: Two bounded specification-review iterations, with independent correctness, standards and acceptance reviewers. Iteration 1 ( The reviewed spec requires actual pipeline cancellation/remaining-work disposition across admission/result races, truthful already-terminal results, actual pre-writer native/BPMN captures and upgraded-host/Studio proof. The user-selected first-delivery recipient snapshot remains required. Author structural/link checks pass; documentation-only changes need no behavioral test run. Next: Spec Kit implementation plan and concrete contracts/qualification sequence, independent plan review, then reviewed tasks. These are specification reviews only, zero complete-PR implementation review rounds have run. No runtime behavior or #2898/#2907 acceptance is claimed, and this draft must not merge on documentation-only green checks. |
|
Ordered planning checkpoint Specification review is clean across all three independent lenses at Draft tasks are pushed at No production writer/schema has changed. First implementation action after task review/cross-artifact analysis: the portable actual-host baseline capture runner, then actual parked checkpoints. First observable production milestone: genuine direct start/wait/resume and partial fork/join restart through the shared authority. Real ETL/parent settlement and existing Studio upgrade evidence remain required before #2898 closes. Complete-PR implementation review rounds: zero; no runtime or full-program acceptance claimed. |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 39189012 | Triggered | Generic High Entropy Secret | 72b13f4 | specs/1017-direct-bpmn-hosting/evidence/baseline/manifest.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
T001 verified; actual pre-writer capture underway Current head T001 is complete: the portable capture runner parks real normally published/executed legacy partial forks and uses exact owned-process identity plus consistent whole-store snapshots. Committed actual receipt and manifest retain eight actual held executions, Balanced/Durable × legacy root/Sequence/Flowchart/CompensationScope. BranchA is durably completed by the normal Event command and branchB remains held. Executing source is438001406d980051584234e5d656eb8e6a67f47f, not relabeled as a later docs/tooling head. Nine inspected writer/host binaries share that source; three released library binaries are recorded separately. Both whole-store backups and frozen authoring verify. Twelve mechanical/capture-control tests pass, including four mutations of copies of the actual bundle; originals still verify. Metadata-reader build passes. The initial tooling-local variable collision and macOS canonical-path ownership refusal were fixed before successful qualification; no runtime state was fabricated. Only the explicit owned baseline host was briefly stopped/resumed; the user's hosts and owned Studio remain running. T002 remains open: capture affected pending callback, recipient/cohort/rearm, called-control/MI/compensation and actual Studio boundaries before editing their writers. No production source under Essentials/src or ETL/src and no schema has changed from verified main. This bundle is actual old-writer capture, not new direct hosting or upgraded-host recovery proof. #2898/#2907 and the full program remain open; next implementation action is the remaining T002 capture matrix, then T003–T013 shared foundations. No new issue, competing claim or merge of this incomplete draft. |
|
#2898 / PR3410 continuation: actual pre-writer capture is progressing; Gate A remains open.
The portable matrix is being assembled, not yet accepted. T002 remains unchecked. Upgraded-host recovery, genuine direct hosting, RunBpmn and real ETL bridge/retry acceptance remain unproved. Full-PR review rounds remain zero. Project62 stays In Progress / Partial; no production acceptance is closed. |
|
Gate A / T002 is captured and verified at
Portable bundle, manifest, verification. The specific pre-writer barrier is satisfied for this map. No affected production runtime/ETL writer or schema changed. Direct hosting, RunBpmn, real ETL/retry/settlement, changed-host recovery and final Studio/runtime acceptance remain unproved. Full-PR review rounds 0; draft3410 is not merge-ready. Keep #2898/#2907/#2892 open; #3242 native fault projection and Orleans/task-runner deferrals remain unchanged. Project62 remains In Progress / Partial. |
|
T004 is complete; T005 model-material contracts are started at The new integration-tier project launches the real built Workbench in an owned temporary content root, publishes and runs a native workflow through normal authenticated APIs, kills only its own process, restarts against the same isolated stores and verifies the persisted execution/pin. Its build metadata supports The first shared Core contracts add a versioned semantic protocol, opaque model material, complete dependency pins, declared input/output contracts and a physical material-incarnation snapshot. No native root is fabricated. Existing artifact providers/decorators default-refuse the additive model operations and preserve cancellation; none advertises model material yet. Native constructors/serialization remain unchanged, with 42 tracked public API additions. Verification: 62 targeted runtime/material/native artifact/hash/cache/start tests pass, 0 skipped; the owned-host test passes; generated solution-filter check passes; tier discovery confirms 123 projects each in one tier/shard, with exactly one child-process integration entry for the new suite. Host fixture, material contracts. T005 remains unchecked: model-state/input/lifecycle/checkpoint and dispatch contracts still follow, then the actual provider/driver implementation. No schema or persisted execution writer changed, no model storage/admission is enabled, and this native restart is not direct-model or upgraded-version recovery acceptance. The verified Gate A inputs remain unchanged. Full-PR review rounds 0; draft3410 and #2898/#2907/program acceptance remain open. Project62 stays In Progress / Partial. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
1 similar comment
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
blocked: review loop exhausted Complete-PR self-review round 6 complete — NOT CLEAN Reviewed exact head
Independent acceptance verification passes28 portable checks,7842 asset references/157 archive members,16 immutable stores and16 inspected screenshots. Standards independently passes399 manifest references/50 distinct snapshot integrity checks and all raw discovery/TRX method reconciliation. The earlier source04c eight-suite6928/0skip and source9c frontend116/0skip positives retain their exact sources; they do not prove these newly demonstrated failure cases.104 frozen assets remain unchanged. The full reports and portable evidence are committed at |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
1 similar comment
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: both round6 corrections are implemented and pushed in
Six original regressions fail then pass; an additional later-reached timer case fails when only the durable-fault guard is removed and passes after byte-exact restoration. Initial import/clock-range setup failures remain diagnostic. The whole BPMN suite passes499/499, zero skips, at this committed source. The hosting project compiles; actual unchanged source9c pending-input cold-host qualification is next, including normal start/wait/restart/resume/complete and further process loss. Controls and original input. Six full rounds completed, none clean; no seventh round or merge. T041/T043/T044 remain open pending affected qualification. Existing API/version-magnitude/needs:decision, deferred GitGuardian39189012, required checks/protected/post-main gates and broader program acceptance remain open. Existing Codex claim/PR retained; #2898/#2907/#2908/#2892 stay open/Partial; all existing deferrals unchanged. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: actual old-input recovery and the direct user journey pass at The original impossible timer now has an inspectable revision1 Faulted result ( A fresh impossible publication refuses422. A normal one-hour human/timer definition starts, waits, survives SIGKILL, resumes through its supported exact human command and completes. It survives another SIGKILL/restart; the original fault and receipt remain identical. Three owned process exits are137; three closed Runtime stores and source-bound product/API observations are retained for import after the ongoing whole suite finishes. No SQL state/queue/claim/receipt/authority edit. This proves selected SQLite direct-host recovery, not Studio/ETL/other-provider acceptance. Exact normal execution: The12 public binary API comparisons also pass at this source with resolved references/no suppressions. Whole BPMN499/0skip remains atdaac77da4, with production/unit code unchanged by2191's test expectation correction. The full42-case standard-host suite is running against frozen2191 products; no product builds/changes occur during it. These checks do not authorize the unresolved version magnitude. Six full reviews completed, none clean; the owner review-route card is pending, and no seventh review or merge has started. T041/T043/T044, existing owner API magnitude/needs:decision, deferred GitGuardian39189012, exact required CI/protected/post-main and broader program gates remain open. #2898/#2907/#2908/#2892 remain open/Partial; existing deferrals unchanged. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: both round6 repairs are verified and their portable evidence is pushed in Whole BPMN: 499/499 at daac77d; whole standard-host: 42/42 at2191e3710; focused original timer recovery: 1/1 at2191e3710; zero failures/skips in these completed runs. Discovery method sets reconcile exactly with both whole-suite TRX files. The test-only2191 correction leaves production/BPMN unit sources unchanged fromdaac. Failed development/setup/mutation controls retain their distinct results. The actual source9c accepted timer input now commits an inspectable Faulted outcome and original accepted receipt, retaining its exact pin/incarnation and settling its input/work/outbox. Fresh impossible publication refuses422. A normal direct model starts, waits, survives SIGKILL, resumes via its supported human command, completes and survives another SIGKILL/restart. Three owned exits137 and three closed Runtime stores are retained for both the focused test and whole-suite repeat. Four prior actual old-fault cuts also pass again. No SQL authority/state edits. This is selected SQLite direct-host proof; broader Studio/ETL/provider acceptance retains its own scope. All12 public binary API comparisons pass, resolved references/no suppressions, and actual host product hashes are unchanged across the run. Shape does not settle the existing owner magnitude decision. Remote main is now dec598d (#3498, Identity/login and Studio presentation). These completed2191 runs remain bound to their source. Next: adopt that legitimate main progress, reconcile publish-state76d0132, and qualify the affected Identity/Studio saved-authoring journey. T041/T043/T044 remain open until that work and gate reconciliation finish. Six full reviews completed, none clean. Both adopted P2 findings are repaired; no seventh round or merge has started, and the existing owner review-route card is pending. Existing API magnitude/needs:decision, deferred GitGuardian39189012, exact required CI/protected/post-main and broader program gates remain open. #2898/#2907/#2908/#2892 remain open/Partial, deferrals unchanged. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
2 similar comments
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: legitimate main dec598d (#3498 Linen/branding/login) is integrated cleanly in existing PR3410 at At this integrated source, whole frontend 4012/4012 across307 files, affected appearance/account browser suite 121/121, no skips/retries, whole Identity 532/532, zero skips, supported typecheck/lint and production frontend build pass. Three package scripts with no test files are recorded separately, not counted as tests. Whole Studio/architecture and the actual original accepted-input restart case are continuing sequentially; fresh two-family actual saved-store Studio qualification follows frozen product builds. These pending checks are not green claims. All104 frozen baseline assets match. The adoption changes no execution-model/runtime/BPMN test code. All12 previously audited public package baselines are identical at publish-state76d0132. The completed repair qualification retains its original sources: BPMN499 atdaac, whole host42 and focused actual old-input/direct restart journey1 at2191, zero skips, API12 pass. No relabelling as current-source/full Studio/provider acceptance. T041/T043/T044 remain open for affected current-source qualification/reconciliation. Six full reviews completed, none clean; both P2 repairs are verified, but the existing owner review-route card is pending before any seventh round. Existing owner magnitude/needs:decision, deferred GitGuardian39189012, exact required CI/protected/post-main and wider program gates remain open. #2898/#2907/#2908/#2892 remain open/Partial; existing deferrals unchanged. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: round6 repairs and current-main compatibility qualification are complete; portable evidence is pushed at At source4dc: whole frontend4012/307 files, affected browser121/no retries, Identity532, Studio645, architecture594, actual old-input/direct restart host1 and unchanged Studio controls13 all pass, zero skips. Three no-test-file package scripts are separate. Typecheck/lint/production frontend build/maps/tier/docs/workflow checks pass. Discovery accounts for every Identity/Studio method (532/638 descriptors;645 Studio executions include theory expansion). All12 public binary API comparisons pass with resolved references/no suppressions; all audited baseline versions remain unchanged at publish-state76d0132. The normal runtime-only Workbench resumes the unchanged source9c accepted timer input into a visible durable fault, preserving its full pin/incarnation/accepted receipt and settling its input/work/outbox. New impossible publication refuses422. A normal direct start/wait/SIGKILL/restart/supported human resume/complete journey and further SIGKILL/restart pass; three closed Runtime stores retained. Both P2 implementations are in daac77d;2191 changes only the host test's correct409 terminal cancellation expectation. Both actual saved Studio families also pass at4dc: exact initial JSON/XML/layout exports, label-only edits, reviewed3.0.0/4.0.0 publication, four completed new runs with distinct Published Run/Test Run identities, exact API views captured before restart and unchanged afterward, nine original saved-run observations,12 coherent whole stores and12 visually inspected screenshots. Host products are byte-identical before/after; all owned processes stopped. All104 frozen baseline assets match. Setup/launcher diagnostics are explicitly distinct from the final qualified runs. Existing Studio compatibility is proved; #2907 first-class direct-model Studio is not claimed. Earlier BPMN499 atdaac and whole host42 at2191 retain their sources; execution code/tests are unchanged during main adoption. Source04c Runtime/Design/Dispatch/ETL suites retain their unchanged scopes. This does not convert shared-provider probes into non-SQLite upgraded-host proof or complete wider ETL acceptance. T041/T043 are verified. T042 owner magnitude and T044/spec preparation remain open. Six full reviews completed, none clean. The existing review-route card is still pending before any seventh round; no seventh review or merge started. Existing needs:decision/API version, deferred GitGuardian39189012, exact required CI/protected/resulting-main and broader program gates remain open. The4dc hosted checks had no failures but were queued/running, with skipped/neutral checks distinguished; the new evidence head starts fresh checks and is not called green. Retained Codex claim6461197535, existing draft PR3410 and deferrals unchanged. #2898/#2907/#2908/#2892 remain open/In Progress/Partial. No program completion claim. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
1 similar comment
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: current qualification at8504fbac/source4dc remains complete within its recorded scope. While hosted checks run and the existing owner review-route/version decisions remain pending, the unchanged committed frozen-v1 ETL/native upgrade acceptance is now running against8504. It creates an actual b555bd8 old-writer pending native/ETL run, crashes the worker after physical JSONL output but before acceptance, then asks the current worker/native consumer to resume the same owned stores/pins with Design offline. No new implementation leaf, production-source change, abstraction or seventh review. The existing runner keeps raw databases/diagnostics private and qualifies same-machine/same-path recovery. A result is not yet claimed. Wider SQL/RabbitMQ/continuous ETL, Workbench/Studio and program acceptance remain separate. Parent2907/2908 readiness summaries now point to the actual six-round state; their acceptance criteria remain open. Existing claim6461197535, draft PR3410, needs:decision, deferred scan and protected/exact-head delivery gates remain unchanged. |
|
checkpoint: actual frozen-v1 ETL/native upgrade acceptance passes on Fresh old writer All three databases pass integrity before and after. ETL Runtime applies the expected1-to9 additive migration chain. Successor working tree/diff are empty; all baseline production/build inputs outside the narrow test-harness adapter remain unchanged. Actual SDK10.0.402, Python3.14.9. Initial system Python3.9.6 stopped before producer execution because the runner requires3.11+; that setup failure remains distinct from the fresh supported-runtime pass. Reproduce at source8504 with an installed Python3.11+ (this run used3.14): python3.14 Extensions/Etl/tests/Shared/test-v1-native-upgrade.py --evidence-root /absolute/new/private-directoryPublic runner SHA256 Scope: one finite file partition, native Sequence and SQLite, same machine/path. This is a real old-writer/current worker-native upgrade witness; it does not prove Workbench/HTTP/Studio upgrade, other providers, continuous/SQL/RabbitMQ processing, arbitrary relocation or stronger external-effect guarantees. Wider #2908 acceptance remains open. Hosted Linux/Windows backend-source and generated-map checks pass on8504; broader PR/integration/EF shards remain queued/running and Full-tier draft skips remain skips. Existing claim6461197535/draft PR3410, six reviews/none clean, pending owner review-route/version decisions, deferred GitGuardian39189012 and exact required CI/protected/resulting-main gates remain unchanged. No seventh review, new implementation leaf or production-source change. #2898/#2907/#2908/#2892 remain open/Partial. |
|
@elsa-workflows-codex[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
checkpoint: primary hosted CI passes on exact remote head8504fbac779941eeef51c1ccdc1a36a07fceee88. CI41160195245 is completed/success: Build & test, all three PR shards, core-only build/test, architecture guards, plan and generated-map freshness. Backend source41160195158 also completed/success for Linux and Windows. Full run41160195267 remains in progress: all seven integration/EF container shards are live. No failure is reported in the current head check readback. Skipped/neutral checks retain those statuses; this is not a full-tier or all-checks-green claim. Actual frozen-v1 ETL/native upgrade remains producer1/1/current consumer1/1 at8504, with its explicit SQLite/native/same-path limits. Existing direct host/legacy/Studio repair qualifications retain their executing sources. Two documentation-only edits are prepared locally to update the canonical overview and link that ETL receipt; they are not pushed while these runs finish. No production-source change or competing implementation leaf. Six full reviews completed, none clean; existing owner review-route/version decisions and deferred GitGuardian39189012 remain pending. No seventh round or merge; retained claim6461197535 and draft PR3410 remain unchanged. Protected/exact-head/resulting-main and broader program gates remain open/Partial. |
[Codex] On behalf of @sfmskywalker.
Problem and result
BPMN needs its own recoverable execution identity while preserving native composition, authored material and saved executions. This implements direct hosting on the existing mailbox, ownership and atomic checkpoint authority with released BPMN0.5.0, supported human/incident APIs, exact delivery-time broadcast cohorts, timers, bounded retry and RunBpmn/RunEtl bindings.
Immediate completion returns to the original native parent on its first decision. Retired publications preserve exact accepted-start replay while refusing fresh admission and conflicts. A final semantic fault retains its interpreter result while remaining committed native work receives a durable cancellation or positive retirement disposition; actual old fault checkpoints recover without reviving progression. Legacy native bindings and corrupt owned commands fail deliberately with contextual domain errors. Design retains historical migrations and recognizes the existing cumulative writer without rewriting physical history. Native composite fault policy is unchanged.
Related issue and acceptance
Fixes #2898; program #2892/spec1017; retained Codex claim6461197535. FR/SC and five-criterion evidence index. #2907/#2908 and program production acceptance remain open.
The source-bound index covers released semantics/compatibility, direct restart and races, real finite ETL outcomes/cancellation, supported operations/native composition and declared limits. Actual embedded ETL-origin cancellation is now proved through all four native parent shapes, alongside the prior inverse cancellation order and pending-return/ACK journeys.
Current repair qualification
8504fba evidence, products4dc/main dec598d: frontend4012/browser121/Identity532/Studio645/architecture594/actual host1/controls13/API12 pass; both saved Studio families,4 new runs/12 stores, exact restart views. T041/T043 verified.6 reviews,none clean; owner route/version/scan/CI/merge gates open. #3410 (comment) Original failure reports and prior qualification retain their sources below. Both repairs and affected main compatibility are verified; owner review route and delivery gates remain open.
Additional bounded ETL upgrade: existing frozen-v1 producer1/current consumer1 pass at8504, zero skips, for a real effect-before-acceptance interruption and persisted native Sequence continuation over SQLite with Design offline. Scope, reproducible command and limits. No production-source change or new implementation leaf. Wider ETL/Workbench/Studio/provider acceptance remains open.
Validation
Complete round6 at reviewed d1449c0/base d481d6a is not clean. Two P2 findings are adopted, none dropped; acceptance has no additional findings. Six full rounds completed, none clean; original bound exhausted. Reports and pre-correction inputs are retained at
e5df13ae16d9da2d421ec9aa66b9c477da99978b. No production correction is included in this evidence commit.C1: accepted P3000000D queues its first input, then cannot represent its deadline; restart/natural claim-expiry recovery keeps it Pending without a model header/receipt, while supported inspect/cancel404. Three original Runtime stores retain the actual source9c accepted input before any correction; PT1H control starts201. S1: owned RunBpmnState decoding leaks raw JsonException through public checkpoint cancellation after one retained predecessor read; zero physical persistence calls, no lost-state claim.
Prior source04c6928/0skip, four actual old-fault cuts, full two-family Studio restart proof/13 controls and12 binary comparisons remain positive at their declared source. Source9c116 frontend tests and both saved editor/exact-export/Test Run/Inspector checks remain positive;104 frozen assets unchanged. Independent acceptance28 portable checks/7842 references and standards discovery/TRX/integrity audits pass, without establishing these newly demonstrated cases.
Remaining gates
An owner review-route decision is required before exceeding the six-round bound; no seventh round or merge is started. T041/T043/T044 reopen; spec In progress. Existing owner API/version-magnitude/needs:decision, deferred GitGuardian39189012, exact required checks, normal protected merge and resulting-main verification remain open. Existing Codex claim/PR retained under end-to-end continuation; no competing leaf. #2898/#2907/#2908/#2892 stay open/Partial. First-class direct-model Studio, wider/upgraded-host ETL, non-SQLite actual-host acceptance, #3242 and Orleans/task-runner deferrals remain unchanged.