[Branden Bonaby (bbonaby)]

📖 Description

Support one named project view containing all of a person's area work plus
anything assigned to them, including assignments outside their areas.
Area work remains visible when somebody else is assigned.

GitHub Projects cannot express this cross-field OR directly. Add a
deterministic synchronizer that maintains derived View-<login> issue labels
from area rules and assignments, with issue-event updates and hourly
reconciliation. It uses the repository token and needs no organization-project
secret. Pull request runs only execute read-only tests.

Keep the existing Type column and manual ordering, with Labels hidden.
The synchronizer does not change assignments, milestones, issue bodies, or
comments. Existing area/subarea rules are preserved in one configuration.
Include a deployment and rollback guide.

Activation is intentionally separate: merge the reviewed workflow, run a
successful full reconciliation, then switch the existing named view filters
to label:View-LOGIN. The live project filters have not been switched yet.
No new tabs are needed.

🔗 References

• processcontainer: intra-container loopback communication is blocked by default #1261 is a visibility example: it should appear under Branden because it is
  both networking work and assigned to him. This PR does not fix or close its
  underlying networking bug.
• docs/development/guides/project-view-membership.md

🔍 Validation

• node --test scripts\tests\project-view-membership.test.cjs — passed, 9 tests.
• node --check scripts\sync-project-view-membership.cjs — passed.
• node scripts\sync-project-view-membership.cjs --repo microsoft/mxc — passed,
  read-only preview of all 67 open issues; processcontainer: intra-container loopback communication is blocked by default #1261 includes View-bbonaby.
• git diff --cached --check — passed.
• Live label writes and project-filter activation were not run; they require
  the reviewed workflow to be deployed first.
• Product builds and SDK/backend suites were not run; no product code changed.

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue
• Updated documentation (if applicable)
• Updated Copilot instructions (if build, architecture, or conventions changed)
• If this PR changes Cargo.lock, the dependency-feed-check check passes (see pull request builds)

📋 Issue Type

• Bug fix
• Feature
• Task

---

GitHub Actions runs the PR validation build automatically. The ADO pipeline
(MXC-PR-Build) is the Azure version of the PR pipeline, kept in parity with the GitHub
Actions build; it runs on merge to main, and Microsoft reviewers with write access can trigger it
on a PR with /azp run. See pull request builds.

If the dependency-feed-check check fails on a new dependency, the crate must be added to
the feed before the PR can pass. See pull request builds
for the steps.

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟡 Changes recommended

Overlapping reconciliation and issue-event runs can delete required membership labels and temporarily hide assigned work.

1 open issue

• Prevent concurrent reconciliations from overwriting issue-event updates · New

What changed in this PR

Adds repository automation to combine area responsibility and assignments in existing named project views using derived View-<login> labels. Project-filter activation remains a separate deployment step; no SDK or backend behavior changes.

Changes:

• Centralizes ownership rules and adds label synchronization with read-only previews.
• Adds issue-event and hourly reconciliation, with read-only tests on pull requests.
• Documents activation and rollback while preserving existing view layout and ordering.

File	Description
scripts/​tests/​project-view-membership.test.cjs	Tests membership rules, label updates, and failure handling.
scripts/​sync-project-view-membership.cjs	Calculates membership and synchronizes derived labels.
scripts/​project-view-owners.json	Defines area ownership and subarea exclusions.
docs/​development/​guides/​project-view-membership.md	Explains ownership rules, activation, rollback, and local checks.
.github/​workflows/​Project.View.Membership.yml	Runs validation and event-driven or scheduled synchronization.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The automation is narrowly scoped to derived labels, separates PR validation from writes, and leaves live filter activation for a successful deployment.

No open issues 🎉

1 resolved since last review

• Prevent concurrent reconciliations from overwriting issue-event updates

_{Review effort: Balanced}