Decide: consolidate Visio-PIAs source into main VisioAutomation repo

[saveenr]

Decide whether to consolidate the source of the Visio-PIAs sibling repo into the main VisioAutomation repo, reducing the number of repos to manage.

Background

Visio-PIAs ships the Visio2010.PrimaryInteropAssembly NuGet package, consumed by VisioAutomation's build via Directory.Packages.props. The repo is active reference in the Phase H1 portfolio audit (last push 2017-02-03), load-bearing but not feature-active.

Surfaced from the Phase H1 status calls on #152.

Question

Should the source of Visio-PIAs be folded into a subdirectory of VisioAutomation (e.g. Visio-PIAs/), with the NuGet package built from that subdirectory? Trade-offs:

Pro:

• One less repo to maintain or track.
• Atomic commits when both pieces need to change together.
• Reduces "is this still active?" friction (the source visibly tracks main-repo activity).

Con:

• Mixes a different-license artifact (PIA repackaging) into the main repo. Need to confirm the licensing model still works.
• Couples NuGet release cadence: today the PIA package is independently versioned; folding the source in tempts coupled releases.
• The PIA package has separate consumers from VisioAutomation; making them visibly coupled may confuse those consumers.

Decision needed

• (a) Consolidate.
• (b) Leave separate; add a clearer pointer from main repo's docs.
• (c) Archive Visio-PIAs (the PIA package is on NuGet; source becomes read-only history).

Cross-refs

• docs/RELATED-REPOS.md.
• Visio repo portfolio audit Phase H1: centralized index + per-repo README status #152 Phase H1.
• Phase H2 work (per-repo retire / merge / maintain decisions), which this overlaps with.

Effort

S to decide. M to consolidate if (a). S if (c).