docs(core): document combinators via the guide instead of a split method type

[btravers]

Follow-up to #66 (already merged).

Context

#66 tried to make flatMap (and the other combinators) discoverable in the generated API reference by exposing ResultMethods + a new AsyncResultMethods as public types. But Result / AsyncResult are discriminated-union aliases, and TypeDoc can't hang a method list off a union — so that approach split the surface into two near-identical method blocks (ResultMethods and AsyncResultMethods), each a hop away from the type you actually landed on, when the mental model (and the guide) is that there's one shared surface.

This PR

Keep the method surface internal; point at the guide instead.

• Revert the exports. ResultMethods goes back to @internal + intentionallyNotExported; AsyncResult's methods are inline again (no AsyncResultMethods). No standalone method type in the public surface.
• Link to the guide. The Result / AsyncResult type docs now link to the intent-organized Choosing a combinator guide, which already documents both in one shared table.
• The categoryOrder reordering and the "Why this matters more with AI in the loop" guide section from docs(core): surface the fluent combinators in the API reference via the guide #66 are unchanged.
• Changeset downgraded minor → patch (the only net effect vs. docs(core): surface the fluent combinators in the API reference via the guide #66 is removing the two type exports it added).

Verification

All gates green: format --check, lint, typecheck, knip, test, build. build:docs is warning-free and the VitePress site builds cleanly (the API→guide dead-link check passes).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR adjusts how the Result / AsyncResult fluent combinator surface is presented in generated docs by removing standalone “method surface” types from the public API and instead linking consumers to the intent-organized guide.

Changes:

• Stop exporting ResultMethods and remove AsyncResultMethods; inline the async method surface back onto AsyncResult.
• Update Result / AsyncResult API docs to link to the “Choosing a combinator” guide.
• Update TypeDoc config / internal docs and downgrade the changeset bump to patch.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/core/typedoc.json	Adds ResultMethods to intentionallyNotExported to align TypeDoc output with the internalized method surface.
packages/core/src/types.ts	Marks ResultMethods as @internal and inlines async combinators back into AsyncResult (removing AsyncResultMethods).
packages/core/src/index.ts	Removes public type exports for ResultMethods and AsyncResultMethods.
packages/core/src/facade.ts	Updates public API docs for Result / AsyncResult to point to the “Choosing a combinator” guide.
CLAUDE.md	Updates contributor/internal documentation to reflect the new documentation approach and non-exported method surface.
.changeset/document-combinator-surface.md	Updates release notes and bumps changeset from minor to patch.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[btravers]

Good catch — fixed in 62f9ddf. The changeset now states plainly that this removes the ResultMethods/AsyncResultMethods exports #66 added, and notes those exports were never released, so no published type surface changes and the patch bump stands.