type-python 0.4.0__tar.gz → 1.0.0rc1__tar.gz

{type_python-0.4.0 → type_python-1.0.0rc1}/Cargo.lock

@@ -1779,7 +1779,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-binding"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "typepython-diagnostics",
  "typepython-syntax",
@@ -1787,7 +1787,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-checking"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "criterion",
  "proptest",
@@ -1802,7 +1802,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-cli"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "anyhow",
  "clap",
@@ -1835,7 +1835,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-config"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "serde",
  "thiserror",
@@ -1845,7 +1845,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-diagnostics"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "serde",
  "serde_json",
@@ -1853,7 +1853,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-emit"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "insta",
  "littrs-ruff-python-ast",
@@ -1866,7 +1866,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-graph"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "criterion",
  "typepython-binding",
@@ -1875,7 +1875,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-incremental"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "serde",
  "serde_json",
@@ -1887,7 +1887,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-lowering"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "criterion",
  "insta",
@@ -1902,7 +1902,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-lsp"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "anyhow",
  "criterion",
@@ -1925,7 +1925,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-project"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "anyhow",
  "glob",
@@ -1939,7 +1939,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-syntax"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "criterion",
  "littrs-ruff-python-ast",
@@ -1953,7 +1953,7 @@ dependencies = [
 
 [[package]]
 name = "typepython-target"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 dependencies = [
  "serde",
 ]

{type_python-0.4.0 → type_python-1.0.0rc1}/Cargo.toml

@@ -22,7 +22,7 @@ authors = ["unadlib"]
 edition = "2024"
 license = "MIT"
 rust-version = "1.94.0"
-version = "0.4.0"
+version = "1.0.0-rc.1"
 
 [workspace.dependencies]
 anyhow = "1"

{type_python-0.4.0 → type_python-1.0.0rc1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: type-python
-Version: 0.4.0
+Version: 1.0.0rc1
 Summary: A statically-typed authoring language that compiles to standard Python
 Author: unadlib
 License-Expression: MIT
@@ -40,16 +40,25 @@ Dynamic: license-file
 ---
 
 TypePython is a typed dialect of Python that compiles to standard `.py` + `.pyi`.
-It brings TypeScript-class ergonomics — `sealed` classes, exhaustive `match`,
+It brings author-time TypeScript-class ergonomics — `sealed` classes, exhaustive `match`,
 strict null checks, `unknown`, `interface`, `data class` — to a language whose
 output runs anywhere CPython runs.
 
-**No custom runtime. No per-checker plugin. No vendor lock-in.**
-
-> Status: **Core v1 Beta** (v0.4.0). Core syntax, config, `init`/`check`/`build`/
-> `clean`/`verify`, diagnostic code identity, and emitted `.py`/`.pyi` compatibility
-> are the stable Beta surfaces. LSP UX, adapter manifests, runtime validators, and
-> migration heuristics remain prototype/experimental.
+Those stronger checks are enforced while authoring `.tpy`; emitted artifacts
+remain standard Python and do not transfer every TypePython-only constraint to
+downstream checkers.
+
+**No custom runtime. No required per-checker plugin for emitted output. No vendor lock-in.**
+
+> Status: **Core v1.0 RC** (v1.0.0-rc.1). Core syntax, config, `init`/`check`/
+> `build`/`clean`/`verify`, Core checker semantics, diagnostic code identity,
+> and emitted `.py`/`.pyi` compatibility are the release-candidate surfaces.
+> Supported DX, Experimental opt-in, and Roadmap / prototype features remain
+> outside the Core v1.0 RC compatibility promise and are tracked separately in
+> the Experimental Feature Registry.
+> This is not a full product-wide v1.0 RC: editor UX, VS Code packaging,
+> `watch`, migration heuristics, and research slices remain outside the stable
+> v1.0 promise until their own gates are complete.
 > Bug reports and contributions are very welcome.
 
 ## Install
@@ -65,7 +74,9 @@ You now have `.typepython/build/` with `.py` + `.pyi` + `py.typed` ready for
 any Python interpreter, IDE, or downstream type checker.
 
 - **Wheels** are prebuilt for Windows AMD64, macOS x86_64, macOS arm64, and Linux x86_64.
-  Other platforms fall back to source and need Rust + `cargo`.
+  Other platforms fall back to source and need Rust + `cargo`. Wheels are tagged
+  `py3-none-<platform>` because the bundled Rust CLI is platform-specific while
+  the Python wrapper is ABI-independent.
 - **Python**: the package bridge supports 3.9+; generated projects target Python 3.10 through 3.14.
 
 ## See it in 15 lines
@@ -90,7 +101,9 @@ def evaluate(expr: Expr) -> int:
 ```
 
 `typepython build` lowers that to ordinary Python and writes a matching `.pyi`
-that any modern type checker can consume — no TypePython runtime required.
+that any modern type checker can consume — no TypePython runtime required. The
+exhaustiveness proof happens before emit; downstream tools see a normal Python
+class hierarchy.
 
 ## What you write vs. what ships
 
@@ -108,29 +121,43 @@ that any modern type checker can consume — no TypePython runtime required.
 
 ## Why not just mypy / pyright / PEP 695?
 
-| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy`** |
-| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :-------------------: |
+The comparison below is about `.tpy` authoring inside the package checked by
+TypePython. Emitted `.py` / `.pyi` remain standard Python typing, so external
+consumers do not automatically inherit TypePython-only constraints such as
+sealed exhaustiveness or `unknown` strictness.
+
+| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy` authoring** |
+| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :--------------------------------: |
 | `sealed class` + compiler-proved exhaustiveness         |      —      |       —        |       —       |          ✅           |
 | `unknown` — safe dynamic boundary, must narrow          |      —      |       —        |       —       |          ✅           |
 | `unsafe:` audit fence for `eval` / `exec` / `setattr`   |      —      |       —        |       —       |          ✅           |
 | First-class `interface` / `data class` / `typealias`    |    via      |     via        |    via        |     keyword           |
 | Inline generics `def f[T]` on **any** target ≥ 3.10     |     3.12+   |     3.12+      |     3.12+     |          ✅           |
 | `TypedDict` transforms (`Partial`, `Pick`, `Readonly`…) |      —      |       —        |       —       |          ✅           |
-| Output consumed by mypy / pyright / ty unmodified       |     N/A     |     N/A        |       ✅       |          ✅           |
+| Output consumed by mypy / pyright / basedpyright / ty unmodified | N/A | N/A | ✅ | ✅ |
 
 TypePython doesn't replace those checkers. It sits **one step earlier**: you
 author in `.tpy`, the compiler emits standard typed Python that those tools
 then consume normally.
 
+The strongest TypePython guarantees are author-time checks. Emitted artifacts
+remain standard Python: sealed exhaustiveness, `unknown` strictness, and
+`unsafe:` fences are enforced by TypePython during authoring, but external
+checkers see the portable `.py` / `.pyi` boundary. Carrying TypePython-only
+semantics across that boundary requires an opt-in sidecar, checker plugin, or
+TypePython-aware consumer.
+
 ## What you also get
 
 - **Rust-native, incremental compiler** — public-API fingerprints skip
   downstream rechecks when only a body changes.
 - **Full toolchain** — `init`, `check`, `build`, `watch`, `clean`, `verify`,
   `compat`, `api-diff`, `type-health`, `migrate`, `lsp`.
-- **LSP server** — hover, go to definition, references, rename, completions,
-  signature help, real-time diagnostics, and code-action quick fixes.
-  Bring your own LSP-capable editor (VS Code, Neovim, Helix, Sublime, Emacs).
+- **Supported DX LSP server** — hover, go to definition, references, rename,
+  completions, signature help, real-time diagnostics, and code-action quick fixes.
+  The repository includes a source-installable VS Code extension plus copy-paste
+  setup for Neovim, Helix, Sublime Text, and Emacs. Editor UX and extension
+  packaging are still outside the Core v1.0 RC compatibility promise.
 - **Standard, portable output** — emitted `.py` + `.pyi` work with mypy,
   pyright, and ty out of the box. PEP 561 `py.typed` is written automatically.
 - **Mixed projects** — `.tpy`, `.py`, and `.pyi` live in the same source tree.
@@ -151,6 +178,8 @@ typepython type-health --project . --fail-under 85
 These catch missing/stale `py.typed`, wheel ↔ build-tree drift, multi-checker
 portability gaps, public-API drift between releases, and runtime-annotation
 hazards for frameworks that introspect annotations.
+They validate the standard published surface; they do not make ordinary
+downstream `.py` checkers enforce TypePython-only facts.
 
 ## Documentation
 
@@ -165,6 +194,8 @@ hazards for frameworks that introspect annotations.
 - [Migration Guide](https://github.com/type-python/type-python/blob/main/docs/migration-guide.md)
 - [Framework Adapters](https://github.com/type-python/type-python/blob/main/docs/framework-adapters.md)
 - [Beta Readiness](https://github.com/type-python/type-python/blob/main/docs/beta-readiness.md)
+- [Feature Status](https://github.com/type-python/type-python/blob/main/docs/feature-status.md)
+- [Experimental Feature Registry](https://github.com/type-python/type-python/blob/main/docs/experimental-features.md)
 - [Language Spec v1](https://github.com/type-python/type-python/blob/main/docs/spec/language-spec-v1.md)
 
 ## Links

{type_python-0.4.0 → type_python-1.0.0rc1}/README-PyPI.md

@@ -11,16 +11,25 @@
 ---
 
 TypePython is a typed dialect of Python that compiles to standard `.py` + `.pyi`.
-It brings TypeScript-class ergonomics — `sealed` classes, exhaustive `match`,
+It brings author-time TypeScript-class ergonomics — `sealed` classes, exhaustive `match`,
 strict null checks, `unknown`, `interface`, `data class` — to a language whose
 output runs anywhere CPython runs.
 
-**No custom runtime. No per-checker plugin. No vendor lock-in.**
-
-> Status: **Core v1 Beta** (v0.4.0). Core syntax, config, `init`/`check`/`build`/
-> `clean`/`verify`, diagnostic code identity, and emitted `.py`/`.pyi` compatibility
-> are the stable Beta surfaces. LSP UX, adapter manifests, runtime validators, and
-> migration heuristics remain prototype/experimental.
+Those stronger checks are enforced while authoring `.tpy`; emitted artifacts
+remain standard Python and do not transfer every TypePython-only constraint to
+downstream checkers.
+
+**No custom runtime. No required per-checker plugin for emitted output. No vendor lock-in.**
+
+> Status: **Core v1.0 RC** (v1.0.0-rc.1). Core syntax, config, `init`/`check`/
+> `build`/`clean`/`verify`, Core checker semantics, diagnostic code identity,
+> and emitted `.py`/`.pyi` compatibility are the release-candidate surfaces.
+> Supported DX, Experimental opt-in, and Roadmap / prototype features remain
+> outside the Core v1.0 RC compatibility promise and are tracked separately in
+> the Experimental Feature Registry.
+> This is not a full product-wide v1.0 RC: editor UX, VS Code packaging,
+> `watch`, migration heuristics, and research slices remain outside the stable
+> v1.0 promise until their own gates are complete.
 > Bug reports and contributions are very welcome.
 
 ## Install
@@ -36,7 +45,9 @@ You now have `.typepython/build/` with `.py` + `.pyi` + `py.typed` ready for
 any Python interpreter, IDE, or downstream type checker.
 
 - **Wheels** are prebuilt for Windows AMD64, macOS x86_64, macOS arm64, and Linux x86_64.
-  Other platforms fall back to source and need Rust + `cargo`.
+  Other platforms fall back to source and need Rust + `cargo`. Wheels are tagged
+  `py3-none-<platform>` because the bundled Rust CLI is platform-specific while
+  the Python wrapper is ABI-independent.
 - **Python**: the package bridge supports 3.9+; generated projects target Python 3.10 through 3.14.
 
 ## See it in 15 lines
@@ -61,7 +72,9 @@ def evaluate(expr: Expr) -> int:
 ```
 
 `typepython build` lowers that to ordinary Python and writes a matching `.pyi`
-that any modern type checker can consume — no TypePython runtime required.
+that any modern type checker can consume — no TypePython runtime required. The
+exhaustiveness proof happens before emit; downstream tools see a normal Python
+class hierarchy.
 
 ## What you write vs. what ships
 
@@ -79,29 +92,43 @@ that any modern type checker can consume — no TypePython runtime required.
 
 ## Why not just mypy / pyright / PEP 695?
 
-| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy`** |
-| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :-------------------: |
+The comparison below is about `.tpy` authoring inside the package checked by
+TypePython. Emitted `.py` / `.pyi` remain standard Python typing, so external
+consumers do not automatically inherit TypePython-only constraints such as
+sealed exhaustiveness or `unknown` strictness.
+
+| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy` authoring** |
+| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :--------------------------------: |
 | `sealed class` + compiler-proved exhaustiveness         |      —      |       —        |       —       |          ✅           |
 | `unknown` — safe dynamic boundary, must narrow          |      —      |       —        |       —       |          ✅           |
 | `unsafe:` audit fence for `eval` / `exec` / `setattr`   |      —      |       —        |       —       |          ✅           |
 | First-class `interface` / `data class` / `typealias`    |    via      |     via        |    via        |     keyword           |
 | Inline generics `def f[T]` on **any** target ≥ 3.10     |     3.12+   |     3.12+      |     3.12+     |          ✅           |
 | `TypedDict` transforms (`Partial`, `Pick`, `Readonly`…) |      —      |       —        |       —       |          ✅           |
-| Output consumed by mypy / pyright / ty unmodified       |     N/A     |     N/A        |       ✅       |          ✅           |
+| Output consumed by mypy / pyright / basedpyright / ty unmodified | N/A | N/A | ✅ | ✅ |
 
 TypePython doesn't replace those checkers. It sits **one step earlier**: you
 author in `.tpy`, the compiler emits standard typed Python that those tools
 then consume normally.
 
+The strongest TypePython guarantees are author-time checks. Emitted artifacts
+remain standard Python: sealed exhaustiveness, `unknown` strictness, and
+`unsafe:` fences are enforced by TypePython during authoring, but external
+checkers see the portable `.py` / `.pyi` boundary. Carrying TypePython-only
+semantics across that boundary requires an opt-in sidecar, checker plugin, or
+TypePython-aware consumer.
+
 ## What you also get
 
 - **Rust-native, incremental compiler** — public-API fingerprints skip
   downstream rechecks when only a body changes.
 - **Full toolchain** — `init`, `check`, `build`, `watch`, `clean`, `verify`,
   `compat`, `api-diff`, `type-health`, `migrate`, `lsp`.
-- **LSP server** — hover, go to definition, references, rename, completions,
-  signature help, real-time diagnostics, and code-action quick fixes.
-  Bring your own LSP-capable editor (VS Code, Neovim, Helix, Sublime, Emacs).
+- **Supported DX LSP server** — hover, go to definition, references, rename,
+  completions, signature help, real-time diagnostics, and code-action quick fixes.
+  The repository includes a source-installable VS Code extension plus copy-paste
+  setup for Neovim, Helix, Sublime Text, and Emacs. Editor UX and extension
+  packaging are still outside the Core v1.0 RC compatibility promise.
 - **Standard, portable output** — emitted `.py` + `.pyi` work with mypy,
   pyright, and ty out of the box. PEP 561 `py.typed` is written automatically.
 - **Mixed projects** — `.tpy`, `.py`, and `.pyi` live in the same source tree.
@@ -122,6 +149,8 @@ typepython type-health --project . --fail-under 85
 These catch missing/stale `py.typed`, wheel ↔ build-tree drift, multi-checker
 portability gaps, public-API drift between releases, and runtime-annotation
 hazards for frameworks that introspect annotations.
+They validate the standard published surface; they do not make ordinary
+downstream `.py` checkers enforce TypePython-only facts.
 
 ## Documentation
 
@@ -136,6 +165,8 @@ hazards for frameworks that introspect annotations.
 - [Migration Guide](https://github.com/type-python/type-python/blob/main/docs/migration-guide.md)
 - [Framework Adapters](https://github.com/type-python/type-python/blob/main/docs/framework-adapters.md)
 - [Beta Readiness](https://github.com/type-python/type-python/blob/main/docs/beta-readiness.md)
+- [Feature Status](https://github.com/type-python/type-python/blob/main/docs/feature-status.md)
+- [Experimental Feature Registry](https://github.com/type-python/type-python/blob/main/docs/experimental-features.md)
 - [Language Spec v1](https://github.com/type-python/type-python/blob/main/docs/spec/language-spec-v1.md)
 
 ## Links

{type_python-0.4.0 → type_python-1.0.0rc1}/README.md

@@ -14,15 +14,16 @@
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License: MIT" /></a>
   <a href="https://www.python.org/"><img src="https://img.shields.io/badge/python-3.9%2B-blue.svg" alt="Python 3.9+" /></a>
   <a href="https://www.rust-lang.org/"><img src="https://img.shields.io/badge/built%20with-rust-orange.svg" alt="Built with Rust" /></a>
-  <a href="https://github.com/type-python/type-python/issues"><img src="https://img.shields.io/badge/status-Core%20v1%20Beta-blue.svg" alt="Core v1 Beta" /></a>
+  <a href="https://github.com/type-python/type-python/issues"><img src="https://img.shields.io/badge/status-Core%20v1.0%20RC-blue.svg" alt="Core v1.0 RC" /></a>
 </p>
 
 <p align="center">
   TypePython is a typed dialect of Python that compiles to standard <code>.py</code> + <code>.pyi</code>.<br/>
-  It brings TypeScript-class ergonomics — <code>sealed</code> classes, exhaustive <code>match</code>,
+  It brings author-time TypeScript-class ergonomics — <code>sealed</code> classes, exhaustive <code>match</code>,
   strict null checks, <code>unknown</code>, <code>interface</code>, <code>data class</code> —
   to a language whose output runs anywhere CPython runs.<br/>
-  <em>No custom runtime. No per-checker plugin. No vendor lock-in.</em>
+  Those stronger checks are enforced while authoring <code>.tpy</code>; emitted artifacts remain standard Python and do not transfer every TypePython-only constraint to downstream checkers.<br/>
+  <em>No custom runtime. No required per-checker plugin for emitted output. No vendor lock-in.</em>
 </p>
 
 ---
@@ -48,7 +49,7 @@ def evaluate(expr: Expr) -> int:
     # Add a fourth subclass and TypePython tells you exactly where to update.
 ```
 
-`typepython build` lowers that to ordinary Python and writes a matching `.pyi` that any modern type checker can consume:
+`typepython build` lowers that to ordinary Python and writes a matching `.pyi` that any modern type checker can consume. The exhaustiveness proof happens before emit; downstream tools see a normal Python class hierarchy:
 
 ```python
 # .typepython/build/app/expr.py        # runs on stock CPython, no TypePython runtime
@@ -72,6 +73,7 @@ typepython build --project .
 You now have `.typepython/build/` with `.py` + `.pyi` + `py.typed` ready for any Python interpreter, IDE, or downstream type checker.
 
 > **Wheels** are prebuilt for Windows AMD64, macOS x86_64, macOS arm64, and Linux x86_64. Other platforms fall back to source and need Rust + `cargo`.
+> Wheels are tagged `py3-none-<platform>` because the bundled Rust CLI is platform-specific while the Python wrapper is ABI-independent.
 > **Python**: the package bridge supports 3.9+; generated projects target Python 3.10 through 3.14.
 
 ## What you actually write vs. what ships
@@ -94,23 +96,24 @@ Full lowering map: [`docs/interop.md`](docs/interop.md) · syntax tour: [`docs/s
 
 Python's type story has gotten genuinely good. TypePython exists for the gaps that source-only annotations still can't close.
 
-| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy`** |
-| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :-------------------: |
+The comparison below is about `.tpy` authoring inside the package checked by TypePython. Emitted `.py` / `.pyi` remain standard Python typing, so external consumers do not automatically inherit TypePython-only constraints such as sealed exhaustiveness or `unknown` strictness.
+
+| Capability                                              | mypy strict | pyright strict | PEP 695 `.py` | **TypePython `.tpy` authoring** |
+| ------------------------------------------------------- | :---------: | :------------: | :-----------: | :--------------------------------: |
 | `sealed class` + compiler-proved exhaustiveness         |      —      |       —        |       —       |          ✅           |
 | `unknown` — safe dynamic boundary, must narrow          |      —      |       —        |       —       |          ✅           |
 | `unsafe:` audit fence for `eval` / `exec` / `setattr`   |      —      |       —        |       —       |          ✅           |
 | First-class `interface` / `data class` / `typealias`    |    via      |     via        |    via        |     keyword           |
 | Inline generics `def f[T]` on **any** target ≥ 3.10     |     3.12+   |     3.12+      |     3.12+     |          ✅           |
 | `TypedDict` transforms (`Partial`, `Pick`, `Readonly`…) |      —      |       —        |       —       |          ✅           |
-| Framework shapes beyond `dataclass_transform`           |   plugin    |    plugin      |       —       |    declarative        |
-| Output consumed by mypy / pyright / ty unmodified       |     N/A     |     N/A        |       ✅       |          ✅           |
+| Output consumed by mypy / pyright / basedpyright / ty unmodified | N/A | N/A | ✅ | ✅ |
 
 TypePython doesn't replace those checkers. It sits **one step earlier**: you author in `.tpy`, the compiler emits standard typed Python that those tools then consume normally.
 
 ## Who this is for
 
 - **Python developers who envy TypeScript.** You want sealed unions, exhaustiveness, `unknown`, strict nulls, and `interface` without inventing five mypy plugins to get there.
-- **Library authors.** You publish a typed package and need `py.typed`, `.pyi`, wheel/sdist contents, and public-API drift to all stay in sync. `verify`, `compat`, and `api-diff` are built for that.
+- **Library authors.** You publish a standard typed package and need `py.typed`, `.pyi`, wheel/sdist contents, and public-API drift to all stay in sync. TypePython-only safety applies inside the author package checked by TypePython; downstream users receive portable Python typing unless they also opt into TypePython-aware metadata or checking.
 - **Application teams adopting types gradually.** Mix `.tpy`, `.py`, and `.pyi` in the same source tree; baseline existing debt; gate new debt with type-budgets.
 - **Framework authors** (advanced, currently prototype). Describe your runtime-generated shape **once**, declaratively, and stop maintaining one plugin per checker.
 - **Platform / typing owners.** Centralize multi-checker policy, dependency type-health checks, and framework adapters in CI.
@@ -139,7 +142,7 @@ Full reference: [`docs/cli-reference.md`](docs/cli-reference.md).
 
 ## Editor support
 
-`typepython lsp --project .` is a stdio LSP server with:
+`typepython lsp --project .` is a supported DX stdio LSP server with:
 
 - real-time diagnostics, hover, go to definition, references, rename
 - completions, signature help
@@ -147,25 +150,30 @@ Full reference: [`docs/cli-reference.md`](docs/cli-reference.md).
 - code actions for migration and portability fixes
 - project commands (`migrate`, `compat`, `type-health`, emitted-output preview, `Any` / `Unknown` source lookup)
 
-There is **no official editor extension yet** — any LSP-capable editor (VS Code, Neovim, Helix, Sublime Text, Emacs) can launch the server. Setup snippets are in [`docs/lsp.md`](docs/lsp.md).
+The repository includes a source-installable VS Code extension under
+[`editors/vscode`](editors/vscode). Neovim, Helix, Sublime Text, and Emacs can
+launch the server with copy-paste LSP snippets. Editor UX, command names, and
+extension packaging are not part of the Core v1.0 RC compatibility promise yet.
+Setup snippets are in [`docs/lsp.md`](docs/lsp.md), and the promotion gate is
+tracked in [`docs/dx-stability.md`](docs/dx-stability.md).
 
 ## Standard, portable output — by design
 
 TypePython makes one strong promise about its output:
 
-> Emitted `.py` and `.pyi` contain **only standard Python typing constructs**. Nothing TypePython-specific leaves the build directory.
+> Emitted `.py` and `.pyi` use **standard Python syntax** and **standard Python typing constructs**. TypePython-specific metadata, when emitted, appears only as comments and is not required by CPython or downstream type checkers.
 
-A few stronger guarantees are author-time only — they live in your `.tpy` source and don't survive into the consumer-facing artifacts:
+The stronger guarantee is for the package while it is authored and checked by TypePython. A few facts intentionally degrade to standard typing surfaces in consumer-facing artifacts:
 
-| TypePython author-time guarantee   | At the boundary                                |
-| ---------------------------------- | ---------------------------------------------- |
-| `unknown` requires narrowing       | lowers to `object` in `.pyi`                   |
-| `sealed class` exhaustiveness      | external checkers see a normal class           |
-| `unsafe:` audit fence              | erased; lowered to valid Python                |
-| `TypedDict` transforms             | expanded to standard `TypedDict` shapes        |
-| effect, taint, and witness facts   | checked at author-time; erased or sidecar-only |
+| TypePython author-time fact         | Stability status                | At the boundary                                |
+| ----------------------------------- | ------------------------------- | ---------------------------------------------- |
+| `unknown` requires narrowing        | Stable Core v1                  | lowers to `object` in `.pyi`                   |
+| `sealed class` exhaustiveness       | Stable Core v1                  | external checkers see a normal class           |
+| `unsafe:` audit fence               | Stable Core v1                  | erased; lowered to valid Python                |
+| `TypedDict` transforms              | Stable Core v1                  | expanded to standard `TypedDict` shapes        |
+| effect, taint, and witness facts    | Roadmap / prototype             | checked at author-time; erased or sidecar-only |
 
-This trade is intentional: **you get stronger checks while authoring; consumers get clean, portable Python they can read with mypy, pyright, ty, IDEs, and any PEP 561 tool**. See [`docs/interop.md`](docs/interop.md) and [`docs/author-time-semantics.md`](docs/author-time-semantics.md).
+This trade is intentional: **the author package gets stronger checks before publish; consumers get clean, portable Python they can read with mypy, pyright, basedpyright, ty, IDEs, and any PEP 561 tool**. Carrying TypePython-only semantics across that boundary would require an opt-in sidecar, checker plugin, or TypePython-aware consumer. See [`docs/interop.md`](docs/interop.md), [`docs/feature-status.md`](docs/feature-status.md), and [`docs/author-time-semantics.md`](docs/author-time-semantics.md).
 
 ## For library and framework authors
 
@@ -181,7 +189,7 @@ typepython api-diff    dist/previous.whl .typepython/build
 typepython type-health --project . --fail-under 85
 ```
 
-These catch missing/stale `py.typed`, wheel ↔ build-tree drift, multi-checker portability gaps, public-API drift between releases, and runtime-annotation hazards for frameworks that introspect annotations.
+These catch missing/stale `py.typed`, wheel ↔ build-tree drift, multi-checker portability gaps, public-API drift between releases, and runtime-annotation hazards for frameworks that introspect annotations. They validate the standard published surface; they do not make ordinary downstream `.py` checkers enforce TypePython-only facts.
 
 **Framework shape adapters** *(prototype tier)* — describe a runtime-generated API once, lower it into `.pyi` declaratively, and skip per-checker plugins:
 
@@ -198,23 +206,33 @@ class BaseModel: ...
 
 ## Project status
 
-TypePython is **Core v1 Beta** (v0.4.0). The Beta claim is deliberately scoped: Core syntax,
-configuration, `init`/`check`/`build`/`clean`/`verify`, diagnostic code identity, and emitted
-`.py`/`.pyi` compatibility are the stable surfaces. DX and Experimental features ship for feedback
-but are not compatibility-stable. See [`docs/beta-readiness.md`](docs/beta-readiness.md).
+TypePython is **Core v1.0 RC** (v1.0.0-rc.1). The release-candidate claim is deliberately scoped:
+Core syntax and checker semantics, configuration, `init`/`check`/`build`/`clean`/`verify`,
+diagnostic code identity, and emitted `.py`/`.pyi` compatibility are the release-candidate
+surfaces. Supported DX, Experimental opt-in, and Roadmap / prototype features ship for feedback but
+are not compatibility-stable. See
+[`docs/beta-readiness.md`](docs/beta-readiness.md),
+[`docs/feature-status.md`](docs/feature-status.md), and
+[`docs/experimental-features.md`](docs/experimental-features.md).
+
+This is not a full product-wide v1.0 RC. It does not promote editor UX, VS Code packaging, `watch`,
+migration heuristics, or research slices to stable v1.0 commitments; those remain Supported DX,
+Experimental opt-in, or Roadmap / prototype until their own gates are complete.
 
 The breakdown:
 
-| Tier             | What's there                                                                                                                                                                                                                                                                                                                                                       |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Core v1 Beta** | `.tpy` Core syntax; project discovery and `typepython.toml` Core config; `init`, `check`, `build`, `clean`, `verify`; diagnostic code identity; `.py` lowering and `.pyi` generation with no mandatory TypePython runtime.                                                                           |
-| **DX prototype** | `watch`, LSP UX details, `compat`, `api-diff`, `type-health`, `migrate`, checker portability profiles, type budgets, and migration dashboards.                                                                                                                                                        |
-| **Experimental** | framework adapter manifests, runtime validators, shape projection beyond `TypedDict`, conditional return syntax, sync/async dual emit paths, notebook ingestion, and other deferred research tracks.                                                                                                                                                                  |
+| Tier | What's there |
+| ---- | ------------ |
+| **Stable Core v1** | `.tpy` Core syntax; Core checker semantics for TypePython-checked author packages, such as sealed exhaustiveness, `unknown` narrowing, `unsafe:` fences, and supported `TypedDict` transforms; project discovery and `typepython.toml` Core config; `init`, `check`, `build`, `clean`, `verify`; diagnostic code identity; `.py` lowering and `.pyi` generation with no mandatory TypePython runtime. |
+| **Supported DX, non-stable** | `watch`, LSP UX details, `compat`, `api-diff`, `type-health`, `migrate`, checker portability profiles, type budgets, and migration dashboards. |
+| **Experimental opt-in** | runtime validators, shape projection beyond `TypedDict`, conditional return syntax, pass-through `.py` inference, sync/async dual emit paths, and other opt-in research slices. |
+| **Roadmap / prototype** | framework adapter manifests and SDK details, effect/capability rows beyond `unsafe:`, taint facts, validator witnesses, notebook ingestion, and other deferred research tracks. |
 
 Conformance and diagnostic-coverage reports are checked into the repo: [`docs/conformance-report.md`](docs/conformance-report.md), [`docs/diagnostic-test-coverage.md`](docs/diagnostic-test-coverage.md).
 
-> **Beta does not mean all roadmap features are stable.** It means the Core v1 authoring and emit
-> contract is ready for serious trial use while DX and Experimental surfaces continue to evolve.
+> **Core v1.0 RC does not mean all roadmap features are stable.** It means the Core v1 authoring
+> and emit contract is in release-candidate status while DX and Experimental surfaces continue to
+> evolve.
 
 ## Configuration
 
@@ -233,6 +251,9 @@ strict_nulls = true
 [emit]
 emit_pyi = true
 no_emit_on_error = true
+
+[experimental]
+accepted_features = []          # add feature ids before enabling unstable gates
 ```
 
 Full reference: [`docs/configuration.md`](docs/configuration.md).
@@ -248,7 +269,7 @@ Full reference: [`docs/configuration.md`](docs/configuration.md).
 | [`config-loader/`](examples/config-loader/) | `unknown`, unsafe boundaries, trust-boundary parsing patterns |
 | [`event-system/`](examples/event-system/)   | sealed events, interfaces, data classes, generics             |
 | [`showcase/`](examples/showcase/)           | multi-file feature showcase                                   |
-| [`research-roadmap-demo/`](examples/research-roadmap-demo/) | effect rows, Shape projection, restricted evaluator, taint, validator witnesses |
+| [`research-roadmap-demo/`](examples/research-roadmap-demo/) | Roadmap / prototype slices only; not a Core v1 stability claim |
 
 Framework and downstream-checker fixtures: [`test-fixtures/downstream-checkers/`](test-fixtures/downstream-checkers/).
 
@@ -289,7 +310,10 @@ Full guide: [`docs/migration-guide.md`](docs/migration-guide.md).
 | You're adopting it in an existing codebase   | [Migration Guide](docs/migration-guide.md)       |
 | You're a framework author                    | [Framework Adapters](docs/framework-adapters.md) |
 | You're evaluating Beta stability             | [Beta Readiness](docs/beta-readiness.md)         |
+| You're checking feature stability            | [Feature Status](docs/feature-status.md)         |
+| You're checking experimental gates           | [Experimental Feature Registry](docs/experimental-features.md) |
 | You want the crate map / pipeline diagram    | [Architecture](docs/architecture.md)             |
+| You're tracking post-RC refactor debt        | [Maintainability Plan](docs/maintainability-plan.md) |
 | You're evaluating the P0-P4 research slices  | [Author-Time Semantics](docs/author-time-semantics.md) |
 | You're sending a PR                          | [Contributing](docs/contributing.md)             |
 | You have a quick question                    | [FAQ](docs/faq.md)                               |

{type_python-0.4.0 → type_python-1.0.0rc1}/crates/typepython_binding/src/binding_impl.rs

@@ -663,7 +663,7 @@ fn bind_named_block(
             is_final: member.is_final,
             is_class_var: member.is_class_var,
             bases: Vec::new(),
-            type_params: Vec::new(),
+            type_params: bind_type_params(&member.type_params),
         }
     }));
     declarations