Documentation progress
This commit is contained in:
parent
94c49ac5bd
commit
5cc5612f4e
14 changed files with 244 additions and 814 deletions
|
|
@ -9,6 +9,14 @@ Rules for keeping it useful:
|
|||
|
||||
## Remaining TODOs
|
||||
|
||||
### Apply-Class-Layout Schema Parity
|
||||
|
||||
- Missing capability: reliable minimal-payload use of `apply_class_layout(...)` during live class-lift batches.
|
||||
- Current fallback: create the class namespace and provisional structs directly through live `run_write_script(...)`, then defer any later class-binding or per-method typing work.
|
||||
- Why it matters: the first `EntityDispatchEntry` pilot batch reached the point where the class shell and provisional datatypes existed, but the endpoint still rejected the bind attempt with an undocumented required `methods` property even though the local workflow only needed `class_path`, `instance_struct`, and `vtable_struct`.
|
||||
- Proposed MCP behavior: `apply_class_layout(...)` should accept a true minimal bind payload when no method list is being applied, or else the bridge/schema should expose the `methods` field explicitly and treat an omitted list as empty instead of a validation error.
|
||||
- Latest status (2026-04-07): live `CRUSADER.EXE` class-lift pass for `Remorse::EntityDispatchEntry` succeeded via `run_write_script(...)`, creating the class shell plus `/Remorse/EntityDispatchEntryBase` and `/Remorse/EntityDispatchEntryVtable`. The only failed step in that batch was the direct `apply_class_layout(...)` call, which rejected the payload before any class work ran.
|
||||
|
||||
### Class-Lift Typing Live Parity
|
||||
|
||||
- Missing capability: end-to-end live-session parity for storage-aware `this` typing on 16-bit NE methods whose current storage does not match the default pointer storage the binder would choose.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue