The chat screen stored the unsent message separately from the state cleared
by panic wipe, leaving old text visible after completion. Mention
suggestions could also put text back into the cleared input.
Cleared the input and its command and mention suggestions when the user
confirms the wipe. Rejected mention selections when suggestions are hidden
or the nickname is no longer in the current list, including older click
handlers and rows still visible during their closing animation.
The spam filter keeps recent message text and sender keys for its
repeat checks, and panic clear left them in memory. Reset the shared
filter as part of the panic wipe.
Add a broadcast_spam Mesh Lab scenario so messaging validation covers
both admitted and filtered public messages: B must show two
near-copies from A, hide the third, and still show A's next ordinary
message. It runs phone-to-phone and phone-to-watch.
The directory parser converted path-bearing and other unsupported URL
forms into relay endpoints. Updated it to reject those rows while keeping
valid neighboring entries, and refreshed the bundled CSV from the
configured source.
Added independent rejection cases and accepted port-boundary controls,
updated the documentation’s test references, and removed the unrelated
CommandProcessor test re-enablement from this PR’s changes.
Nine rejection cases failed with the previous parser and passed with the
change. Local tests and debug builds passed with three existing test skips;
lint added no diagnostics against the tested main baseline. Physical Mesh
Lab validation remains unperformed.
- The panic wipe announces success only when every data-at-rest stage
confirms: identity and signing-key prefs, Nostr keys, favorites, media,
bookmarks, and the conversation database. Each stage now returns
whether its wipe was committed instead of swallowing failures; any
failure shows the incomplete message.
- Add docs/PACKET_PAYLOAD_LIMITS.md for the per-type admission rules and
literal wire vectors with real DEFLATE bodies at and past the caps.
- Document the random sender ID in geohash envelopes.
Shared fixtures make the relay-selection rules executable on Android and
extracted iOS code. A partial-read regression reproduced the previous
cache-copy operation overwriting existing bytes before failing.
Added thirteen selection cases and documented the algorithm. Added
staged writes before atomic rename, cleanup attempts on refresh exit,
one refresh worker at initialization, and corrected status/error
interpolation. Restored three ignored tests. Atomic replacement depends
on filesystem support.
Local integration with main passed: 869 tests, zero failures or skips.
Debug builds passed; lint added no diagnostics against the tested main
baseline, which has existing errors and warnings. Cache-helper emulator
checks passed. Required physical Mesh Lab validation remains
unperformed.
A relay row with valid coordinates and a digit-only port outside the
integer range caused directory parsing to throw a NumberFormatException.
The surrounding load handlers caught the exception, but that parse
returned no relay list. This did not establish an application crash or a
delivery failure.
Changed the conversion to skip that row. Added a regression containing
valid rows before and after it, plus ordinary-port controls. Narrowed
the source, selection and test descriptions: sharing a source alone does
not establish equal loaded snapshots or successful message delivery.
Used the Kotlin preferences helper for asynchronous writes.
The integer-overflow port test reproduced the parsing failure before the
fix and passed afterward. The full test suites passed with three
unrelated skips, and debug builds passed. Lint reported errors and
warnings, with none in the changed files. Required physical Mesh Lab
validation remains unperformed.
Review follow-up from the automated pass. The selection tests carried a
real relay hostname and real city coordinates; AGENTS.md requires
synthetic, non-identifying fixtures. Both are replaced with clearly
synthetic values that keep the same shapes: the port-variant pair, the
one-coordinate tie group, and the duplicated nearest relay that used to
displace the fifth server.
The selection rules are also now recorded in
docs/client-rewrite-contracts.md, since agreeing clients are the point
of the change: same source file, same host key, same tie order.
Behavior is unchanged; RelayDirectoryTest covers it.