fix(cli): accept --props comma batch form on mutating verbs

[ylz92871-dotcom]

What

--props "k=v,k2=v2" is now a registered option on set / add / remove / move / mark, parsed with the same key=value semantics as repeating --prop. A value that itself contains a comma is protected by single quotes (--props "text='a,b',bold=true" → text=a,b, bold=true). --prop values are never split, so comma-bearing values (--prop data="S1:1,2,3") behave exactly as before. Malformed input (a segment without =, a stray comma, an unterminated quote) is rejected up front with code=invalid_argument and a --prop suggestion — never partially applied.

Why

Agents habitually guess the plural form. Because --props was not a registered option, System.CommandLine shunted the entire value into unmatched tokens, where it was dropped — at best with a warning, at worst via a misleading downstream error. Real-world repro against 1.0.148: a chart add lost dataRange/categories entirely and reported "Chart requires a 'data' property", which misleads the caller into "fixing" the wrong thing. The existing BUG-BT-R6 typo-catch only turned the silent drop into a warning; the properties still never reached the handler. The warning's suggestion also doubled the flag (Use: --prop --prop value=...) because the claimed token was pre-prefixed; the prefix is now added exactly once by consumers.

Implementation

• CommandBuilder.CreatePropsBatchOption() — shared --props option factory; MergePropFlags() merges --prop entries with quote-aware comma-split --props entries; SplitPropsBatch() does the splitting + up-front validation. All in CommandBuilder.cs next to the existing DetectUnmatchedKeyValues machinery.
• Wired at the five existing --prop registrations (set/add/remove/move/mark). The merge happens at the single point where each verb reads its props, so resident and standalone routes share it with no behavior difference.
• BUG-BT-R6's Pattern 3 stays (for -props / --prop= spellings and verbs without the option) but no longer injects a --prop prefix into claimed tokens.

How to verify

officecli add data.xlsx /Sheet1 --type chart --props "type=line,anchor=H20,dataRange=Sheet1!B2:B3,categories=Sheet1!A2:A3" --json
  → "Added chart at /Sheet1/chart[1]"   (before: Chart requires a 'data' property)

officecli set data.xlsx /Sheet1/F1 --props "value='a,b',bold=true" --json
  → text "a,b" (comma preserved, quotes stripped), font.bold=true

officecli set data.xlsx /Sheet1/A1 --props "bold" --json
  → invalid_argument + "Use --props \"k=v,k2=v2\" … or pass repeated --prop k=v"

officecli set data.xlsx /Sheet1/A1 --prop value=x,y --json
  → text "x,y" (--prop values untouched)

Local regression harness (shells the built exe; resident + OFFICECLI_NO_AUTO_RESIDENT=1 standalone): 9/9 green — comma-form chart add, quote protection, --prop passthrough, three rejection paths with code+suggestion, mixed --prop --props merge, both execution modes.
dotnet build -c Release: 0 errors (1 pre-existing CS8602 warning, untouched by this change). dotnet publish single-file smoke-verified end-to-end on the published exe (atomic batch rollback, formula evaluation readback, chart adds, validate 0 errors).