[PR #1440] [MERGED] docs(process): verify independent full-report hashing budgets #2889

New issue

Closed

opened 2026-10-17 21:11:26 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-17 21:11:26 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1440
Author: @N0zoM1z0
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/10/2026
Merged by: @N0zoM1z0

Base: main ← Head: docs/process-full-report-digest-1251

📝 Commits (1)

395694b docs(process): verify independent full-report hashing budgets

📊 Changes

2 files changed (+148 additions, -2 deletions)

View changed files

📝 docs/process-capture.md (+44 -2)
📝 tests/boundary/process/processFilesystemCoverageAdapters.test.ts (+104 -0)

📄 Description

Fixes #1251.

limits.file_bytes already bounds whole-file hashing independently of retained terminal output. Clarify its cumulative scope and reset at each filesystem checkpoint, and add an executable complete-report example with a 1 KiB terminal budget and a 256 KiB hash budget. Explain that a full digest binds checkpoint bytes; the producer's completion marker, exit and settlement must establish whether those bytes are final.

The documented scenario now runs through compiled CLI and actual SDK MCP adapters with a real owned child. Additional captures cover exact/cumulative budgets and independent before/after accounting, including a stable running report. Existing changed/replaced-file and cancellation cleanup regressions remain green. No duplicate budget option or digest algorithm change is needed.

Validation:

35 tests across filesystem adapters, truncation adapters, snapshot identity/cancellation and filesystem coverage.
Full serial typecheck, lint/module boundaries, docs check, formatting and whitespace checks pass.
Fresh public stdio MCP runs the documented scenario: a 131,103-byte report has its independently verified complete SHA-256 despite omitted verbose terminal output; text/structured parity, exit 0, verified owned-group cleanup and subsequent ping pass. Two CPUs, 768 MiB Node heaps, 1.5 GiB family guard; observed peak 803,524,608 bytes.
Native Windows PTY capture remains unavailable as documented. Hopper/Ghidra are not involved.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1440 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `docs/process-full-report-digest-1251` --- ### 📝 Commits (1) - [`395694b`](https://github.com/morluto/rea/commit/395694b4b8059e9d2663179f44e3ec7ba06acc7c) docs(process): verify independent full-report hashing budgets ### 📊 Changes **2 files changed** (+148 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/process-capture.md` (+44 -2) 📝 `tests/boundary/process/processFilesystemCoverageAdapters.test.ts` (+104 -0) </details> ### 📄 Description Fixes #1251. `limits.file_bytes` already bounds whole-file hashing independently of retained terminal output. Clarify its cumulative scope and reset at each filesystem checkpoint, and add an executable complete-report example with a 1 KiB terminal budget and a 256 KiB hash budget. Explain that a full digest binds checkpoint bytes; the producer's completion marker, exit and settlement must establish whether those bytes are final. The documented scenario now runs through compiled CLI and actual SDK MCP adapters with a real owned child. Additional captures cover exact/cumulative budgets and independent before/after accounting, including a stable running report. Existing changed/replaced-file and cancellation cleanup regressions remain green. No duplicate budget option or digest algorithm change is needed. Validation: - 35 tests across filesystem adapters, truncation adapters, snapshot identity/cancellation and filesystem coverage. - Full serial typecheck, lint/module boundaries, docs check, formatting and whitespace checks pass. - Fresh public stdio MCP runs the documented scenario: a 131,103-byte report has its independently verified complete SHA-256 despite omitted verbose terminal output; text/structured parity, exit 0, verified owned-group cleanup and subsequent ping pass. Two CPUs, 768 MiB Node heaps, 1.5 GiB family guard; observed peak 803,524,608 bytes. - Native Windows PTY capture remains unavailable as documented. Hopper/Ghidra are not involved. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-17 21:11:26 +00:00