83 lines
3.9 KiB
Markdown
83 lines
3.9 KiB
Markdown
# Processor selection for disposable MCP playtests
|
|
|
|
> Technical evidence extract for the VCC Plus white paper. Only reviewed contracts, mechanisms, methods, results and limitations are retained. Original validation dates and configuration limits remain historical; this export is not a new test run.
|
|
|
|
## Discovery and starting a run
|
|
|
|
Export a fresh C Assistant connection with **Allow Disposable Playtests**.
|
|
Toolset 8 with `playtestProcessors: true` adds optional `processor` to
|
|
`start_playtest`. Earlier grants retain their schemas and MC6809 default.
|
|
This adds no tool: a fully enabled fresh C connection still advertises 28.
|
|
|
|
`get_capabilities` reports `playtest_processor_selection`,
|
|
`playtest_processors: ["MC6809", "HD6309"]` and
|
|
`playtest_default_processor: "MC6809"`. Use the live schema when choosing input.
|
|
|
|
```json
|
|
{
|
|
"name": "start_playtest",
|
|
"arguments": {
|
|
"project_id": "<current project>",
|
|
"revision": 0,
|
|
"artifact_id": "<current verified build>",
|
|
"request_id": "6309-entry-1",
|
|
"processor": "HD6309",
|
|
"stop_function": "main",
|
|
"stop_kind": "function_entry"
|
|
}
|
|
}
|
|
```
|
|
|
|
Omitting `processor` selects `MC6809`. Exact canonical names are required;
|
|
numeric values, `6309`, null and aliases are rejected. Explicit MC6809 and the
|
|
omitted default identify the same selection. An identical start request returns
|
|
its reserved run. Changing processor with that ID returns `request_id_conflict`.
|
|
|
|
Startup remains asynchronous: poll `get_run` until ready, failed or cancelled.
|
|
Pending receipts report `requested_processor` without claiming an observed
|
|
execution mode. Once ready, the worker receipt reports actual CPU state.
|
|
|
|
## Actual processor and execution mode
|
|
|
|
Worker receipts, captures and owned debugger snapshots report:
|
|
|
|
| Field | MC6809 | HD6309 |
|
|
| --- | --- | --- |
|
|
| `processor` | `MC6809` | `HD6309` |
|
|
| `requested_processor` | `MC6809` | `HD6309` |
|
|
| `execution_mode` | `not_applicable` | `emulation` or `native` |
|
|
| `md_register` | null | Actual MD byte |
|
|
| Legacy `cpu` in worker receipts | `6809` | `6309` |
|
|
|
|
The 6309 resets into emulation mode. Only guest instructions such as `LDMD`
|
|
change mode; the tool never sets MD. Mode is observed at each receipt's actual
|
|
stop. A guest that executes LDMD again after restart may therefore already be
|
|
native by its next stop. 6309 debugger registers additionally include actual
|
|
`E`, `F`, `W`, `V` and `MD`; W combines E/F. MC6809 snapshots omit those registers.
|
|
|
|
Existing code, bank, source, global and memory availability checks still apply.
|
|
A processor choice does not create C metadata or change a compiler target.
|
|
Build an artifact appropriate to the selected CPU. `restart_playtest` retains
|
|
the processor and writable disk. To change CPU, stop and start another run with
|
|
a new request ID. Retained disks may be resumed under either CPU after the usual
|
|
project, artifact and hash checks; compare actual run identities in test reports.
|
|
|
|
## Input, audio and limits
|
|
|
|
Ownership, revision, executable-byte verification, field, boot, mutation and
|
|
audio limits remain in force. Stop/retention remains available after execution
|
|
budgets are exhausted. Shared-run `send_keys` restrictions are unchanged.
|
|
|
|
`playtest_input` releases physical keys at the end of each bounded plan.
|
|
`capture_playtest_audio` also releases keys before and after its recording
|
|
interval; it records the following guest interval, not prior input or sound.
|
|
Do not use it to claim a continuously held moving-route test. See the
|
|
[audio contract](MCP_AUDIO_CAPTURE.md) and
|
|
[banked playtest contract](MCP_BANKED_PLAYTEST.md).
|
|
|
|
Qualification should run the same compatible disk on both CPUs and retain its
|
|
artifact hash, actual CPU/mode, boot/field identity, framebuffer, debugger/global
|
|
evidence and stop/retention receipts. Native-mode validation requires guest code
|
|
that really executes LDMD. The [build 45 record](MCP_BUILD45_VALIDATION.md)
|
|
identifies executed checks and their limits.
|