Dagger Module Manifest v2: remaining design issues

module-manifest-v2-remaining-issues.md

Module Manifest v2: Review Status

Review baseline: future/module-manifest-v2.md at fa99a6039.

No open item from the previous engine-side review remains.

Previous issue	Resolution
Entrypoint construction	Each driver has an explicit construction rule.
Call routing	Constructors use the owning type and an empty function name. Object functions use their original names.
currentNode	The engine keeps the target receiver across the entrypoint call and nested clients.
Module contexts	Entrypoint and dispatch schemas remain separate because module serving is client-specific.
Main-object installation	The design has no main object. The engine exposes the only object constructor under the module name.
Type identity	Name-only references bind by type kind and original name.
Cache identity	Existing Dagger call identity controls caching.
Source identity	Recursive driver cycles compare resolved entrypoint Directory IDs.

The rewritten contract needs a new engine-side review. The previous review does not cover the constructor-based type model.

Changelog

• Mark currentNode propagation as resolved.
• Record the internal target-receiver context rule.
• Update the review baseline to d9071a13e.

Changelog

• Replace the main-object design with constructor-bearing TypeDefs.
• Mark all items from the previous review as resolved or removed.
• Set fa99a6039 as the new review baseline.