[PR #7480] [MERGED] fix(docs): drop duplicate native-inspection guide row #7865

Closed
opened 2026-11-05 01:48:15 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7480
Author: @BeqaKs
Created: 10/27/2026
Status: ✅ Merged
Merged: 11/3/2026
Merged by: @morluto

Base: main ← Head: fix/docs-index-native-guide-duplicate


📝 Commits (1)

  • 0f066f2 fix(docs): drop duplicate native-inspection guide row

📊 Changes

1 file changed (+0 additions, -1 deletions)

View changed files

📝 docs/index.md (+0 -1)

📄 Description

Summary

Fixes #7405. The docs home “Choose a guide” table listed the native-inspection task twice with inconsistent guide lists. This keeps the complete row (including Linux kernel modules) and removes the older incomplete duplicate.

Problem and expected behavior

docs/index.md had two body rows for “Inspect native functions, references, or types”: one linked kernel-modules.md, the other omitted it. The table should have one complete native-inspection row.

Change and scope

Editorial-only: delete the incomplete duplicate row. No other guide rows, website/i18n, or navigation changes.

Contribution scope: not applicable (documentation-only duplicate cleanup within existing docs).

Contract and boundary impact

  • Semantic owner and earliest changed stage: authored docs index navigation only; no runtime producers or consumers.
  • 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 (docs/public/product-catalog.json), package, or installation impact: none

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: none (editorial docs index row only)
  • Base reproduction or other evidence: source check before fix reported body_rows=12, distinct_tasks=11 with duplicate native rows (kernel_guide=True then False); after fix body_rows=11, distinct_tasks=11 with a single complete row
  • User-visible CLI/MCP output (if applicable): not applicable
  • Remaining proof gaps: rendered website page not rechecked in this change; source table uniqueness verified

Boundary/lifecycle regressions: not applicable (documentation-only).

Validation performed

  • npm run docs:check — passed (docs:check:built + readmeConsistency 9/9)
  • npm run format:check — passed (oxfmt)
  • npm run check:fast — passed (typecheck + lint)
  • source uniqueness probe — body_rows=11, distinct_tasks=11; one native-inspection row includes kernel-modules.md

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; docs navigation only

Author readiness

Human owner: @BeqaKs

  • 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.

🔄 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/7480 **Author:** [@BeqaKs](https://github.com/BeqaKs) **Created:** 10/27/2026 **Status:** ✅ Merged **Merged:** 11/3/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/docs-index-native-guide-duplicate` --- ### 📝 Commits (1) - [`0f066f2`](https://github.com/morluto/rea/commit/0f066f20ee4b42f3e2c71aa57bbb677d37caeb04) fix(docs): drop duplicate native-inspection guide row ### 📊 Changes **1 file changed** (+0 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/index.md` (+0 -1) </details> ### 📄 Description ## Summary Fixes #7405. The docs home “Choose a guide” table listed the native-inspection task twice with inconsistent guide lists. This keeps the complete row (including Linux kernel modules) and removes the older incomplete duplicate. ## Problem and expected behavior `docs/index.md` had two body rows for “Inspect native functions, references, or types”: one linked `kernel-modules.md`, the other omitted it. The table should have one complete native-inspection row. ## Change and scope Editorial-only: delete the incomplete duplicate row. No other guide rows, website/i18n, or navigation changes. Contribution scope: not applicable (documentation-only duplicate cleanup within existing docs). ## Contract and boundary impact - Semantic owner and earliest changed stage: authored docs index navigation only; no runtime producers or consumers. - 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 (`docs/public/product-catalog.json`), package, or installation impact: none Expected effects: - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: none (editorial docs index row only) - Base reproduction or other evidence: source check before fix reported `body_rows=12, distinct_tasks=11` with duplicate native rows (`kernel_guide=True` then `False`); after fix `body_rows=11, distinct_tasks=11` with a single complete row - User-visible CLI/MCP output (if applicable): not applicable - Remaining proof gaps: rendered website page not rechecked in this change; source table uniqueness verified Boundary/lifecycle regressions: not applicable (documentation-only). ## Validation performed - `npm run docs:check` — passed (docs:check:built + readmeConsistency 9/9) - `npm run format:check` — passed (oxfmt) - `npm run check:fast` — passed (typecheck + lint) - source uniqueness probe — `body_rows=11, distinct_tasks=11`; one native-inspection row includes `kernel-modules.md` ## 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; docs navigation only ## Author readiness Human owner: @BeqaKs - [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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-05 01:48:15 +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#7865
No description provided.