Update CLI Stage runtime to 4.39

[einari]

Changed

• cratis render and cratis run now use Stage 4.40.0 packages and the matching cratis/stage:4.40.0 runtime image by default. (part of Pass full screen application and package configuration through run and render #284)

[einari]

Verification notes:

• dotnet restore is blocked before build/test by unavailable Stage 4.39.0 packages from configured NuGet sources. Log: .ai-work/logs/cli-dotnet-restore-stage439.log.
• NuGet flat-container probe for Cratis.Stage.Contracts currently lists latest 4.38.1, not 4.39.0. Probe saved at .ai-work/nuget-stage-contracts-after.json.
• The PR changes only the Stage version vector, docs, and specs asserting render/run use the released Stage 4.39 package/image pair.

Release vector:

• Stage release: v4.39.0.
• Stage merge commit: 87f8026c2b0bdacfbe9612221469b9710ee5b9f9.
• Stage image: cratis/stage:4.39.0 (sha256:302fb8e4eb6073bd098a6192c708d1d8fd5861b8ca9a0ede49c2ceb6b193b360).
• Stage spec runner image: cratis/stage-specrunner:4.39.0 (sha256:1289d539d2f20acd81cca21dafcad745fa799baced32957e8478e5614abacfea).

[einari]

Round 3 status:

• Merged origin/main into the branch with a true merge commit (feb9d2a) to resolve PR conflicts; PR Update CLI Stage runtime to 4.39 #288 is now mergeable.
• Local dotnet restore is still blocked by unavailable Stage 4.39.0 NuGet packages. Log: .ai-work/logs/cli-dotnet-restore-stage439-after-merge.log.
• CI confirms the same restore blocker: Cratis.Stage.Contracts and Cratis.Stage.Rendering.Cratis 4.39.0 are not visible from NuGet; nearest is 4.38.1. Build run: https://github.com/Cratis/cli/actions/runs/37830776655.
• Release notes, release intent, markdown lint, and link verification checks are green.

No CLI code fallback to local Stage outputs was added; the branch remains pinned to the requested released Stage vector and blocked until the 4.39.0 packages are available to restore.

[einari]

Round 4 verification notes:

• NuGet flat-container now lists Stage 4.39.0 for Cratis.Stage.Contracts and Cratis.Stage.Rendering.Cratis; local NuGet HTTP cache had to be cleared before restore saw it.
• dotnet restore passed after clearing the NuGet HTTP cache. Log: .ai-work/logs/cli-dotnet-restore-stage439-round4-after-cache.log.
• dotnet build passed. Log: .ai-work/logs/cli-dotnet-build-round4.log.
• dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter FullyQualifiedName~StageContainer passed. Log: .ai-work/logs/cli-dotnet-test-stagecontainer-round4.log.
• dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter FullyQualifiedName~RunCommand passed. Log: .ai-work/logs/cli-dotnet-test-runcommand-round4.log.
• dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter "FullyQualifiedName~CratisRenderTarget|FullyQualifiedName~ScreenplayPlanning|FullyQualifiedName~RenderCommand" passed. Log: .ai-work/logs/cli-dotnet-test-renderplanning-round4-2.log.
• dotnet test passed. Log: .ai-work/logs/cli-dotnet-test-round4.log.

A follow-up commit (983be6a) aligns the affected specs with the Stage 4.39 package behavior.

[einari]

Round 5 Stage 4.40 update:

• Public NuGet flat-container visibility is present for Stage 4.40.0: Cratis.Stage.Contracts, Cratis.Stage.Rendering.Cratis, Cratis.Stage.Rendering.Cratis.Scaffolding, Cratis.Stage.Specifications, and Cratis.Stage all list 4.40.0.
• Docker image cratis/stage:4.40.0 is visible. Manifest entries observed:
  • linux/amd64 sha256:e748288e63dc046354cd861ab203fd190f094b4c3952d9547ba065c04ad5afc0
  • linux/arm64 sha256:2cba781f4d34e632601f245939c3ace80c1ef75482051f4c2ca558abdae8f37f
• Appended commit c33373a updates CLI StageVersion, docs, default image assertions and renderer package assertions from Stage 4.39.0 to 4.40.0.

Local checks:

• PASS: dotnet restore — .ai-work/logs/cli-dotnet-restore-stage440.log
• PASS: dotnet build — .ai-work/logs/cli-dotnet-build-stage440.log
• PASS: dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter FullyQualifiedName~StageContainer — .ai-work/logs/cli-dotnet-test-stagecontainer-stage440.log
• PASS: dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter FullyQualifiedName~RunCommand — .ai-work/logs/cli-dotnet-test-runcommand-stage440.log
• PASS: dotnet test Source/Cli.Specs/Cli.Specs.csproj --filter "FullyQualifiedName~CratisRenderTarget|FullyQualifiedName~ScreenplayPlanning|FullyQualifiedName~RenderCommand" — .ai-work/logs/cli-dotnet-test-renderplanning-stage440.log
• FULL SUITE ATTEMPTED: dotnet test timed out at 300s and again at the 600s maximum. The 600s log shows Templating and Chronicle integration suites passed, then the run timed out in unrelated CLI specs after for_ValidateScreenplayCommand.when_selecting_a_scope.and_a_module_is_selected.should_exclude_other_module_diagnostics cancelled. Log: .ai-work/logs/cli-dotnet-test-stage440-full-600.log.

CI status after the Stage 4.40 commit: all visible PR checks are green and the PR is mergeable.

[einari]

Coordinator review/test notes for screens-release CLI tranche:

• Reviewed as a partial cli#284 Stage-vector tranche, not final Scene#7 completion.
• PR body uses (part of #284) and should not close the issue by itself.
• Consumes released Stage v4.40.0 packages/image; public NuGet and Docker visibility recorded in worker status.
• CI is green on reviewed head c33373a; local targeted restore/build/specs passed. Full local dotnet test was attempted up to the 600s cap and timed out in unrelated validation specs after targeted in-scope Stage/run/render checks passed.
• Remaining after release: final canonical conformance/Studio/Stage/CLI/browser vector must still exercise exact shipped packages/images.