Repository navigation
test(research): observe dual-axis WindTerm resize and replay it in core - #316
Merged
JavaZeroo merged 6 commits intoNov 5, 2026
Merged
Conversation
Add a new independent probe for the missing #27/#29 original observation: one window action simultaneously narrows 91x20 to 61x14, then a fixed CUP(7;2)+"DQ" write and DSR are sent, and a second window action restores 91x20 before the final DSR. The controller records actual NAWS event count and order instead of assuming an atomic two-axis transport event, and the strict exporter accepts only finite source-derived ASCII lines with one bounded write line. The old combined/height/width probes and their frozen records are unchanged. Offline Python and Node controllers pass; no original run has happened yet. Co-authored-by: JavaZeroo <[email protected]>
Publish the one authorized dual-axis original capture and its strict export: one window action 91x20 -> 61x14 followed by CUP(7;2)+"DQ"+DSR, then restore to 91x20. The capture recorded NAWS 1->2, scroll 5, DSR 7;4 before and after the restore, and a 62-character written row " DQ"+58 spaces+"w". Add resize_dual_axis_core: the retained row is still full before the fixed write, the edited row materializes to the observed 62-character form, and the protocol DSR is 7;4 at both points. The old six-stage B/CD native-sync failure is not explained or relaxed, and no production behavior was changed. Update EVIDENCE/FEATURES and accept the bounded clipped/write form in the dual-axis strict exporter. Co-authored-by: JavaZeroo <[email protected]>
Record that the first strict export refused the observed clipped/write row before writing mechanics-check.json. The correction stayed offline (document line whitelist/exporter) and reused the same raw recording, plan and .attempted marker; the original was not rerun. Co-authored-by: JavaZeroo <[email protected]>
5 tasks
Owner
|
@JavaZeroo-Bot 本轮交付核验暂不合并 #316。请在原 ticket 2e7373117ea0e21d783b8ef977a13581 修正下列证据边界，保持单 worker、Flash 优先。允许修改报告/身份记录、必要离线验证并推送新 head；本轮不是要求重跑原版或接管实现，不触发 Codex review。
请逐处核对 PR正文、README、FEATURES/EVIDENCE、validation与测试合同说明，将已观测事实限定为“缩放+后续CUP写入后的行/DSR/scroll结果”；明确裁剪/物化发生在resize、CUP或写入哪个时点未知，pre-write保留检查目前只属于产品工程不变量，不是已验证的原版差异。若原始冻结录制确实已有独立pre-write正文观察，可只读提取并给出精确来源；没有则保持缺口，不篡改旧录制、不通过重新解释最终结果补造中间态。原版实际NAWS/CUP/DSR/写后文本及现有11项核心工程测试仍可交付，不需丢弃。
出口：修正后新的head、准确的观测/工程/未知分界与身份说明，必要定向检查及属于新head的CI。此处未批准任何新产品行为或取消原版差异，#27/#29仍OPEN。调度者读回核验后再合并。若仍缺来源而不能交付，明确阻塞及解除条件，不无限重试。 |
Open
Collaborator
Author
|
On it: correcting #316's evidence boundaries without rerunning the original. I will limit the claimed facts to the post-resize CUP/write endpoint, mark clipping attribution and the #308 comparison as unknown, and split the frozen run source from the later offline-export/core-replay source identities in validation and reports. |
Limit the recorded fact to the post-resize CUP+write endpoint: no original pre-write body observation exists, so clipping/materialization cannot be attributed to resize, CUP or the write, and the sequential #308 sample is not a comparable control. Pre-write full-row retention remains only the core engineering invariant. Split the frozen original-run source identity from the later offline exporter and core-replay source identities in validation, and record the offline export correction without rerunning the original. Co-authored-by: JavaZeroo <[email protected]>
Set the validation documentation identity to the correction commit without changing the frozen run, plan or .attempted marker. Co-authored-by: JavaZeroo <[email protected]>
Record the attribution correction and the validation/identity correction as separate documentation commits; neither reran the original or changed the frozen source/plan/attempt identity. Co-authored-by: JavaZeroo <[email protected]>
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
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.
背景
#27/#29 仍缺“主屏同一窗口动作同时缩宽+缩高后视口/滚动选择与后续 CUP/DSR”的原版证据；只缩宽（#309）、顺序宽高组合（#308）与隐藏帧七阶段（#315）都不足以决定该场景。本 PR 新增一个预先冻结的最小探针，完成一次授权原版观察，并据此增加当前核心的有界工程回放。
改动
resize_dual_axis_reference（探针 + 控制器 + 严格导出器 + 离线测试；CMake/CTest 注册）：91×20正文 → 一次窗口动作61×14→ 固定CUP(7;2)+"DQ"+DSR→ 一次窗口动作恢复91×20+ DSR。95ad9c5b…）、validation.json。计划3beabf9a…、单次.attempted标记、参考 EXE7b10531d…/4047 清单e459adf2…均由严格出口核验。resize_dual_axis_core工程回放（11 项检查）：保留行在双轴事务后仍完整；固定写后该编辑行按当前 61 列足迹物化为记录中的DQ+58 空格+w（62 字符）；DSR 在写后与恢复后均为7;4。未修改生产实现。.attempted，未重跑原版。身份分层
dee3c78…；10 个执行源哈希与严格出口的execution_source_files_sha256一致；计划/attempted 见上2fc3f25…的导出器/白名单；严格出口offline_export_source_files_sha256已核对，未倒填为原运行源2fc3f25…的resize_dual_axis_test.cpp与 CMake 注册；不是原版运行源1e41fc7…；本次边界修正aed6333…/e3296fc…实测（一次原版运行，写后端点）
19;7uvw（92）7;4DQ+58 空格+w（62）7;4证据边界：阶段 1 的正文端点是“缩放后又执行 CUP+写入”之后的结果；录制中没有“缩放后、写入前”的原版正文端点，因此无法判断裁剪/物化发生在 resize、CUP 还是写入。pre-write 保留完整 92 字符只是 TermForge 核心工程不变量，不是已验证的原版差异。#308 顺序样本没有同样的后续写入干预，不能作为裁剪差异对照；不据此裁决双轴与顺序 resize 的裁剪差异，也不证明宽高交换律。
本地验证
-O由 CTest 注册）、Node controller 13/13 通过、0 原版/0 socket。resize_dual_axis_core1/1（11 断言），默认核心 CTest 38/38 通过。边界