fix: update error hints to reference subdir after path→subdir rename

[min0625]

Three user-facing error hints still told users to check a mistyped path in the manifest, but the field was renamed to subdir in #31. Users following the hint would look for a key that no longer exists.

• internal/fetcher/fetcher.go (two occurrences)
• internal/hasher/hasher.go (one occurrence)

No golden files or docs contain the old wording, so this is a message-only change.

🤖 Generated with Claude Code

[qodo-code-review]

PR Summary by Qodo

Fix stale error hints: path → subdir in manifest guidance

🐞 Bug fix 🕐 Less than 5 minutes

AI Description

• Update config error hints to reference subdir after manifest field rename.
• Fix remaining occurrences in fetcher and hasher user-facing messages.
• Prevent users from searching for the removed path key in manifests.

High-Level Assessment

This is the correct, minimal fix: update the remaining user-facing hints to match the subdir manifest field rename. Alternatives (e.g., preserving path as an alias) are unnecessary for a stale-message-only issue and would introduce avoidable surface area.

Files changed (2) +3 / -3

Bug fix (2) +3 / -3

fetcher.goReplace 'path' with 'subdir' in missing-path config hints +2/-2

Replace 'path' with 'subdir' in missing-path config hints

• Updates two clierr config-hint strings emitted when a dependency path/subdir cannot be found at a commit. Aligns the guidance with the manifest field rename to 'subdir' so users are directed to the correct key.

internal/fetcher/fetcher.go

hasher.goReplace 'path' with 'subdir' in empty-dependency hint +1/-1

Replace 'path' with 'subdir' in empty-dependency hint

• Updates the clierr config-hint string used when a dependency tree contains no files. The hint now points users to the 'subdir' manifest field rather than the removed 'path' key.

internal/hasher/hasher.go

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review