Skip to content

Publish adapter, tracker and working-memory translations - #838

Open
zlareb1 wants to merge 2 commits into
mainfrom
docs/publish-reviewed-translations-batch4-public
Open

zlareb1 wants to merge 2 commits into
mainfrom
docs/publish-reviewed-translations-batch4-public

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 18, 2026

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • Documentation (changelog entry is not required)

Changelog entry

Publish eighteen reviewed documentation translations: adapter architecture pages in all five translation languages, Japanese tracker guidance and Spanish and Korean working-memory references.

Why

These generated pages have complete semantic and native-language reviews and available translated link destinations. Publishing them makes the adapter boundaries, tracker contract and working-memory operations available through the existing native documentation navigation.

Scope and risk

Generated Markdown only. Each imported page retains its exact model output, source blob, configured model and bilingual authority notice. The maintained producer validates protected content and link dependencies before publication. Existing pending pages keep their generated bytes and source stamps. English remains canonical, and incomplete or stale coverage remains explicit.

Compatibility, rollout and rollback

  • Wire and settings: none.
  • Operator steps: none. The documentation deployment publishes the available pages after merge. Automatic paid translation runner configuration remains separate.
  • Rollback: reverting removes these added documentation pages.

Tests

  • Maintained provider-free imports accepted all eighteen reviewed pages, with current-source invariants and dependency closure checks. Existing published pages remain unchanged.
  • Exact generated bytes, source blobs, complete independent semantic and native-language review receipts and active semantic exclusions checked for every added body.
  • git diff --check: pass.
  • Full unit, integration and strict documentation checks run in PR CI and must pass before merge. No heavy local suite ran.

AI assistance in the code (leave one; writing this description with AI is fine):

  • AI-generated (an agent wrote most of the diff): Codex prepared the generated-data imports and checked the validation results and independent reviews. Translation prose comes from the approved translation model.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Required full checks pass in CI before merge.
  • Generated translations retain their exact model output; no translated prose is edited by hand.
  • No migration, SDK, plugin, frontend or runtime interface changes.
  • English remains canonical and pending coverage remains explicit.
  • Public text contains no private evidence or deployment details.
  • Commits are signed off.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant