Correct the v0.3 consumer API before stable release

[Aaronontheweb]

Summary

• replace the experimental sparse EffectiveArguments coordinate overlay with one parser-owned AnalyzedArgument per non-cwd Arg, including direct many-to-one inline option joins
• replace public value and redirect property bags with closed parser-owned record families, reference actual ancestry and host-argument objects, and remove public alpha-only syntax vocabulary that no stable parser emits
• preserve the stable v0.2 surface and its construction/list semantics; no compatibility shims are retained for disposable 0.3.0-alpha.* APIs
• synchronize the implementation, API snapshots, executable corpora, shared/PowerShell specs, OpenSpec checklist, README, consumer guide, release notes, and implementation plan
• pin the zero-iteration cwd path for zero-or-more Bash loops and normalize incomplete redirects to Unknown plus UnresolvedRedirectAnalysis

Validation

• dotnet build -c Release --no-restore — zero warnings/errors, both target frameworks and both samples
• dotnet test -c Release --no-build — 2,870 passed, 0 failed
• explicit PII audit — passed
• dotnet pack -c Release --no-build -o ./bin/nuget — package and symbols produced
• pwsh ./scripts/Add-FileHeaders.ps1 -Verify — passed
• openspec validate v0-3-structured-shell-analysis --strict — passed
• Slopwatch strict scan — 0 issues
• git diff --check — passed

Review

Required adversarial review passed after correcting two contract-wording issues: FileRedirectMode intentionally has no Unknown enum member, and defensive-list/parser-ownership promises apply only to the new v0.3 surface. The reviewer also verified no breaking assembly changes against stable 0.2.0 for netstandard2.0 or net8.0.

Follow-up

After this merges, publish the corrected prerelease, bump Netclaw from alpha.5, and run its existing Linux/native-Windows approval matrices before stable v0.3.