Skip to content

docs: align migration status and rollout boundary #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
swernerx merged 1 commit into from
Aug 17, 2026
Merged

docs: align migration status and rollout boundary #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@
> [`microsoft/typescript-go`](https://github.com/microsoft/typescript-go), not
> an official Microsoft or TypeScript project. The experiment explores a small,
> stable interface for attaching TypeScript semantic facts to source code. See
> [RFC 0001](rfcs/0001-semantic-facts-kernel.md) for the proposed direction.
> [RFC 0001](rfcs/0001-semantic-facts-kernel.md) for the accepted direction and
> its current migration boundary.

The accepted semantic-facts boundary is exposed by the experimental
[`tsfacts`](docs/tsfacts-protocol.md) JSON Lines command. It currently provides
Expand All @@ -21,6 +22,16 @@ compatibility boundary and current exclusions are tracked in the
[migration contract](docs/porting/migration-contract.md), and durable
implementation choices are recorded in [ADRs](docs/adr/README.md).

## Current migration status

The occurrence-to-OXC attachment path and the independent Rust primitive/literal
producer are implemented and exercised by deterministic Go-versus-Rust shadow
gates. The controlled rollout evidence records exact agreement for the current
supported corpus, but Rust is not a production semantic authority: the Go
checker remains the serving implementation and fallback. See [ADR-0020](docs/adr/0020-keep-primitive-literals-shadow-only-after-dual-run.md)
for the remaining blockers and the [rollout evidence](docs/evidence/primitive-literal-rollout-2026-08-17.json)
for the measured boundary.

# TypeScript 7

[Not sure what this is? Read the announcement post!](https://devblogs.microsoft.com/typescript/typescript-native-port/)
Expand Down
6 changes: 3 additions & 3 deletions docs/porting/migration-contract.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
evidence justifies pruning.
- **Authority:** This repository may implement, test, and merge the adapter and
its conformance corpus. Replacing checker categories with another backend
requires the compatibility threshold in ADR-0016 and fresh differential
requires the replacement checklist in ADR-0020 and fresh differential
evidence from an independent semantic producer.

## Equivalence boundary
Expand Down Expand Up @@ -117,8 +117,8 @@ authorize production routing.
4. The complete repository test suite passes without reduced test counts.
5. Format and lint checks pass.
6. CI passes on the upstream-supported matrix.
7. Phase 0 meets every acceptance criterion in RFC 0001 before that RFC becomes
Accepted.
7. RFC 0001 remains Accepted, with its current evidence and limitations kept in
sync with the ADR index and checked-in rollout artifacts.
8. `./internal/oxc_reference/run-evidence.sh --output <path>` produces stable
repeated observations and passes ADR-0016's occurrence/attachment gate.
9. `./internal/oxc_reference/run-conformance.sh --output <path>` emits the
Expand Down