Skip to content

Bound CLI migration readiness by process lifecycle - #2613

Open
Chris0Jeky wants to merge 1 commit into
mainfrom
issue-1665/migration-readiness
Open

Bound CLI migration readiness by process lifecycle#2613
Chris0Jeky wants to merge 1 commit into
mainfrom
issue-1665/migration-readiness

Conversation

@Chris0Jeky

Copy link
Copy Markdown
Owner

Summary\n\n- Race the migration startup-trace observer against the real CLI process task and one absolute default process deadline.\n- Fail promptly on early process completion with exit code, bounded redacted stderr, and the last trace snapshot.\n- Keep the existing cancellation/reap path and production process deadline unchanged.\n- Add deterministic regressions for early completion and missing readiness.\n\n## Verification\n\n- dotnet test backend/tests/Taskdeck.Cli.Tests/Taskdeck.Cli.Tests.csproj -c Release -m:1 --filter FullyQualifiedName~CliTestHarnessTests — 24/24\n- dotnet test backend/tests/Taskdeck.Cli.Tests/Taskdeck.Cli.Tests.csproj -c Release -m:1 — 208/208\n- git diff --check origin/main...HEAD — passed\n\n## Docs\n\nNo canonical docs changed; this is a bounded CLI test-harness repair.\n\n## Scope\n\nRefs #1665

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

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

Labels

None yet

Projects

Status: Pending

Development

Successfully merging this pull request may close these issues.

1 participant