docs(terminology): retire the stale develop seed — one latest TERMINOLOGY.md

[LukasWodka]

develop still had the 40-line seed while main has the 184-line v2 (docs#61) — the divergence that twice caused a wrong 'secure environment vs workspace' read. This syncs develop's TERMINOLOGY.md to the v2 so there's one latest, not two.

Docs-only; safe to merge (docs exempt from the FR-gate).

---

Note

Low Risk
Single markdown file on the docs branch; no code, auth, or data paths affected.

Overview
Aligns develop with main on product vocabulary by replacing the old 40-line seed TERMINOLOGY.md with the full v2 glossary (docs#61), eliminating two conflicting “latest” copies that had already caused wrong reads on secure environment vs workspace.

The updated file marks itself authoritative for UI, docs, CLI, and skills; records secure environment (2026-07-12) as the on-prem term; expands tables for people, task taxonomy (16 tasks + layouts), training, models, FL, brand, CLI verbs, and engineering naming; adds a words to retire sweep tied to live code/UI drift; and lists open questions (Hub vs dashboard, owner label, model verb, etc.) with explicit note that renames follow decisions—not this PR alone.

Docs-only change — no runtime or API behavior.

^{Reviewed by Cursor Bugbot for commit 67dfdae. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 67dfdae. Configure here.}

[cursor]

Stale training-images repo name

Medium Severity

Section 9 proposes keeping the tracebloc-client repo name for training-execution images. That violates the decided canonical naming rule: the repo was renamed to tracebloc-engine, so the authoritative terminology file should not instruct people to keep the retired name.

 

^{Triggered by learned rule: Flag retired terminology — use decided canonical terms}

^{Reviewed by Cursor Bugbot for commit 67dfdae. Configure here.}

[cursor]

Edge rename allows client

Medium Severity

Words to retire maps user-facing edge / edge device to secure environment / client, including frontend copy. For on-prem deployment the decided canonical term is secure environment, not client, so listing client as a replacement target invites the retired term back into product UI.

 

^{Triggered by learned rule: Flag retired terminology — use decided canonical terms}

^{Reviewed by Cursor Bugbot for commit 67dfdae. Configure here.}