Skip to content

P02: import selected foreign Matrices before publishing new teams #3072

Closed

Description

@mblua

Parent: #3068. Phase P02, design-bearing. Owner: ac-dev-rust-v5. Dependencies: P01 landed in main (verify native linkage and merge ancestry).

Frozen specification

Canonical plan v2: D:/0_repos/AgentsCommander_iac/.ac/plans/3068-cross-project-agent-copy/plan-v2-cross-project-agent-copy.md
Plan-SHA256: 664D6CD1FB4EC3FD0E63E24514F0510E85ED2B66C1A2616A187F4916A9F9E9BF
Phase: D:/0_repos/AgentsCommander_iac/.ac/plans/3068-cross-project-agent-copy/P02-v2-create-team-ipc.md
Phase-SHA256: 9ED82885109FF9BFB8243BD0D15B971BDBEC3946B9D1E70405EB46288C78B459

Scope and acceptance

Implement frozen P02 in src-tauri/src/commands/entity_creation.rs only after P01 lands. Add optional agentSources to create_team and optional destination project plus projectPath/isLocal discovery response. Preserve existing local callers and portable persisted refs. Validate all sources and collisions before reserving/copying, use the P01 capability in a blocking worker, then normalize destination refs and exclusively publish team config per plan without overwriting racing config/conventions. Preserve sources, external changes and existing refresh. Add real-core integration tests for identity binding, local/foreign flows, alias/homonym cases, batch failures and deterministic exclusive-publication collisions. Remove the P01 temporary dead_code attributes. Rust compilation/tests belong to shipper.

Delivery and validation

Follow the phase's complete frozen commands and acceptance criteria from a cold start. Use synthetic Matrices only; no real private agent state. No dependencies, lockfiles, workflows, release/version bump or final distributable build. One branch/PR per phase, sequential delivery; branch must start from synchronized main after dependencies merge. Grinch review and applicable exact-head CI required, primary checkout kept on that branch while CI runs. Use existing ci:full label at PR creation for relevant cross-platform/frontend checks. The PR closes only this child; #3068 closes after all three phases and integrated validation. User explicitly authorized implementation with “avanza”; standing exact-version consensus authorization applies. All five original participants approved the same v2 digest set; no v1 approvals transferred.

Activity

  1. added 2 commits that reference this issue on Oct 17, 2026
  2. mblua commented on Oct 17, 2026

    @mblua
    OwnerAuthor

    Delivered P02 via PR #3082, merged at 2026-10-17T23:50:16Z.
    Merge/main SHA: e86896d. Reviewed/tested PR head: b7033fb.

    create_team now accepts optional source identity, validates and copies foreign Matrices before exclusive team publication, preserves cumulative provenance and local-call compatibility, and rolls back only owned unchanged output. Discovery reports canonical project identity/locality. The frontend consumer remains the next phase.

    Evidence: both independent code/integration reviews PASS; local Rust format/check/strict Clippy/cognitive wrapper, all 29 focused tests, 9 layering tests, full suite 6717 passed/0 failed/32 ignored. PRE/POST pairs and SCCs unchanged. Exact-head CI run39076334013 attempt2 SUCCESS; all required/triggered checks green, reconciled against ruleset15279066.
    The initial ProjectPanel frontend assertion failure did not reproduce in the one authorized same-head recurrence; original logs retained, cause unknown. Earlier lost local execution receipt is likewise preserved as UNKNOWN, with successful recovery and later independent exact-head validation recorded.

    Incoming Settings/container UI (#3077) and message archive (#3090) deltas were independently classified as unrelated and documented on the PR. Inherited Markdown line breaks in upstream release documentation remain explicitly recorded; P02-owned whitespace checks passed.

    Post-merge cleanup verified: clean main equals origin/main at the merge SHA; feature local/remote/tracking refs removed. The feature fetch refspec added by the requested git-chequear-rama-principal skill was removed before the post-deletion fetch, preserving main's refspec.
    No final distributable build was requested.

    Epic #3068 remains open. Remaining child: #3073/P03, New Team labels and source-identity payload, starting after the required safe handoff/clear and per-phase cold gate. Frozen plan v2 and approved mapping are unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdeveloped-windowsDeveloped on Windows.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions