asks: the proof sees what the phone shows at a tap, and the question's outcome as its title (issue 372) #76

2026-10-10T12:14:22Z

mesh-admin commented

2026-10-10 12:14:22 +00:00

Issue 372 (tapping Approve or Decline on Telegram gives the operator no visible feedback). Stacked on #74 (the asks proof, not yet on main), so its base is that branch; merge after #74.

The fake Bot API now keeps each answerCallbackQuery text (the toast). TestTheOperatorsAnswerEndToEnd checks:

step 3: the toast says "You chose Approve: recorded…", no earlier than the warrant; the edited question opens with "You chose Approve at HH:MM on Telegram · …" and has no buttons;
step 4: the same Approve tapped again is toasted "You already chose Approve at HH:MM: recorded." (it used to be refused, which read as the approval failing).

Runs:

against mesh-catalog #175 (fix/372-a-tap-shows-its-outcome at 6b4cfc3), mesh-controller main, mesh-tools main: PASS in 191 s;
against mesh-catalog main (without the fix): FAIL at step 3, "the phone never showed the approval confirmed; it showed: """ (the empty acknowledgement the operator got at 13:30).

Do not merge without review; merge after mesh-catalog #175.

Issue 372 (tapping Approve or Decline on Telegram gives the operator no visible feedback). Stacked on #74 (the asks proof, not yet on main), so its base is that branch; merge after #74. The fake Bot API now keeps each `answerCallbackQuery` text (the toast). `TestTheOperatorsAnswerEndToEnd` checks: - step 3: the toast says "You chose Approve: recorded…", no earlier than the warrant; the edited question opens with "You chose Approve at HH:MM on Telegram · …" and has no buttons; - step 4: the same Approve tapped again is toasted "You already chose Approve at HH:MM: recorded." (it used to be refused, which read as the approval failing). Runs: - against mesh-catalog #175 (fix/372-a-tap-shows-its-outcome at 6b4cfc3), mesh-controller main, mesh-tools main: PASS in 191 s; - against mesh-catalog main (without the fix): FAIL at step 3, "the phone never showed the approval confirmed; it showed: \"\"" (the empty acknowledgement the operator got at 13:30). Do not merge without review; merge after mesh-catalog #175.

mesh-admin commented

2026-10-10 12:14:48 +00:00

Delivery novox/mesh-lab@7289edb276ec — rejected since 2026-10-10T12:38:42Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-10 12:14 (new) → proposed (announced): novox/mesh-lab#76's head announced
2026-10-10 12:17 proposed → checked (checked): the verdict names this commit
2026-10-10 12:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-10 12:37 rejected → proposed (recheck): its check ran against the base branch of mesh-lab #74, which is merged and deleted; the pull request now targets main
2026-10-10 12:38 proposed → checked (checked): the verdict names this commit
2026-10-10 12:38 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-lab@7289edb276ec` — **rejected** since 2026-10-10T12:38:42Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 12:14 (new) → proposed (announced): novox/mesh-lab#76's head announced - 2026-10-10 12:17 proposed → checked (checked): the verdict names this commit - 2026-10-10 12:17 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-10 12:37 rejected → proposed (recheck): its check ran against the base branch of mesh-lab #74, which is merged and deleted; the pull request now targets main - 2026-10-10 12:38 proposed → checked (checked): the verdict names this commit - 2026-10-10 12:38 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin changed target branch from proofs/asks-answered-on-the-phone to main

2026-10-10 12:15:08 +00:00

mesh-admin added 1 commit 2026-10-10 12:15:08 +00:00

asks: the proof sees what the phone shows at a tap, and the question's outcome as its title (hq issue 372)

mesh/merge-gate error: the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change:…

Details

mesh/repo-check error: the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change:…

Details

mesh/delivery rejected: the gate failed or could not run, or the repository's own check failed

Details

7289edb276

The operator approved on Telegram and saw nothing: the tap was acknowledged
with no words and the question kept its title. The proof now checks the toast
says the approval was recorded, no earlier than the warrant; that the edited
question opens with how it ended; and that the same answer tapped again is
said as already recorded, not refused.

mesh-admin commented

2026-10-10 12:17:03 +00:00

Merge check at 7289edb2

mesh/merge-gate: ERROR — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1
mesh/repo-check: ERROR — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1

Run by the build seat on shanks as build-1791634476742862802 (builds --log build-1791634476742862802).

**Merge check** at `7289edb2` - `mesh/merge-gate`: **ERROR** — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1 - `mesh/repo-check`: **ERROR** — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1 Run by the build seat on shanks as `build-1791634476742862802` (`builds --log build-1791634476742862802`).

mesh-admin commented

2026-10-10 12:38:42 +00:00

Merge check at 7289edb2

mesh/merge-gate: ERROR — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1
mesh/repo-check: ERROR — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1

Run by the build seat on shanks as build-1791635872772332363 (builds --log build-1791635872772332363).

**Merge check** at `7289edb2` - `mesh/merge-gate`: **ERROR** — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1 - `mesh/repo-check`: **ERROR** — the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change: exit status 1 Run by the build seat on shanks as `build-1791635872772332363` (`builds --log build-1791635872772332363`).

Some required checks failed

mesh/merge-gate error: the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change:…

Details

mesh/repo-check error: the check could not run: the base branch proofs/asks-answered-on-the-phone cannot be read, and the check it holds judges the change:…

Required

Details

mesh/delivery rejected: the gate failed or could not run, or the repository's own check failed

Details

This pull request has changes conflicting with the target branch.

asks/faketelegram_test.go
asks/proof_test.go

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin proofs/372-a-tap-shows-its-outcome:proofs/372-a-tap-shows-its-outcome

git checkout proofs/372-a-tap-shows-its-outcome

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#76