Repository navigation
feat: preserve cross-project agents in New Team (refs #3073) - #3102
Conversation
|
Step 9.5 base-drift review: target advanced from integrated Incoming paths:
There is no overlap with P03's seven frontend paths and no changed existing command used by New Team. The delta changes no frontend source, manifest, lockfile, workflow or relevant build configuration. Reviewers checked symbols/call paths rather than inferring safety from filenames; merge-tree is conflict-free. Local evidence remains valid for the exact PR head. The later main Rust graph belongs to main's own changes; no P03 Rust or structural delta is introduced. Required and triggered PR checks must still pass before merge. |
|
CI run 39089324848, attempt 1, on exact head The complete original frontend log and run metadata are preserved. This is not the local Node26 storage-hook failure and no debt classifier accepted it. The failing test and ProjectPanel source are unchanged by P03, but shared imports mean that fact alone does not prove the cause is unrelated. No root cause or flaky classification is claimed. Under the bounded recurrence rule, one rerun of only failed job 117562485792 was requested on the same SHA and configured conditions. No source, test, environment, runner, workflow or threshold changed. Other green jobs are reused. Merge remains blocked until the actual rerun and every required/applicable triggered check are green. The earlier PR run 39089324334 was cancelled when superseded by the full-tier run; its unexpanded matrix placeholders are retained as historical cancelled-run entries, not successful checks. Their corresponding concrete jobs in the full run completed successfully. |
|
|
Stale-base triage for target advancement from Incoming paths:
The ten incoming files (418 additions/352 deletions) share no path with P03's seven files and do not use its changed symbols. The shared IPC/type additions are optional and additive; incoming consumers use unchanged types/APIs. The two ProjectPanel hunks only pass The delta digest is Retaining the exact validated feature head and its CI under the documented unrelated-delta landing policy; no branch update or CI restart. The strict freshness rule does not justify unnecessary integration under that policy's admin-merge path. This does not claim green CI or waive any required/applicable check: all must pass on this exact head before merge. |
|
Final landing triage: subsequent target advancement from Four incoming paths (501 additions/3 deletions): Delta digest The unchanged validated head |



New Team retains each selected agent's source project through the IPC request, so the landed import backend copies the selected foreign Agent Matrix rather than resolving a destination homonym. Foreign agents show a dimmed
@sourceProjectsuffix; destination-local agents show their name alone.The optional IPC arguments preserve existing callers. The modal rejects missing identity and duplicate portable references before creation, preserves source-bound coordinator/repository assignments, and keeps existing context alerts. The real discovery/store test verifies waiting and one close while preserving the existing best-effort reload policy: a discovery failure can still leave the view stale.
Validated head:
dc4b998cd54772e73d3ac9cace9e1f188265fdd6, integrated withmainatf08b2734dbe60a40f3341f7d27b727d8e10ecc0e. The merge had no conflicts or manual source edits. The target-relative change remains the seven approved frontend/type/test paths (282 additions, 12 deletions).Validation:
a704376702f72dd6bee7aa6b7e38050091c2c6be: 6,729 passed, zero failed, 32 ignored across 32 parent harnesses; all three required layering guards PASS. Child subprocess summaries are excluded from totals.Earlier failed and cancelled results remain preserved. Five Rust cases failed with fixtures beneath real
.acancestry; the single authorized run using an isolated temp root passed those cases and the full suite. An invalid frontend preflight downloaded Node 26 into a shared cache and its suite was cancelled; the known process chain was settled before the single corrected Node 22 pass. Those earlier executions are not relabeled as successful, and no broader exclusive-cause claim is made.Evidence:
room-shared/i3068-validation/P03/integrated-mainf08/, with corrected frontend report/manifest hashes4b389eb885b9cd5fa276c81e524385bdfbbe27d0978e21ab6c3b790716b92905/77152be4cac944033f72217f4b51f687b22dc92ac4c3811ecd6a787e5cf88ffc. Full PR CI remains required for this exact published head via the existingci:fulllabel. No distribution build, release or version bump is requested.Closes #3073