Add independent alignment plus native Apple and Windows support

[CodeinScrubs]

What changed

• separates paragraph direction from physical alignment across DOM, React, Vue, Web Component, Android Views, and Compose integrations;
• preserves authored physical-left alignment for RTL Persian/Arabic/Hebrew content while retaining RTL paragraph direction and inline isolation;
• adds a root Swift Package with Unicode 17 analysis, UIKit adapters, state restoration, a runnable example, and shared-corpus tests;
• adds .NET 8 analysis plus WPF adapters, state restoration, a runnable sample, exact corpus/isolation verification, and NuGet pack gates;
• adds macOS/iOS and Windows native CI jobs and documents explicit platform and security boundaries.

The root cause of the alignment regression was coupling content direction to content-edge alignment. The new contract treats those as independent properties and keeps pure LTR content on the existing strict no-op path.

Evidence

• Added or updated a focused regression test.
• Added or updated a corpus fixture when direction policy changed. (Direction policy did not change; generated Apple corpus parity was added.)
• Confirmed source text, selection, and copy order remain logical.
• Ran pnpm run check.
• Ran pnpm run test:visual for rendering or adapter changes.
• Ran package/release gates for manifest, dependency, or public API changes.
• Added a Changesets entry for a published-package API or behavior change.

Additional local evidence:

• Android full gate: 269 Gradle tasks plus isolated Maven consumer build.
• Windows: zero warnings/errors, 1,130 assertions, 918 direction fixtures, all 197 exact isolation plans, WPF sample build, and two NuGet package builds.
• Web: 396 tests with coverage; 76 focused adapter tests; type, lint, docs, audit, SBOM, three-browser visual, packed types, and all packed examples passed.
• Apple compilation and tests are intentionally delegated to the new macOS/iOS hosted CI job because Swift/Xcode are unavailable on the Windows development host.

Security and language review

The runtime remains offline and source-preserving. No source reversal or persisted bidi controls were added. Native Swift/.NET control auditing is explicitly documented as narrower than the richer JavaScript/Android balance-and-context scanner. The 918-case corpus is technically reviewed but has zero native-speaker-certified templates; this PR does not claim native-language certification, physical-device accessibility validation, registry publication, or downstream adoption.