You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish MP Catalog and API Documentation Wave A #16
Publish the documentation-first contract for MP Catalog Wave A: disposition every retained command in the included top-level SA groups, populate their grouped catalog pages, and define the gRPC, .NET, Python, and JavaScript/TypeScript APIs for every command selected for Briosa support.
This issue owns one substantial Docusaurus PR. Proposed APIs remain marked Next until the coordinated server and client implementations are released.
Included top-level SA groups
Accumulator Math Operations
Analysis Operations
Dimension Operations
Event Operations
Excel Direct Connect
File Operations
Google Sheets Operations
MP Subroutines
MP Task Overview
MS Office Reporting Operations
Process Flow Operations
Reporting Operations
Scalar Math Operations
Scale Bar Operations
Utility Operations
Variables
Vector Operations
View Control
Scope
Publish a catalog entry for every retained command identity in the 18 included groups.
Record Current, Next, Undecided, Uncommitted, Excluded, or SDK Unavailable disposition; rationale; validation qualifier; and alternative/workaround where applicable.
Define gRPC and all three idiomatic client APIs only for commands selected for implementation.
Preserve the exact-target SA group hierarchy for navigation without turning group names into public API namespaces.
Implement catalog search and filtering by command, group, status, and validation qualifier as part of this PR.
Link current supported operations to their authoritative implementation and represent planned Wave A operations as Next.
Keep documentation data isolated from server, protocol, client, runtime-policy, and package builds.
Acceptance criteria
Every retained Wave A command has a complete public disposition and grouped-page entry.
Unsupported commands explain why and provide a workaround, alternative, or none-known statement.
Every selected command has mechanically traceable gRPC, .NET, Python, and JavaScript/TypeScript API documentation.
Search and filters are keyboard-accessible, URL-addressable, and work with static-site generation.
No API page is created for an Uncommitted, Excluded, or SDK Unavailable command.
Proposed APIs are visibly Next and cannot be mistaken for released support.
Outcome
Publish the documentation-first contract for MP Catalog Wave A: disposition every retained command in the included top-level SA groups, populate their grouped catalog pages, and define the gRPC, .NET, Python, and JavaScript/TypeScript APIs for every command selected for Briosa support.
This issue owns one substantial Docusaurus PR. Proposed APIs remain marked
Nextuntil the coordinated server and client implementations are released.Included top-level SA groups
Scope
Current,Next,Undecided,Uncommitted,Excluded, orSDK Unavailabledisposition; rationale; validation qualifier; and alternative/workaround where applicable.Next.Acceptance criteria
Uncommitted,Excluded, orSDK Unavailablecommand.Nextand cannot be mistaken for released support.Coordinated implementation
Parent: #13