[PR #7158] [CLOSED] fix(doctor): classify unreadable skill identity as unknown #7683

Closed
opened 2026-11-03 13:39:38 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7158
Author: @surajvelip
Created: 10/25/2026
Status: ❌ Closed

Base: main ← Head: doctor-skill-identity-unknown


📝 Commits (1)

  • 41c78c3 Classify unreadable skill identity as unknown in doctor

📊 Changes

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

View changed files

📝 src/application/Doctor.ts (+2 -1)

📄 Description

Summary

Fixes #7091 — rea doctor classified an unreadable skill copy as config_drift while reporting unknown skill state.

Problem and expected behavior

A skill copy that cannot be read reports identity.skill.state: "unknown" but the skill:identity check classified it config_drift, directing users to repair drift when the real problem is unreadable files. It should classify unknown, matching the state and the registration checks.

Change and scope

skillIdentityCheck now maps the unknown state to the unknown classification, the same pattern registrationCheck already uses.

Contract and boundary impact

  • Semantic owner and earliest changed stage: doctor check classification
  • Contribution scope fit and linked maintainer decision: not applicable
  • CLI and MCP/tool-catalog contract: doctor --json classification value now matches the reported state
  • 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): none
  • Generated metadata, 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 added; existing Doctor.test.ts coverage passes
  • Base reproduction or other evidence: source-derived from the issue report
  • User-visible CLI/MCP output (if applicable): skill:identity check now reports classification: "unknown"
  • Remaining proof gaps: no rea doctor --json run against a real unreadable copy

Validation performed

  • npm run test:local -- src/application/Doctor.test.ts — 32/32 pass
  • lint-staged oxfmt/oxlint on commit — clean

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: reporting only

Author readiness

Human owner: @surajvelip

  • 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/7158 **Author:** [@surajvelip](https://github.com/surajvelip) **Created:** 10/25/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `doctor-skill-identity-unknown` --- ### 📝 Commits (1) - [`41c78c3`](https://github.com/morluto/rea/commit/41c78c309d3ba7233853b1a6208edf3ef6597951) Classify unreadable skill identity as unknown in doctor ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/application/Doctor.ts` (+2 -1) </details> ### 📄 Description ## Summary Fixes #7091 — `rea doctor` classified an unreadable skill copy as `config_drift` while reporting `unknown` skill state. ## Problem and expected behavior A skill copy that cannot be read reports `identity.skill.state: "unknown"` but the `skill:identity` check classified it `config_drift`, directing users to repair drift when the real problem is unreadable files. It should classify `unknown`, matching the state and the registration checks. ## Change and scope `skillIdentityCheck` now maps the `unknown` state to the `unknown` classification, the same pattern `registrationCheck` already uses. ## Contract and boundary impact - Semantic owner and earliest changed stage: doctor check classification - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: `doctor --json` classification value now matches the reported state - 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): none - Generated metadata, package, or installation impact: none Expected effects: - [x] 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 added; existing `Doctor.test.ts` coverage passes - Base reproduction or other evidence: source-derived from the issue report - User-visible CLI/MCP output (if applicable): `skill:identity` check now reports `classification: "unknown"` - Remaining proof gaps: no `rea doctor --json` run against a real unreadable copy ## Validation performed - `npm run test:local -- src/application/Doctor.test.ts` — 32/32 pass - lint-staged oxfmt/oxlint on commit — clean ## 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: reporting only ## Author readiness Human owner: @surajvelip - [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. - [ ] 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-03 13:39:38 +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#7683
No description provided.