v3.14.1: the counter probe demands its PoR

_counter_probe_params validates SPI2, forces b1 (PoR required; a caller's
00 becomes 01) and defaults to the RAM listing transport 21; the no-PoR
error names the effective SPI2, and ramSyncCounter posts
ramListingSpi2('40') for the RAM view (the failed operation's transport).

Live 2026-10-02 (NP BAP): the probe had sent the plain SCP80 form's 00
(no PoR) - the card answered the ENVELOPE 9000 and sent nothing, so the
probe stopped after one packet with "card verdict: no PoR".

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

frontend/tests/ram.test.js

@@ -981,6 +981,8 @@ test('every SCP80/RAM flow checks the low counter and stops', () => {
 	assert.ok(sync.includes('kvnOf(other)'), sync);
 	assert.ok(sync.includes("getElementById('sp-cntr')"), sync);
 	assert.ok(sync.includes('spKeysetSync()'), 'the keyset labels must refresh');
+	assert.ok(sync.includes("ramListingSpi2('40')"),
+		'the RAM view must probe with the RAM listing transport (a PoR is required)');
 });
 
 test('the RAM form offers the command format choice', () => {