Skip to content

Reconcile module inventory installation and adoption #151

Description

@marcinpsk

Parent

#144

What to build

Move module inventory assessment, parent-first installation, selected and branch installation, component adoption, and endpoint binding into reconciliation. Preserve module configuration as a separate domain.

Acceptance criteria

  • Module inventory assessment reports current, proposed, and blocked rows through reconciliation.
  • Inventory identity, hierarchy, current mapping rules, ignore rules, and VC placement preserve their behavior.
  • Parent modules install before children and newly created bays are resolved from current state.
  • Single, selected, and branch installation use explicit operations and structured outcomes.
  • Existing component adoption preserves eligible object identities and applies current permission rules.
  • Interface and console endpoint creation or binding is represented in the plan and outcomes.
  • Current locks, rollback behavior, and partial-group semantics remain intact.
  • Module rule, module-type, and bay-template configuration remain outside reconciliation.
  • Synchronous and background installation paths use the same implementation.
  • Old assessment and install/adopt implementations covered by this slice are removed.
  • Real hierarchy, adoption, VC, permission, concurrency, cache, and large-inventory tests pass.

Blocked by

  • Reconcile base interfaces and bulk relationships.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentReady for an implementation agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions