chore(branding): remove PPDS.Tools / PPDS ALM, rename SDK to libraries

[joshsmithxrm]

Summary

Brings .claude/rules/branding.md in sync with what actually ships at v1. CLAUDE.md #18 recently pruned to point at this file as the canonical name list, so staleness here now actively misleads any AI session authoring docs.

Changes

• Components table — remove PowerShell | PPDS.Tools and ALM | PPDS ALM rows (not shipping at v1; add back when they do)
• Repositories table — remove ppds-tools and ppds-alm rows; update Main repo description from PPDS (SDK + CLI + TUI + Extension + MCP) to PPDS (Libraries + CLI + TUI + Extension + MCP)
• Links — remove PSGallery link (no PPDS.Tools package to point at)
• New Terminology section — explicit rule on libraries vs SDK, noting the NoSdkInPresentationAnalyzer rule in the ppds monorepo that enforces the same convention in code
• Value props — standard SDK patterns → standard Dataverse SDK patterns (disambiguates Microsoft's SDK from PPDS libraries)

Test plan

• File is not rendered by Docusaurus (.claude/rules/ is ignored), so no build check required
• Verify CLAUDE.md link target still resolves

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the branding and terminology guidelines in .claude/rules/branding.md. Key changes include removing references to PowerShell and ALM components, updating repository tables, and introducing a 'Terminology' section to distinguish between PPDS 'libraries' and the Microsoft Dataverse 'SDK'. Review feedback suggests reordering the component list in the repository table for consistency and ensuring the 'PPDS' abbreviation is consistently capitalized in the documentation.

[gemini-code-assist]

The list of components in the repository description should follow the order established in the 'Components' table (lines 19-22) for better consistency. Additionally, 'TUI' should be grouped as a feature of the 'CLI' component. Please ensure these rules are centralized in the primary AI instructions file to avoid duplication and maintain a single source of truth.

Suggested change

	| Main | power-platform-developer-suite | PPDS (Libraries + CLI + TUI + Extension + MCP) |
	| Main | power-platform-developer-suite | PPDS (CLI + TUI + Extension + Libraries + MCP) |

References

1. Centralize global rules in a primary file to maintain a single source of truth and conserve context.

[gemini-code-assist]

Capitalize the product abbreviation as 'PPDS' for consistency with branding guidelines. Additionally, use 'libraries' for PPDS packages and 'SDK' for the underlying Microsoft Dataverse SDK to avoid ambiguity. These rules should be centralized in the primary AI instructions file to avoid duplication.

Suggested change

- Use **"libraries"** (not "SDK") to refer to PPDS NuGet packages (`PPDS.Auth`, `PPDS.Dataverse`, `PPDS.Migration`, `PPDS.Plugins`). "SDK" is reserved for Microsoft's Dataverse SDK (`ServiceClient`, `IOrganizationService`) that the PPDS libraries sit on top of. Disambiguation matters — sentences like "the SDK handles throttling" are ambiguous in this codebase. The `NoSdkInPresentationAnalyzer` rule in the ppds monorepo enforces the same convention in code.

- Use "libraries" (not "SDK") to refer to PPDS NuGet packages (PPDS.Auth, PPDS.Dataverse, PPDS.Migration, PPDS.Plugins). "SDK" is reserved for Microsoft's Dataverse SDK (ServiceClient, IOrganizationService) that the PPDS libraries sit on top of. Disambiguation matters — sentences like "the SDK handles throttling" are ambiguous in this codebase. The NoSdkInPresentationAnalyzer rule in the PPDS monorepo enforces the same convention in code.

References

1. Centralize global rules in a primary file to maintain a single source of truth and conserve context.