1097bd3c3c
The review's suggestion: the open-merge mechanism (incremental split billing on both sides, host caps logBudget-1/logBudget+2, the sub-2-byte walk guard, the child's _open_started-keyed billing) lived only in code comments. The wire contract section of the note now states it, paired and re-recorded.
6 lines
559 B
YAML
6 lines
559 B
YAML
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
|
|
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
|
# after editing either side, bring the other along and re-record with:
|
|
# pnpm run verify-translation-pairing --write .agents/notes/implemented/architecture/2026-07-31-code-runtime-python-fd3-protocol.md
|
|
2026-07-31-code-runtime-python-fd3-protocol.md: 61974380011d1b2c25d9eadd55645cfad47c163a
|
|
2026-07-31-code-runtime-python-fd3-protocol.zh.md: 0aeee5bfbd36f54035a37f9e409f1f857cfbdf23
|