docs(code-runtime-python): register the zero-billed empty open-frame hold as a known limitation

The review's suggestion: an empty open continuation frame bills zero and holds
one host slot, so a forged empty-open flood grows the held fragment array
without touching logBudget. Accepted as a residual (per-frame host cost far
below its ~30-byte fd-3 wire cost, bounded by pipe throughput, model-code trust
level equal to bash) and now registered in the README's Known Limitations on
both sides, paired and re-recorded.
This commit is contained in:
Chinesezjc
2026-08-31 15:04:43 +08:00
committed by Tianyi Cui
parent 909d5c334b
commit e7ac747e2d
3 changed files with 4 additions and 2 deletions
@@ -2,5 +2,5 @@
# 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 packages/code-runtime/code-runtime-python/README.md
README.md: 889776e03c7af250411fe7ff9663204febf1e1bf
README.zh.md: 233cf01c3e1f8ad97f181e7f65ce009438e2366d
README.md: eaba8999c03429473acbfc968ebd0dcd6aae1080
README.zh.md: f71eb0b76fbeeece79e747befb1dd090dfd7bb58