Files
ARCADIA-Studio/harness/experiments/source-alias-rename-preparation-20260911/README.md
T

38 lines
2.2 KiB
Markdown

# Alias-rename preparation: preliminary CLI timing
Codex-9e8r6t `/root`; issue 9. This evaluates the existing CLI on the realistic
water-pressure walkthrough. It is not implementation or acceptance of a Text
rename dialog and does not measure `Document::execute` in isolation.
The preserved Windows debug CLI SHA256 is
`bad169f8be78dcfa74b32714569c886dd2132727080684fc2ba618d5822e3559`;
its [published provenance](../../release-cli-prerelease-published-20260911.md)
identifies semantic/build basis `01b76a1e89e93b7992f39e63560aa8b2ca2f69e0`.
The current desktop correction was not compiled into this binary. The copied
fixture contains 30 reachable Arcadia files and 37 physical files.
On 2026-09-11 at 19:09 UTC, `check` took 1.603 s; two separate default-preview
`rename-alias ... oa_restore_work oa_restore_pressure --json` processes took
2.186 and 2.189 s. All exited successfully. Preview JSON was identical between
runs; `written` was false, no identities needed stabilization, and migration was
null. Original and copied fixture inventories were unchanged. No `--write` was
used. Source/code and documentation work elsewhere on the host was not suspended;
these observations are not controlled performance benchmarks.
These timings include process startup, disk reads, compilation/validation and
JSON output. Do not subtract them to claim precise command timing or infer UI
responsiveness. They justify measuring accepted-snapshot preparation and
confirmation directly before settling the proposal's recomputation choice.
The 45 raw payloads total 446,726 bytes. Manifest SHA256:
`804a9098e5e2f5424334924bdf9d50f61473eaacd960acb6fe177a9d49a7aa2e`.
`cli-preview/receipt.json` records exact commands, timings, hashes and original
physical-file inventory; stdout/stderr and all copied inputs are retained.
`measure_cli.py` is the exact executed helper, archived from its original private
directory. It expects the documented pinned executable and prepared fixture at
their original project-local paths; reconstruct those inputs before rerunning in
a fresh output directory. The large executable is not duplicated here.
The manifest covers copied payloads; this README, `.gitattributes` and manifest
are explanatory/control files. No Linux/WSL actions or new grammar/API changes.