fix(client): settle table paging cancellation and errors

[HandSonic]

Related issue

N/A - no matching issue was found.

Summary

Table-browser paging treated a success=false result as completed data and replaced the last confirmed page. Desktop cancellation resolved as success without republishing that confirmed page, leaving an optimistic page number beside old rows. This change keeps a confirmed result in the paging state, rejects failed Web/Desktop results through the existing error path, and republishes a clean confirmed clone on cancellation.

Affected surfaces

• Frontend / Web
• Backend / API / Storage
• Database plugin / Driver
• JCEF / Desktop packaging
• CI / Build / Release
• Documentation only

Verification

• Commands and results:
  • Red result-pagination suite: 10 passed / 2 failed on current main.
  • Fixed result-pagination suite: 12 passed.
  • Related result-set, status, SQL request-tracker, stream, and execution-log contracts: passed.
  • Targeted ESLint: passed.
  • Full Community prebuild, Umi/Webpack build, and production bundle verifier: passed.
  • Fork code and CodeQL checks: passed.
• Manual verification: N/A - pure reducer and deferred stream tests cover failure and cancellation settlement.
• UI evidence: N/A

Risk and compatibility

• Public API or stored data: No API or persisted-state changes.
• Database or driver compatibility: N/A.
• Network, privacy, or security: N/A.
• Community / Local / Pro boundary: Shared Community table-browser paging.
• Backward compatibility: Successful page responses preserve current normalization and result identity behavior.

Reviewer map

• Start here: viewTablePagingModel.reduceViewTablePagingEvent, then useViewTablePaging.executePage.
• Failure condition: a failed result replaces confirmed rows, or cancellation leaves page controls ahead of visible data.
• Rollback or disable path: Revert commit d5aac0924f22cc422e25272dc2530ac97b05ea36; no migration is required.

Contributor declaration

• I linked the Issue that defines this change.
• I tested the affected behavior and reported the actual results above.
• I did not include credentials, private data, or generated build output.
• I disclosed substantial AI assistance below, or this PR contains no substantial AI-generated code.

AI assistance: OpenAI Codex assisted with diagnosis, implementation, automated tests, verification, and adversarial review.

Latest-main revalidation (2026-09-04)

• Rebased onto upstream 144a04e; current head d5aac09.
• Table paging flow and related pagination suite: 12/12 passed; targeted ESLint passed.
• Included in the green combined Community production build and bundle verification.