docs: VisioScripting.Client is undocumented in the gitbook

[saveenr]

Background

The .NET-side gitbook (https://saveenr.gitbook.io/visioautomation/) has zero coverage of VisioScripting.Client, even though the source readme.md leads with a VisioScripting.Client snippet as its quick-start. A new C# reader's first impression is therefore an undocumented type.

VisioScripting/Client.cs exposes ~25 command groups (Application, Arrange, Connection, ConnectionPoint, Container, Control, CustomProperty, Developer, Document, Draw, Export, Grouping, Hyperlink, Layer, Lock, Master, Model, Output, Page, Selection, ShapeSheet, Text, Undo, UserDefinedCell, View). The source has a VisioScripting/README.md that's a solid starter, but it's not surfaced on the gitbook.

Public-API status (resolved)

Resolved per #156: hybrid public. VisioScripting.Client, the 25 group properties, and the public method signatures on each *Commands class are the documented public-stable contract. Helpers/, Loaders/, CommandTarget, and other plumbing stay internal-mutable. The pre-lock cleanup (#182) has landed: facade methods added for the two boundary leaks, and the enforcement layer is in place. Authoritative table: docs/decisions/visioscripting-public-api.md. Documented surface is ~156 method signatures across the 25 *Commands classes plus Client itself, the Target* types, ClientContext / DefaultClientContext, and the Models.* types referenced from public signatures.

Dead-method stance (resolved)

Resolved per #184: Option A ("public, candidate for CY27 removal"). Each dead method's gitbook page carries a "Remarks: candidate for CY27 removal (see #183)" note. The list of methods that get the flag is the ~36 identified in the #156 audit (filed under "Dead methods" in #183's body).

Status

• Overview page landed. visio-scripting.md on the gitbook (commit 79474d1) covers the facade introduction, instantiation, the Target* convention, the 25-group index, and ClientContext / DefaultClientContext. SUMMARY now has a ## VisioScripting section between ## Core APIs and ## Shape data.
• Per-group sub-pages: pending. 25 pages, one per *Commands class. Each follows the standard ## Syntax / ## Parameters / ## Examples / ## See also template, with a "Remarks: candidate for CY27 removal" block on dead methods per #184.
• getting-started.md preamble polish: pending. Existing API selection table is the foundation; the VisioScripting.Client row should now link to visio-scripting.md.
• PowerShell-side cross-links: pending. Each cmdlet that wraps a Client.<Group> call gets a cross-link to the corresponding new .NET-side page on the PSGallery gitbook.

Proposed work (remaining)

• Write 25 per-group sub-pages under visio-scripting/ on the gitbook. Standard layout per existing per-namespace pages on the gitbook, with the "Remarks: candidate for CY27 removal" block where applicable.
• Update getting-started.md to link the VisioScripting.Client table entry at the new overview page.
• Cross-link from PowerShell-side cmdlet docs to the corresponding new .NET-side group page.

Effort

M-L. Per-group pages are the bulk; ~25 pages with similar structure should batch reasonably. Comparable in scope to the Tier 1+2+4 .NET-side coverage that landed in 2026-05.

See also

• #156 — hybrid public-API decision (closed).
• #182 — pre-lock cleanup (closed). Phase B added 4 facade methods; Phase C internalized the plumbing.
• #184 — dead-method stance decision (closed; Option A).
• docs/decisions/visioscripting-public-api.md — authoritative public/internal contract table.
• Tracked in docs/FUTURES.md under "Decide whether to document VisioScripting as a public API".
• Surfaced by the 2026-05-05 doc-review pass (proposed-issues.md issue Visio 2013 Support with Powershell Modules #1).

[saveenr]

All three proposed-work items landed. Closing.

What shipped

.NET gitbook (VisioAutomation_GitBook_Docs), 4 commits on `main`:

• `79474d1` - new top-level visio-scripting.md overview page; `SUMMARY.md` adds a `## VisioScripting` section between Core APIs and Shape data.
• `d4c0306` - first 2 per-group pages (client.Hyperlink, client.Page) as template-validation pair.
• `d3e8710` - remaining 23 per-group pages. All 25 `*Commands` classes now have dedicated coverage. Pages with dead methods carry a `## Removal candidates (CY27)` section per #184's stance.
• `c5144e6` - getting-started.md's entry-point table now links the `VisioScripting.Client` row at the new overview.

PowerShell gitbook (VisioPowerShellDocs), 1 commit on `visiops_v4_docs`:

• `8d15141` - 15 cmdlet topic READMEs (`cmdlets/control/`, `cmdlets/pages/`, `cmdlets/visioapplication/`, etc.) gain a `## On the C# side` section pointing at the corresponding client.<Group> page on the VisioAutomation gitbook.

Coverage of the proposed work

• Top-level `visio-scripting/` section on the gitbook (overview + 25 per-command-group sub-pages).
• `getting-started.md` API-tiers preamble polish (entry-point table now links the VisioScripting.Client row).
• PowerShell-side cross-links from cmdlet topic READMEs to the corresponding .NET-side group page (Scope A in our discussion: per-topic READMEs only; per-cmdlet See-also additions deferred as polish if useful later).

Surface size

The locked public-stable surface documented across these pages is ~156 method signatures across the 25 `Commands` classes (~120 active + ~36 candidates for CY27 removal under #183), plus `Client`, the `Target` types, `ClientContext` / `DefaultClientContext`, and the `Models.*` types referenced from public signatures.