fix: force UTF-8 stdout/stderr in repoctl and drop non-ASCII em dashes
End-to-end smoke testing of `init` and `adopt` (plan -> approve -> apply -> verify) via subprocess surfaced a real portability bug: on Windows, sys.stdout defaults to the console codepage rather than UTF-8 when not attached to a UTF-8 terminal, so machine YAML/JSON output containing non-ASCII characters (an em dash in generated skill/docstring text) could fail to decode for downstream consumers. repoctl now reconfigures stdout/stderr to UTF-8 unconditionally in main(), and the offending em dashes are replaced with ASCII hyphens so generated file content is unaffected either way. Verified via manual CLI smoke tests: full init and adopt flows (including baseline re-check, plan-hash approval, collision rejection on re-apply, and preservation of profiles-source/, profiles/ and legacy kdb.yaml) work end to end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
7286322c83
commit
64e6c2f5f5
@@ -1,6 +1,6 @@
|
||||
"""`repoctl init`: plan-then-apply bootstrap of a new repository.
|
||||
|
||||
Content roots are declared in the contract but their directories are not created —
|
||||
Content roots are declared in the contract but their directories are not created -
|
||||
this repository's self-hosting rule forbids placeholder directories and fictional
|
||||
domain artifacts. `init` never commits, pushes or creates a remote.
|
||||
"""
|
||||
|
||||
Reference in New Issue
Block a user