docs: show recall() scoringWeights on SKILL.md (WALM-616)

[HoangDucBach]

Ticket

WALM-616 — https://linear.app/mysten-labs/issue/WALM-616
GH #708 — #708

What changed?

• TypeScript recall() already sends scoring_weights when RecallOptions.scoringWeights is set (shipped in 0.1.6). Existing tests in recall-created-at.test.mjs pin the wire body.
• SKILL.md still listed the old recall({ query, limit?, topK?, namespace?, maxDistance? }) / RecallOptions without scoringWeights or sort. That is the copy GH recall() cannot use recency-weighted ranking that already exists in the SDK — it's implemented, typed, and wired, but only reachable through recallManual() #708 used to conclude recency ranking was unreachable.

Why is this needed?

Agents reading SKILL.md still cannot see scoringWeights on recall(). The SDK gap is already closed; this is the remaining advertised contract.

Scope

SKILL.md only. No MCP memwal_recall change (WALM-428).

Out of scope

• MCP sort=recent (WALM-428)
• Python recall() still does not send scoring_weights

How was this tested?

• Unit tests
• Integration tests
• End-to-end tests
• Manual testing
• Not applicable

Commands: npm test --prefix packages/sdk (includes recall sends scoringWeights as snake_case scoring_weights)

Verify

• recall({ query, scoringWeights: { semantic: 1, recency: 0.5 } }) POSTs scoring_weights
• Omit scoringWeights and the body has no scoring_weights key
• MCP memwal_recall schema unchanged

Risks

Docs-only. No runtime change.

Author checklist

• I ran the relevant tests (npm test --prefix packages/sdk)
• I did not bump the unpublished 0.1.7 changelog (behavior already in 0.1.6)
• No secrets committed

[ducnmm]

Summary

Docs-only: SKILL.md now lists sort and scoringWeights on recall() / RecallOptions. That matches origin/dev (recall() already POSTs scoring_weights since 0.1.6). No dump needed. MCP memwal_recall is untouched.

Issue counts by severity

• bugs: 0
• suggestions: 1
• nits: 0

[ducnmm]

[suggestion] scoringWeights?: ScoringWeights is the advertised contract this ticket is closing, but ScoringWeights is never defined in SKILL.md. Agents reading only this file still cannot see { semantic?, recency?, recencyHalfLifeDays?, importance? }.

Suggestion: Add the ScoringWeights interface next to RecallOptions (same fields as packages/sdk/src/types.ts). A one-liner that sort: "recent" is newest-wins (over-fetch then write-time) and scoringWeights only re-ranks the cosine window would match the SDK docs.

[HoangDucBach]

Added ScoringWeights next to RecallOptions, plus the sort vs weights one-liner.

[ducnmm]

LGTM, documentation updates match the SDK options.