Resolve #1610: Align Prisma token docs and transaction coverage

[ayden94]

Summary

• Clarifies @fluojs/prisma public DI tokens versus internal normalized module tokens across README and book material.
• Documents nested transaction option behavior for manual/request-scoped transaction reuse and adds focused regression coverage.

Closes #1610

Changes

• Added PRISMA_OPTIONS README sections in EN/KO and clarified named-token helpers as the public targeting surface.
• Updated Advanced Dynamic Modules book references to current Prisma module line ranges and internal-token boundaries.
• Updated Beginner Transactions book EN/KO to state nested transactions reuse the active client but reject nested transaction options.
• Added a patch changeset for @fluojs/prisma.

Testing

• pnpm --filter @fluojs/prisma test — 3 files / 27 tests passed.
• pnpm --filter @fluojs/prisma... build — Prisma package and dependency build passed.
• LSP diagnostics on packages/prisma — 0 diagnostics after dependency build.

Public export documentation

• Changed public exports include a source-level summary.
• Changed exported functions document matching @param / @returns tags where applicable.
• Source @example blocks and README scenario examples still play complementary roles.

Notes: no new exports were added; the existing PRISMA_OPTIONS token summary was clarified to distinguish public runtime options from internal normalized module tokens.

Behavioral contract

• No documented behavioral contracts were removed without migration notes.
• New behavioral contracts are documented in the affected package README.
• Intentional limitations are explicitly stated (not silently removed).
• Runtime invariants are covered by regression tests.

Notes: nested transaction option rejection is now documented in book material and covered for request-scoped transaction reuse.

Platform consistency governance (SSOT)

• SSOT English/Korean mirror structure remains synchronized for changed governance docs.
• If platform contract docs changed, companion updates include discoverability/docs index, tooling or CI enforcement, and regression-test evidence.
• Any package README alignment/conformance claims are backed by createPlatformConformanceHarness(...) tests.

Notes: no platform contract docs or platform conformance claims changed; EN/KO package and book mirrors were updated together.