Standardize Cycles scope terminology and clarify protocol behavior

[amavashev]

Summary

This PR updates documentation across multiple guides to standardize terminology for Cycles budget scopes and clarify the reserve/commit/release protocol behavior. The changes reflect a more consistent naming convention and better explain automatic vs. explicit release semantics.

Key Changes

Scope Terminology Updates:

• Replaced "application" with "app" throughout
• Replaced "environment" with "workspace"
• Replaced "run" as a built-in scope with guidance to use dimensions field for run-level tracking
• Replaced "tool" with "toolset"
• Reordered scope hierarchy to: tenant → workspace → app → workflow → agent → toolset

Protocol Behavior Clarification:

• Clarified that unused remainder is released automatically when actual usage is committed (not a separate step)
• Separated explicit release behavior: only needed when work is canceled or fails before producing usage
• Updated step descriptions to reflect automatic release as part of commit operation
• Simplified example flows to show automatic remainder handling

Documentation Improvements:

• Added explicit note in "how-to-model-tenant-workflow-and-run-budgets" explaining run-level budgets use dimensions field
• Clarified shadow mode behavior with dry_run: true protocol parameter
• Updated policy examples to reference "per-workspace limits" instead of "per-environment"
• Refined language around when explicit release is necessary vs. automatic

Notable Details

• The changes maintain backward compatibility in concept while improving clarity
• Run budgets are now modeled as a dimension rather than a built-in scope, providing more flexibility
• The reserve/commit/release pattern is now more precisely documented: reserve → execute → commit (auto-releases unused) → release only if canceled

https://claude.ai/code/session_01KLGxrhRub1DLcL9ZXZZ9wG