issue 4531 slice 96: PublishingShell change one location scheme parameter sequence

[natechadwick-intsof]

Parent: #4531

Slice goal

In Publishing design, an admin changes the sequence of one location-scheme parameter. The parameter name, type, and value stay. The other parameters stay on the scheme. The new sequence shows only after a successful save.

Out of scope

Parameter value (slice 94) and type (slice 95). Add and remove. Reordering by dragging the whole list.

Acceptance criteria

• Sequence-only update of one stored parameter on the existing scheme PUT. Do not combine it with add, remove, value-only, or type-only. Name, type, and value stay. Other parameters stay, including their sequences. WebUI Publishing design + Vitest + sitemanage test + H2 surface Playwright + product-docs/8.2/admin/publishing.md.
• A blank or non-integer sequence does not write. Cancel does not write. A name that is not on the scheme is HTTP 409. HTTP 400, 403, and 409 leave the previous sequence in place.
• Do not replace the stored parameter set. Do not edit api/paths.ts, DeveloperShell.tsx, sitemanage-beans.xml, or WebUI / perc-qa-automation package.json.
• Update parent [8.2] Unified publishing — next React increments #4531 Agent progress section.

Leave unassigned. Do not add In Progress.

Co-Authored by Grok Build 1.0.46 using grok-4.7 with agent night-issue-prs-triage.

[natechadwick-intsof]

night-issue-prs: sequence-one location scheme parameter update is in #5377. Closing this slice. Parent #4531 stays open.

Co-Authored by Grok Build 1.0.46 using grok-4.6 with agent night-issue-prs.

[natechadwick-intsof]

Work complete. See PR #5377.