Skip to content

exo-408 items 10 and 14 (refused rail wording, LEZ preview from its real source); exo-a2a closed - #288

Closed
corpetty wants to merge 3 commits into
mainfrom
fix/spec-45e-probes
Closed

corpetty wants to merge 3 commits into
mainfrom
fix/spec-45e-probes

Conversation

@corpetty

Copy link
Copy Markdown
Owner
  • exo-408 item 14: the LEZ send preview prices from the account it will spend. wallet_estimate_fee took no source, so the preview always priced from the module's first LEZ account, the public one. A send from a shielded account previewed the public rail and its disclosure, while the send itself went private: the educational layer said something the code doesn't do. wallet_estimate_fee now takes from_id (empty = the module's account, as before), and the hosted estimate builds the source with its real form, as wallet_send does. Contract changed, surface regenerated; the backend passes the account the Send panel names.
  • exo-408 item 10: a refused rail choice says Propose is off, and why. Propose was already blocked (pickPending is in composeBlocked), but the line said "Propose waits while this proposal switches to …", and a refused switch never completes. It now says the proposal could not switch, with the reason.
  • exo-a2a: closed. Its spec's probes landed under exo-3f2 (a2d3819), and grade-specs.sh exo-45e grades 7/7.

Checks:

  • nim check of the hosted module is clean, and the regenerated surface has 92 methods.
  • The runner rebuilt with the new client.
  • scripts/ui-parity.sh with MUSTER_FLEET=local: 10 of 11 green in the table. The split test was red only for want of foundry on PATH, and it passes under nix shell nixpkgs#foundry.
  • ui-lint: 0 findings.

Still open in exo-408: 1, 11, 12, 15. The pebble notes that the Send panel's chain id is the LEZ adapter's own constant lez:testnet, so it matches the module; that's not a bug.

🤖 Generated with Claude Code

Item 10 of exo-408. A refused policy switch (a Bitcoin split with no
node, a private split with no LEZ wallet) leaves the previous policy in
force and pickPending set, which already keeps Propose off. But the
line under the picker said "Propose waits while this proposal switches
to …", and after a refusal it never switches. It now says the proposal
could not switch, with the reason from chainErrorWords. exo-a2a is
closed too: its spec's probes landed under exo-3f2 and it grades 7/7.

TDD-Exempt: wording on an existing gate; ui-lint 0 findings; no recorded fixture of a refused switch yet

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Session-Id: 4184ac11-a506-5256-a1c3-4f1e988410ce
… will spend

Item 14 of exo-408. wallet_estimate_fee took no source, so the LEZ
preview always priced from the module's first account there, the public
one. A send from a shielded account previewed the public rail and its
disclosure, while the send itself (wallet_send, which reads the source's
real form) went private. The educational layer then said something the
code does not do. wallet_estimate_fee now takes from_id (empty = the
module's account, as before); the hosted estimate builds the source
with its real form, as wallet_send does; the backend passes the account
the Send panel names. Surface regenerated.

TDD-Exempt: wiring on the hosted surface, which no suite test compiles; nim check of muster_module.nim clean; the runner build compiles the UI against the regenerated client

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Session-Id: 4184ac11-a506-5256-a1c3-4f1e988410ce
…s own

TDD-Exempt: tracker only

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Session-Id: 4184ac11-a506-5256-a1c3-4f1e988410ce
corpetty added a commit that referenced this pull request Oct 17, 2026
exo-408 items 10 and 14: refused rail wording; the LEZ preview prices from its real source (revives #288)
@corpetty

Copy link
Copy Markdown
Owner Author

Superseded by #329, the same commits rebased onto main, with muster_gen.nim regenerated and the Nim UI's caller updated. Re-tested and merged.


Generated by Claude Code

@corpetty corpetty closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant