Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.cursor/commands/pull_request.md:
- Line 23: Remove the accidental personal reminder line "Do not push pr until i
read the comment and reviewed it!" from the .cursor/commands/pull_request.md
content; edit the file to delete that sentence so the document contains only
repository-relevant instructions and commit the change with a clear message like
"remove personal reminder from pull_request.md".

In `@docs/ADMIN_DISPUTES.md`:
- Around line 829-831: The documentation references the old field name
`currencies`; update the "Clear Currency Filters" section (the bullet that
currently reads "Clears the `currencies` array in `settings.toml`") to use the
new field name `currencies_filters` instead, keeping the explanatory sub-bullets
(e.g., that an empty list means “no filter”) unchanged so the text now reads
that it clears the `currencies_filters` array in `settings.toml`.

In `@README.md`:
- Around line 103-106: The README explanation refers to the old field name
`currencies`; update the text to reference the actual setting
`currencies_filters` everywhere in that paragraph (including examples), so the
description and examples match the real configuration key `currencies_filters`.
- Around line 67-68: The README example uses the old key name `currencies`;
update the example to the new settings field `currencies_filters` to match
src/settings.rs and the PR summary—replace the line `currencies = ["VES", "ARS",
"USD"]` with `currencies_filters = ["VES", "ARS", "USD"]` so docs match the
actual config key.

In `@src/settings.rs`:
- Line 15: The field rename to currencies_filters breaks deserialization for
existing settings.toml; update the struct definition for the currencies_filters
field in src/settings.rs to accept the old name by adding a serde alias (e.g.,
apply #[serde(alias = "currencies")] to the currencies_filters field) so serde
will accept either key, or alternatively document the required manual migration
in the release notes if you intentionally want to force users to change their
files.

In `@src/util/mostro_info.rs`:
- Around line 146-152: Docstring for the function that fetches the latest Mostro
instance info (the comment above the filter block in src/util/mostro_info.rs)
claims the filter includes tags `y=mostro` and `z=info` but the actual filter
used by the function (the query built for author/kind/identifier/limit) does not
include these tags; either add the `y` and `z` tag constraints to the
query/filter logic in the function that constructs the event filter (so the
query enforces `y=mostro` and `z=info`), or simplify the docstring to remove
mention of `y=mostro` and `z=info` so it matches the current behavior (adjust
the docstring above the filter construction in mostro_info.rs to reflect
whichever option you choose).

---

Outside diff comments:
In `@docs/ADMIN_DISPUTES.md`:
- Around line 839-863: Update the documentation examples so the field name
matches the implementation: replace references to s.currencies in the functions
save_currency_to_settings and clear_currency_filters with the actual struct
field s.currencies_filters (or the exact field name used in
src/ui/key_handler/settings.rs), ensuring the logic still pushes, checks, and
clears that field and the log messages remain unchanged.

---

Nitpick comments:
In `@src/main.rs`:
- Around line 191-202: The startup fetch of mostro_info (via
fetch_mostro_instance_info) only runs once and on Err leaves app.mostro_info
unset; add a background retry to populate mostro_info when the initial fetch
fails by extending start_fetch_scheduler to periodically call
fetch_mostro_instance_info and set app.mostro_info on success (and log
failures), or spawn a dedicated async task that loops with a delay and retries
until app.mostro_info is Some. Locate usages of fetch_mostro_instance_info, the
app.mostro_info field, and the start_fetch_scheduler function to implement the
loop, ensuring you avoid spawning duplicate retry tasks and respect shutdown
signals already used by start_fetch_scheduler.
- Around line 465-476: The fallback string for mostro_instance_currencies
conflates app.mostro_info == None (fetch failed) with an empty
fiat_currencies_accepted (instance accepts all); update the match on
app.mostro_info so you return a distinct message for the None case (e.g.,
"Unknown (failed to fetch Mostro info)") and keep "All (Mostro instance accepts
all)" for Some(info) with empty fiat_currencies_accepted, referencing the
mostro_instance_currencies variable, app.mostro_info and
fiat_currencies_accepted to locate and change the logic.

In `@src/ui/tabs/mostro_info_tab.rs`:
- Around line 36-46: The user-facing message in the None branch of the Mostro
info tab currently exposes an implementation TODO via the styled span; update
the Paragraph/Spans created in the None branch (the variable message built with
Paragraph::new, Line::from, Span::raw/Span::styled) to remove the "or implement
a manual refresh key later" text and replace the styled span with a concise
state-only message (e.g., indicate that no info is loaded and the tab will
refresh after startup) so only the user-visible state is shown; keep the UI
structure (Paragraph::new, f.render_widget(chunks[1])) unchanged.

In `@src/util/mostro_info.rs`:
- Around line 66-144: The function mostro_info_from_tags returns
Result<MostroInstanceInfo> but never produces Err; change its signature to
return MostroInstanceInfo directly, remove the Ok(...) wrapper at the end
(return info), and update any callers (e.g., fetch_mostro_instance_info) to
accept the direct MostroInstanceInfo return instead of handling a Result; also
remove any ? propagation or Result-related imports tied to
mostro_info_from_tags.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/ui/tabs/mostro_info_tab.rs`:
- Around line 55-61: The paragraph rendering currently can cut off long fields
in narrow terminals; update the widget configuration used around
Paragraph::new(lines) so long text is wrapped (use Paragraph's wrap setting,
e.g., Wrap { trim: true }) and, if needed for vertical overflow, convert to a
scrollable view using a scroll state and render via f.render_widget with that
state instead of a plain Paragraph; adjust usage of Paragraph, f.render_widget,
area, and lines accordingly to ensure node pubkey, URIs and joined currency
lists are readable on narrow terminals.
- Around line 41-42: The empty-state guidance string in the view (the literal
"Switch to this tab after startup to refresh automatically, or implement a
manual refresh key later.") is misleading because the tab does not auto-refresh
on switch; update the message in the MostroInfoTab render code (where that
literal is defined) to accurately describe current behavior—e.g. say it displays
the current state and requires a manual refresh or explain how to refresh—or
alternatively implement the actual auto-refresh-on-tab-switch behavior in the
MostroInfoTab render/update handler if you prefer keeping the original copy.
- Around line 79-90: The expiration policy rendering is missing three fields
from MostroInstanceInfo; update the UI code in mostro_info_tab.rs where lines
are built (the block calling
push_opt_i64/push_opt_u64/push_opt_u32/push_opt_f64) to also push
hold_invoice_expiration_window, hold_invoice_cltv_delta, and
invoice_expiration_window using the appropriate push_opt_* helpers (e.g.,
push_opt_u64 for expiration-window fields and push_opt_u32 for cltv if that is
the type on MostroInstanceInfo), keeping the same label style like "Hold invoice
expiration window", "Hold invoice CLTV delta", and "Invoice expiration window"
so the full expiration policy is displayed.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/ADMIN_DISPUTES.md`:
- Around line 157-165: Update the documentation text to reflect that legacy
currency filters are actually active: state that the scheduler reloads the
currencies_filters on each tick and uses the `currencies` array from
`settings.toml` to filter visible orders (so these filters are not ignored), and
clarify interaction with the Mostro instance `fiat_currencies_accepted` tag and
behavior in Admin/User modes (replace claims that filters are ignored/deprecated
with accurate behavior and note legacy status only if still relevant); reference
the `currencies`, `currencies_filters`, `settings.toml`,
`fiat_currencies_accepted`, scheduler, Mostro and Mostrix symbols when updating
the two "Add Currency Filter" and "Clear Currency Filters" bullets.

In `@src/ui/key_handler/enter_handlers.rs`:
- Around line 411-440: The refresh handler currently reloads the Mostro pubkey
from disk (crate::settings::load_settings_from_disk) which can diverge from the
runtime pubkey; instead use the runtime's pubkey in ctx to keep behavior
consistent. Replace the load/parse block with using ctx.mostro_pubkey (or parse
ctx.mostro_pubkey if it is a String) and pass that parsed PublicKey into
fetch_mostro_instance_info along with ctx.client; remove the disk-read path and
error branch so the handler uses ctx.mostro_pubkey (or update ctx first when
settings change) before calling fetch_mostro_instance_info.
- Around line 442-458: The refresh_result match leaves app.mostro_info unchanged
on Ok(None) and Err(e), causing stale Mostro data to remain; update the Ok(None)
and Err(_) arms of the match that handles refresh_result to clear the cached
data by setting app.mostro_info = None before updating app.mode (i.e., in the
Ok(None) arm that currently sets
UiMode::OperationResult(OperationResult::Info(...)) and in the Err(e) arm that
sets OperationResult::Error(...)), so the Mostro Info tab and status bar no
longer show stale currencies/details for the current pubkey.
- Around line 434-440: The Enter handler currently blocks the UI by calling
tokio::task::block_in_place and awaiting fetch_mostro_instance_info directly;
instead, spawn the network fetch as a background task (use tokio::spawn or
ctx.runtime.spawn) that calls fetch_mostro_instance_info(&client,
parsed_pubkey).await and then sends the result back over the existing
order_result_tx channel (similar to the Observer flow around the Observer
handler). Remove the block_in_place usage and ensure the Enter handler only
enqueues the background task and returns immediately; handle updating AppState
when the receiver for order_result_tx processes the outcome.

---

Duplicate comments:
In `@docs/ADMIN_DISPUTES.md`:
- Around line 822-864: The docs and example code refer to the old settings field
`currencies`; update them to consistently use `currencies_filters` instead: in
the snippet for save_currency_to_settings and clear_currency_filters replace
references to s.currencies with s.currencies_filters (e.g., check/append to
s.currencies_filters and call s.currencies_filters.clear()), and update any
prose in this section to mention "currencies_filters" so it matches
src/settings.rs and src/ui/key_handler/settings.rs.

In `@src/ui/tabs/mostro_info_tab.rs`:
- Around line 38-45: The empty-state text built in the message variable
(constructed via Paragraph::new -> Line::from with Span::raw and Span::styled)
is outdated; replace the first or styled Span text to instruct users that they
can press Enter to refresh instead of telling them to restart or wait for a
future keybinding, keeping the italic style for the hint (update the
Span::styled content accordingly).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/ui/tabs/mostro_info_tab.rs`:
- Around line 18-37: The code builds a Layout with a single constraint and then
indexes chunks[1], causing an out-of-bounds panic; either change the render
target to chunks[0] in the None branch (replace f.render_widget(message,
chunks[1]) with chunks[0]) or update the Layout::new constraints array to
produce two slots (e.g., add a second Constraint) so chunks[1] exists—update the
code in the match over app.mostro_info where f.render_widget is called
accordingly.

---

Outside diff comments:
In `@src/ui/status.rs`:
- Around line 27-45: The current loop only appends the notification indicator
when iterating the last element, so if lines is empty the indicator never
renders; before the for (idx, line) in lines.iter().enumerate() loop (or replace
the loop body), add a special-case that checks if lines.is_empty() and, when
pending_notifications > 0, builds a spans Vec similar to the existing one
(create a primary Span::styled for an empty/placeholder line and then push the
indicator Span using the same blink_on logic and styles used for
indicator_style) so the notification is rendered even with no lines; keep using
the same symbols (lines, pending_notifications, blink_on, spans, Span::styled,
PRIMARY_COLOR, BACKGROUND_COLOR) so the styling logic remains consistent.

---

Duplicate comments:
In `@src/ui/tabs/mostro_info_tab.rs`:
- Around line 28-34: The empty-state text in the Paragraph built in
mostro_info_tab.rs currently tells users to "restart Mostrix to refresh or add a
manual refresh keybinding", which is incorrect because pressing Enter already
triggers a refresh via handle_enter_normal_mode in enter_handlers.rs; update the
Span::raw/Span::styled content inside the Paragraph::new(...) (the spans that
mention restart/refresh) to instead instruct users to press Enter to refresh
(matching the hint shown when info is loaded) so the empty-state and
loaded-state guidance are consistent.