v3.14.2: the counter probe's verdict rule

The ladder only advances on cntr_low; any other verdict stops the search.
A stop on a non-por_ok verdict after at least one cntr_low keeps the value
anyway - the earlier rejection proves it is above the card's counter - but
the response reports success: false with counter_saved, the verdict and the
saved counter ("something is likely wrong with the security settings");
the PWA shows it amber.  Without a prior cntr_low nothing is saved, and a
missing PoR stays an error.  actual_response_sms_submit/ussd count as
accepted.

Docs: docs/api.md, repo AGENTS.  sw cache simple-v377.
Tests: 672 Python + 798 frontend green.

This commit is contained in:

Антон Трошин

2026-10-02 14:58:18 +03:00

parent 475c13aeb8

commit 3c5882d16d

7 changed files with 117 additions and 20 deletions

									
										frontend/sw.js
									
		+1
		-1
	
												View File
												
				@@ -1,4 +1,4 @@

				const CACHE = 'simple-v376';

				const CACHE = 'simple-v377';

				const URLS = [

				  'index.html',

				  'help.html',