feat(remix): add optional indicator semantics - #93
Conversation
Related to #90.
Coordination: replay this feature onto canonical #80PR #84 has been closed as superseded. PR #80 now targets Synchronize the local workspace firstThe latest observed #80 head is git status --short
git fetch origin
git rev-list --left-right --count \
HEAD...origin/feat/remix-progress-semanticsThe current PR head is expected to be Create a local safety branch, then replay the one feature commit after the old git branch backup/pr-93-before-final-fortal-contract
git rebase --onto origin/feat/fortal-polish \
ebe9ee1decf0a194c1d2b63c7b0fc18a6e7731d4Required integration
For the accessibility contract:
Verification and publicationRun clean generation and: fvm dart run melos run ci
fvm flutter analyze
git diff --checkAlso format every changed Dart file, run the headless semantics tests, and After verification: git push --force-with-lease origin feat/remix-progress-semantics
gh pr edit 93 --repo conceptadev/remix --base feat/fortal-polishUpdate this PR body with the new test count and final #80 head used. Do not |
Coordination update: absorbed into canonical #80The earlier replay handoff on this PR is superseded. I replayed the handwritten The result is in #80 as No agent should rebase or force-push this branch now. Closing this draft without |
Description
Adds optional semantics to Spinner and determinate Progress, including generated
Fortal forwarding. Null inputs remain decorative; labelled indicators expose
one noninteractive role node, and Progress reports a 0–100 value.
Validation:
fvm dart run melos ci(1,895 tests) andfvm flutter analyze packages/remix.Related Issues
Related to #90. Stacked on #84.
Checklist
///).Breaking Change