Why
@fedify/webfinger already distinguishes several lookup failure shapes, but callers still need enough metadata to explain what went wrong. Better error metadata would help CLI output and application diagnostics without forcing every caller to parse exception messages.
Scope
Review the lookup path in packages/webfinger/src/lookup.ts and the tests in packages/webfinger/src/lookup.test.ts. Add or refine structured failure metadata for cases such as fetch failures, invalid JSON Resource Descriptor payloads, redirect failures, and missing actor links.
Keep the public API small. If a type needs to change, update exports and package documentation so downstream callers can use the new metadata intentionally.
Suggested checks
Run mise run check-each webfinger. If the CLI can use the improved metadata with a small change, include that only when it stays narrow.
Why
@fedify/webfingeralready distinguishes several lookup failure shapes, but callers still need enough metadata to explain what went wrong. Better error metadata would help CLI output and application diagnostics without forcing every caller to parse exception messages.Scope
Review the lookup path in packages/webfinger/src/lookup.ts and the tests in packages/webfinger/src/lookup.test.ts. Add or refine structured failure metadata for cases such as fetch failures, invalid JSON Resource Descriptor payloads, redirect failures, and missing actor links.
Keep the public API small. If a type needs to change, update exports and package documentation so downstream callers can use the new metadata intentionally.
Suggested checks
Run
mise run check-each webfinger. If the CLI can use the improved metadata with a small change, include that only when it stays narrow.