P2: Evaluate upstream manual teammate management

[100yenadmin]

Parent release train: #623
Deferred/upstream tracker: #585
Upstream: iOfficeAI#3532, commit 826eba76cf945ab7687a38d858bc5bb2e009796b, tagged in upstream v2.1.32 with a WIP subject.

Decision

defer. This is a large team/runtime change spanning adapter types, team membership, warmup, queue behavior, agent/model selection, workspace UI, i18n, and E2E coverage. It is not eligible for a direct or mixed reliability port.

Scope

• Audit the upstream runtime/API assumptions against current evaOS team and broker contracts.
• Define one atomic first slice, if any, with explicit customer/account permissions.
• Preserve current team run ownership, scheduled-task behavior, and agent capability propagation.

Guardrails

• No broad patch import, AionCore/runtime bump, broker/auth policy expansion, customer data exposure, Mac-control weakening, or mixed UI/runtime PR.
• Do not claim the upstream WIP commit is production-ready precedent.

Acceptance / validation

• Contract/file-map decision before code.
• Focused team membership, permissions, queue, warmup, and scheduled-task tests for an accepted slice.
• Current-head adversarial review and GitHub Actions before merge; release gates remain separate.

Proof boundary: evaluation and bounded manual-port planning only; no team-runtime or release-readiness claim.

[coderabbitai]

🔗 Related PRs

#403 - fix: recover Mac control installed app states [merged]
#416 - Fix Mac control connector-service ready reconciliation [merged]
#417 - Fix Mac pairing reconnect session gate [merged]
#449 - Fix legacy app stale owner proof path [merged]
#465 - Fix Mac connector readiness probe [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #628 - P2: Evaluate upstream manual teammate management
State: open; milestone: v2.1.34 Deferred Upstream Backlog

Related issues/PRs: #623, #585.
Existing labels: evaos, public-beta, ready-for-agent, area:shell, area:broker, risk:upstream-conflict, kind:spike, kind:integration, deferred-upstream, release-train:runtime-reliability.
Suggested labels: security, tests, support.
Suggested owners: none.

Related context

• Roadmap: Workbench runtime reliability release train #623 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Backlog: v2.1.34 deferred upstream ports #585 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: P2: Evaluate upstream manual teammate management - Parent release train: #623 Deferred/upstream tracker: #585 Upstream: iOfficeAI#3532, commit 826eba76cf945ab7687a38d858bc5bb2e009796b, tagged in upstream v2.1.32 with a WIP subject. ## Decision defer. This
Product fit: Product/UX-sensitive issue; review against repo vision and user flow quality, not only technical P0/P1 risk.
Implementation wedge: Ship the smallest user-visible path or prototype that can be smoke-tested against the intended experience.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• UX/product smoke or screenshot proof when implementation changes user flow.
• Contract or degraded-mode proof before runtime promotion.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• Owner or reviewer signal not detected in issue body.

No labels, owners, reviewers, or roadmap fields were changed by this bot.