In `@docs/plans/2026-02-11-logs-page-plan.md`:
- Around line 11-13: Remove the machine-specific absolute worktree path after
the "Worktree:" label and replace it with a generic placeholder (e.g.,
"Worktree: /path/to/worktree" or "Worktree: ./worktree") so the plan is
portable; leave the "Test command:" line unchanged.

In `@includes/API/Logs.php`:
- Around line 197-218: get_db_entries currently loads the entire log table into
PHP; add optional $limit and $offset parameters to get_db_entries($level = null,
?int $limit = null, ?int $offset = null) and incorporate them into the SQL as
prepared LIMIT/OFFSET clauses (use $wpdb->prepare with %d placeholders) so the
query returns only the requested page; then change get_unread_counts to avoid
calling get_db_entries for counting and instead run a single prepared COUNT(*)
query on the same $wpdb->prefix . 'woocommerce_log' table with the same source =
'woocommerce-pos' and level severity condition to compute unread counts directly
in SQL.
- Around line 81-106: The pagination variables $per_page and $page must be
clamped to positive integers before computing $total_pages and $offset to
prevent negative/zero values; update the assignment logic in the same block
(where $per_page and $page are set and before $total_pages/$offset calculations)
to cast to int and enforce $per_page = max(1, (int)...) and $page = max(1,
(int)...), optionally also bounding $per_page to a sane maximum, so subsequent
math in array_slice, ceil and offset is always valid.
- Around line 351-377: get_unread_counts() is comparing $last_viewed (ISO 8601
stored via gmdate('c')) to $entry['timestamp'] (MySQL DATETIME from
get_db_entries()), which fails due to different formats; normalize both values
to Unix timestamps before the comparison. In the loop inside
get_unread_counts(), convert $last_viewed and $entry['timestamp'] to integers
using strtotime (or DateTime->getTimestamp) when they are non-numeric (e.g.
$last_viewed_ts = is_numeric($last_viewed) ? (int)$last_viewed :
strtotime($last_viewed); $entry_ts = is_numeric($entry['timestamp']) ?
(int)$entry['timestamp'] : strtotime($entry['timestamp'])), then use those
timestamps for the conditional that skips read entries and for any other
ordering/compare logic; reference get_unread_counts(), LAST_VIEWED_META_KEY,
get_db_entries()/get_file_entries(), $last_viewed, and $entry['timestamp'] when
making the change.

In `@packages/settings/src/screens/logs/use-unread-log-counts.ts`:
- Around line 44-51: markLogsRead currently zeroes the shared counts and calls
emitChange before the POST completes; capture the previous counts (the variable
referenced as counts) into a local variable, perform the optimistic update (set
counts = { error:0, warning:0 } and emitChange), then wrap the apiFetch call in
a try/catch; on failure restore counts = previousCounts, call emitChange to roll
back the UI, and rethrow or handle the error as appropriate. Ensure you
reference the markLogsRead function, the counts variable, emitChange, and
apiFetch so the rollback is applied only on request failure.

In `@packages/settings/src/screens/logs/index.tsx`:
- Around line 150-169: The expanded row index (expandedIndex) can persist across
pages and expand the wrong entry when the page changes; update the pagination
handlers or lifecycle to clear it whenever page changes—e.g., when calling
setPage (used in the Previous and Next button onClick handlers) also call the
setter for expandedIndex (setExpandedIndex) to reset to null/undefined/-1, or
add a useEffect that watches page and resets expandedIndex; ensure you reference
and update expandedIndex and setExpandedIndex in the component that renders the
pagination.
- Around line 121-138: The log entry container currently uses a non-focusable
div with an onClick to toggle expansion; replace it with a semantic interactive
element (preferably a <button>) so keyboard users can focus and activate it,
move the onClick handler (onClick={() => isLong && setExpandedIndex(isExpanded ?
null : index)}) to that button, add aria-expanded={isExpanded} and ensure the
disabled state or pointer-events are applied when isLong is false (so
non-expandable entries aren’t interactive), and preserve existing classes
(including LEVEL_STYLES, entry.timestamp, displayMessage) so visual styling
remains unchanged.

In `@packages/settings/src/screens/logs/index.tsx`:
- Around line 109-149: The expandedIndex state can point to the wrong row after
entries are refreshed and reordered; add logic to reset expandedIndex when the
entries array changes by using an effect that watches entries and calls
setExpandedIndex(null) (or appropriate default) to clear expansion; locate the
state and setter for expandedIndex and add a useEffect referencing entries to
clear it whenever entries updates to avoid stale expanded rows in the list
rendering code that maps entries.