Skip to content

Report initialization step timing - #871

Merged
SaladDay merged 2 commits into
mainfrom
report-initialization-step-timing
Oct 25, 2026
Merged

SaladDay merged 2 commits into
mainfrom
report-initialization-step-timing

Conversation

@SaladDay

@SaladDay SaladDay commented Oct 25, 2026 •

Copy link
Copy Markdown
Collaborator

Each terminal Runtime preparation result now carries the Runtime-measured duration_ms. Core records one step per confirmed operation (file, skill, plugin, configure, npm, python, setup with its index, finalize), logs one Environment initialization step line per step, and stores the list on the Environment so it survives a failed initialization.

An Environment that fails without a confirmed failed step now records a private failure category (timeout, runtime_disconnected, unconfirmed, rejected, operation_failed, core_error, core_restart, compute_released). The public reason is unchanged.

Session diagnostics return initialization_steps and params.category; the Web Session page shows an Initialization row and the category sentence.

  • Wire: docs/runtime-protocol.md
  • Diagnostics: contracts/agents-api/session-diagnostics.md, contracts/agents-api/core-errors.md
  • Migration 000009_environment_initialization_steps.sql

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

@SaladDay
SaladDay merged commit 170a498 into main Oct 25, 2026
25 checks passed
@SaladDay
SaladDay deleted the report-initialization-step-timing branch October 25, 2026 06:29
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.

1 participant