Break shows registers it chose, not ones it inherited

Break left DP1 and DP2 alone, so what a stop printed for them was whatever the
shell happened to have left there - which is a CosmOS address, which moves
whenever CosmOS is touched at all. The recorded output had to be taken again
four times in one day's work, every time for a value that is not this program's
and that nothing should ever depend on.

It sets all three of the pointers it owns now, rotated between the two stops so
that every one of them visibly changes, the way A and B already did. DP3 stays
as the system left it: it is where the program was entered, which is the one
thing worth seeing here that this program did not choose, and it is steady
because it is this program's own base.

A demonstration of what the registers were should show registers somebody
chose. Then every line of the record is being asserted rather than merely
observed, and a reader can tell which is which.

Checked both ways: sixty four bytes added to CosmOS's data no longer moves it,
and reading the frame at the wrong offset still fails it.

cosmosRun and cosmosMonitor move because Break is sixteen bytes longer and both
of them list the disk it sits on.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Tests/expected/cosmosBreak.out

@@ -1,13 +1,13 @@
 CosmOS
 > loaded, starting at 4000
 > two stops, and what the registers were at each
-break at 400E
+break at 4016
 A 11 B 22 Q 00 status 00 
-DP0 2030 DP1 09F7 DP2 0000 DP3 4000 SP FFFF
+DP0 2030 DP1 2000 DP2 2037 DP3 4000 SP FFFF
 press a key 
-break at 4023
+break at 4033
 A 44 B 55 Q 00 status 00 
-DP0 2000 DP1 09F7 DP2 0000 DP3 4000 SP FFF5
+DP0 2000 DP1 2037 DP2 2030 DP3 4000 SP FFF5
 press a key 
 carried on to the end
 finished