fix(docs): align refreshed guides with current SDK APIs

[snissn]

Summary

This PR is a reviewed, merge-ready version of the docs/refresh work from #628 with follow-up fixes found during deep-dive API/compile validation.

It includes all changes from #628 plus targeted corrections to keep developer-guide examples aligned with the current SDK/Core/React APIs and strict docs compilation.

Why this is needed

During review of #628, several docs examples were semantically or type-level out of sync with the latest APIs (some in non-Twoslash blocks, so they were not initially caught by type checks).

These issues would create confusing copy/paste failures or incorrect guidance even when docs built successfully.

Changes made

docs/src/content/docs/developer-guides/react-integration.mdx

• Fixed useAccountInfo example to avoid passing address: undefined under exactOptionalPropertyTypes.
• Fixed useDataSets example to pass address only when available.
• Added explicit wallet-connected guards in examples.

docs/src/content/docs/developer-guides/storage/storage-context.mdx

• Fixed batch-upload example to use supported UploadPieceStreamingData (Uint8Array[]) instead of File[] for StorageContext.upload.
• Updated piece-list example to reflect getPieces() returning PieceRecord (prints piece.pieceCid).
• Corrected deletion docs text/signature to deletePiece({ piece: ... }).
• Corrected download examples to current options-object API:
  • synapse.storage.download({ pieceCid, ... })
  • context.download({ pieceCid, ... })
• Corrected inheritance snippet (Synapse.create is sync in current API).

docs/src/content/docs/developer-guides/synapse.md

• Updated getProviderInfo signature docs to string | bigint.

docs/src/content/docs/developer-guides/synapse-core.mdx

• Replaced invalid short private key example (0x1) with a valid 32-byte hex key literal for Twoslash correctness.

Mergeability and readiness deep-dive

• docs: refresh developer guides #628 currently reports mergeStateStatus: CLEAN into master.
• This branch rebases docs: refresh developer guides #628 work with review fixes and remains mergeable.
• Docs/code validation now passes end-to-end.

Validation performed

• pnpm build (repo root): ✅ pass
• cd docs && pnpm build: ✅ pass
  • only non-blocking docs-plugin warnings remain (existing/reference warnings)

Reviewer notes

• Risk is low: docs-only changes.
• Impact is high for developer correctness: examples now match current API behavior and signatures.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	starlight-changelogs@​0.4.0
	starlight-auto-sidebar@​0.1.4
	@​hugomrdias/​docs@​0.1.11
	expressive-code-twoslash@​0.5.3
	starlight-links-validator@​0.19.2
	typedoc-plugin-missing-exports@​4.1.2
	rehype-external-links@​3.0.0
	typedoc-plugin-mdn-links@​5.1.1
	astro-mermaid@​1.3.1
	astro@​5.17.3
	vite-tsconfig-paths@​6.1.1
	mermaid@​11.12.3
	typedoc@​0.28.17

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@hugomrdias/docs@0.1.11 → npm/vite-tsconfig-paths@6.1.1 → npm/astro@5.17.3 → npm/vite@6.4.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@6.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	synapse-dev	417ba51	Commit Preview URL Branch Preview URL	Feb 24 2026, 09:21 PM