chore: refresh wording in runtime messages and pack headers#64
Merged
Conversation
Refresh user-facing wording across the runtime, CLI output, and contract pack headers. Touches Python source (cli, config, core, discovery, generation, integrations, models, onboard, patterns, protocols, render, runtime), TypeScript source (ts/packages/sdk/src/), and the contract pack headers in core/llm_safety, incident/openclaw, premium/.gitkeep (kept byte-identical across the Py and TS mirror pairs). Test assertion comments updated accordingly. No behavior changes. No signatures, return types, exception classes, exit codes, or control flow changed. Local gate: ruff check clean, ruff format clean, full pytest 2236 passed / 2 skipped, tsc --noEmit clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refresh user-facing wording across the runtime and contract pack headers so error/help/validation strings and code comments read consistently with the engine's surface.
In scope:
sponsio/):cli.py,config.py,core.py,contract.py,discovery/*,generation/*,integrations/base.py,models/contract.py,onboard*.py,patterns/__init__.py,protocols/sto.py,render/explain.py,runtime/{evaluators,monitor,strategies,verifier}.pyts/packages/sdk/src/):cli/{packs,patterns,validate}.ts,core/sto.ts,index.ts,integrations/openai-agents.tscore/llm_safety.yaml,incident/openclaw.yaml,premium/.gitkeep(kept byte-identical across the Python and TS mirror pairs)test_oss_sto_gate.py,test_skill_doc_sync.py,test_config_sections.py(no assertion-string changes)What stays the same
No behavior changes. No public signatures, return types, exception classes, exit codes, or control flow modified. The exported types (
StoEvaluator,StoResult,StoContract,JudgeClient,JudgeConfig,CloudFeatureError) and the gate behavior remain intact.Local gate
ruff check: cleanruff format --check: 234 files formattedpytest: 2236 passed, 2 skipped (3m35s)tsc --noEmit: clean🤖 Generated with Claude Code