Codex TypeScript MCP Glossary

Synthesized from the closed grill on 2026-09-28. The grill log is the decision trail. This page does not claim implementation.

Canonical terms reused

The capability reuses existing canonical terms without change: Pack, Baseline, Registry, Installed Record, Recorded Shape, Built Artifact, Authored Artifact, Software Scope, Effective Lint Policy. See the Registry Baseline Glossary and the Managed Lint Glossary.

Working labels (parked, not canonical)

Glossary Q21 was parked at closure. These labels are used in the architecture and spec for clarity; they are not accepted canonical terms.

• Compiler Project: the source program and options selected by one tsconfig.json. Avoid: package folder, workspace, Software Scope.
• Tool Runtime: the pinned Typegraph installation and its exact dependency graph on one machine. Avoid: project compiler, lint toolchain.
• Semantic Session: one live Typegraph process answering for one Compiler Project in one worktree. Avoid: installation, registration, an approved call.

Relationship: a Semantic Session uses one Tool Runtime to answer about one Compiler Project. A Software Scope may span several Compiler Projects.

Axioms

• Pack is the only selection unit; detection proposes, never selects (C4).
• Semantic reads never replace format, lint or typecheck evidence (C2).
• Installed, registered, probe-passing and answered are four distinct facts (Q18).
• "Compatible" means the bundled compiler loads the project; it is not a version-string match (Q16).
• "Fresh" covers ordinary source edits only; tsconfig, dependency and branch changes need a new session (Q17).
• "LSP" is an umbrella label; the enabled tools use the compiler API, not language-server hover.

Excluded from this capability

Other languages and harnesses; semantic mutations; graph and Effect diagnostics; LSP hover; an HI router server; automatic recovery; runtime pruning; changes to global Codex approval policy.