[PR #5667] [CLOSED] docs(browser): describe admitted unsafe HAR numbers accurately #7023

Closed
opened 2026-11-01 21:44:47 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5667
Author: @umi008
Created: 10/20/2026
Status: ❌ Closed

Base: main ← Head: fix/5444-har-numeric-docs


📝 Commits (1)

  • eb7bd85 docs(browser): describe admitted unsafe HAR numbers accurately

📊 Changes

1 file changed (+4 additions, -2 deletions)

View changed files

📝 docs/web-network-captures.md (+4 -2)

📄 Description

Summary

Fixes #5444. The capture guide's numeric_literals bullet said unsafe standard HAR numeric fields fail schema validation. The inspector admits schema-valid HAR numbers that cannot be published safely as JSON numbers, publishes them as null in reported, and keeps their exact lexemes in numeric_literals.

Problem and expected behavior

docs/web-network-captures.md described a blanket rejection that no longer matches the admission behavior pinned by src/browser/history/HarCapture.test.ts and introduced in #3159.

Change and scope

Replaces the stale sentence with the wording proposed in the issue. Documentation only; no runtime change.

Contribution scope: not applicable (documentation fix within existing boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation only

  • Contribution scope fit and linked maintainer decision: not applicable

  • CLI and MCP/tool-catalog contract: none

  • Provider, bridge, target-format, or platform compatibility: none

  • Evidence, artifact, provenance, or reconstruction contract: none

  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable

  • Generated metadata, package, or installation impact: none

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none (documentation only)
  • Base reproduction or other evidence: source-derived from the issue's cited tests (HarCapture.test.ts) and CHANGELOG entry; not re-run at runtime for this PR.
  • Remaining proof gaps: npm run docs:check was not completed locally (see below).

Validation performed

  • npm run test:local -- tests/conformance/readmeConsistency.test.ts — 5 passed
  • npm run check:fast (pre-push hook) — passed
  • npm run docs:check — not completed on the local Windows host: compilation failed from an unrelated @xterm/xterm package in an ancestor node_modules; CI will run it.

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: none

Author readiness

Human owner: @umi008

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🤖 Generated with Claude Code


🔄 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/5667 **Author:** [@umi008](https://github.com/umi008) **Created:** 10/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/5444-har-numeric-docs` --- ### 📝 Commits (1) - [`eb7bd85`](https://github.com/morluto/rea/commit/eb7bd85145bd5b2c96eae0831778c5d2bc86e9df) docs(browser): describe admitted unsafe HAR numbers accurately ### 📊 Changes **1 file changed** (+4 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/web-network-captures.md` (+4 -2) </details> ### 📄 Description ## Summary Fixes #5444. The capture guide's `numeric_literals` bullet said unsafe standard HAR numeric fields fail schema validation. The inspector admits schema-valid HAR numbers that cannot be published safely as JSON numbers, publishes them as `null` in `reported`, and keeps their exact lexemes in `numeric_literals`. ## Problem and expected behavior `docs/web-network-captures.md` described a blanket rejection that no longer matches the admission behavior pinned by `src/browser/history/HarCapture.test.ts` and introduced in #3159. ## Change and scope Replaces the stale sentence with the wording proposed in the issue. Documentation only; no runtime change. Contribution scope: not applicable (documentation fix within existing boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation only - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable - Generated metadata, package, or installation impact: none - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none (documentation only) - Base reproduction or other evidence: source-derived from the issue's cited tests (`HarCapture.test.ts`) and CHANGELOG entry; not re-run at runtime for this PR. - Remaining proof gaps: `npm run docs:check` was not completed locally (see below). ## Validation performed - `npm run test:local -- tests/conformance/readmeConsistency.test.ts` — 5 passed - `npm run check:fast` (pre-push hook) — passed - `npm run docs:check` — not completed on the local Windows host: compilation failed from an unrelated `@xterm/xterm` package in an ancestor `node_modules`; CI will run it. ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: not applicable - Package or release metadata impact: none - Security, privacy, process, or containment review: none ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @umi008 - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:47 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7023
No description provided.