Turtle
e7def469e1
* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
description, kind
| description | kind |
|---|---|
| Cross-runtime UUID generation for maintainers replacing secure-context-only crypto.randomUUID calls. | package-library |
dsh-util-crypto
English | 中文
Summary
Zero-dependency browser-safe UUID and byte-encoding helpers. UUID minting uses crypto.getRandomValues, the one random primitive every shipped context provides. crypto.randomUUID is a secure-context Web API: a page or worker served over plain HTTP on a LAN address (the browser preview deployment) has no such method, so code that must run there cannot call it. The repository-wide no-restricted-properties lint rule points crypto.randomUUID callers here; Node-only code importing randomUUID from node:crypto stays as it is.
Table of Contents
Use this package
It is a library, not a service or plugin: no ctx, registers nothing, holds no state.
API
import { bytesToBase64, randomUUID, type Uuid } from '@deepseek-ai/dsh-util-crypto'
| Export | Role |
|---|---|
bytesToBase64(data) |
Canonical base64 for a byte array, encoded in bounded chunks. |
randomUUID() |
Random RFC 9562 v4 UUID string, minted from crypto.getRandomValues. Drop-in for crypto.randomUUID(). |
Uuid |
The five-group UUID string type, matching crypto.randomUUID's declared return shape. |
Model Experience
Indirectly, through consumers that mint request, session, and attachment identifiers with it, none of which enter prompts as semantic content.
KV Cache effect
No direct invalidation; identifier-minting consumers own any request changes.
Known Limitations and Deferred Work
- v4 only — no other UUID versions, namespaces, or parsing; consumers needing more should take a real UUID dependency.
- Uniqueness is probabilistic — 122 random bits, the same guarantee
crypto.randomUUIDgives; nothing here detects collisions.
Dev Note
Working context for maintainers — click to expand
None.
Runtime invariant: No companion is published. This pure utility owns no event stream or mutable runtime data; its value algebra is enforced by unit tests.