48f108a58a
* docs: align resolution architecture and roadmap * docs: add language ingestion gap inventories * test: audit receiver gap targets and coverage Check exact declaration IDs, expose the Dart await wrong-owner edge, and execute previously excluded C++, Rust, PHP, Dart and Vue shapes. Refresh the baseline and all language inventories from fresh measurements; call-drop counts remain unchanged. * docs: focus roadmap and shorten project README Keep the resolution roadmap limited to future work and acceptance criteria. Move detailed editor, CLI, MCP, deployment and wiki instructions into linked guides, preserve their command examples, and correct stale onboarding claims. * docs: correct setup and audit descriptions --------- Co-authored-by: Gergo Magyar <gergomagyar0@gmail.com>
4 KiB
Kotlin Ingestion Gaps
Audited on 2026-10-23 with freshly built production sources at c35806d24 and
the accompanying benchmark changes. See the measurement audit
for commands, target checks, exclusions and test limits. Historical reports below
remain separate from freshly measured receiver cases; broader ingestion is not
exhaustively assessed.
Receiver shape snapshot
States below come from baseline.json. The harness defines each spelling and its N/A reason. RESOLVES requires the exact expected declaration ID and no same-named call to a different owner. WRONG-TARGET records incorrect edges.
| Shape | Recorded state | Expression or exclusion |
|---|---|---|
plainChain |
RESOLVES | svc.getUser().save() |
plainDeepChain |
RESOLVES | svc.getUser().address.save() |
optionalChain |
RESOLVES | svc?.getUser()?.save() |
nonNullAssert |
RESOLVES | svc!!.getUser().save() |
awaitParen |
RESOLVES | (svc.getUserAsync()).save() |
explicitTypeArgs |
RESOLVES | svc.getTyped<User>().save() |
indexElement |
RESOLVES | repos[0].save() |
fieldReceiverCall |
RESOLVES | this.repo.save() |
decoratedReceiverBase |
N/A | Kotlin this carries no type decoration. |
decoratedFieldType |
RESOLVES | this.repo?.save() |
Every applicable shape in this row resolves. Separate qualified-factory controls retain conservative ownership boundaries: inherited receivers need re-established bases and canonical MRO evidence; companion fallback requires captured proof that the companion header has no supertype. This is not a complete build-system classpath model.
Planning candidates
| ID | Evidence | Gap or boundary | Next planning step and acceptance |
|---|---|---|---|
| KOTLIN-01 | Documented boundary | Complete companion inheritance is outside the delivered factory fallback. | Reproduce a bounded inherited-companion case before extending it. Keep unknown bases and shadowed factories unresolved and preserve worker/cache ownership evidence. |
| KOTLIN-02 | Coverage audit | The passing matrix does not measure every package-qualified factory spelling. | Retain the identifier, implicit-receiver and shadow-boundary suites; identify a concrete missing case before proposing broader inference. |
Code and regression entry points
- Language provider directory.
- Scope resolver.
- kotlin-qualified-factory-implicit-receivers.test.ts.
- kotlin-qualified-factory-type-ownership.test.ts.
- kotlin-qualified-factory-identifier-review.test.ts.
Evidence details: receiver baseline notes and current roadmap.