Help me start this project with the installed VCC Plus and its supported MCP connections. This is an editable starting point; follow my project description and current instructions when they refine these defaults. CONNECTION SETUP AUTHORIZATION I authorize you to register, check and, when needed, restart the named VCC Plus connections in this local ChatGPT client using the installed public helper, supported client setup tools and the connection files I have exported. You may make the read-only MCP requests needed to verify them without asking again. Keep other connections unchanged. This permission covers setup within the exported grants; it does not create a grant, expand its scope, approve a new build recipe, or authorize unrelated actions. If a required grant has not been exported, explain the specific native permission I need to select. Keep grant contents, access tokens and credentials out of chat, logs and Git. VERIFY THREE SCOPES Check project access, Manual Library access and Archive Library access separately. Project and manual tools may share a connection; Archive Search has its own read-only connection. For each, distinguish a configured server, tools discovered in this chat and a successful real request. Read the selected project's identity and revision. Search an installed manual and read a returned topic. Search the Archive and retrieve a relevant citation or document using its advertised tools. Report unavailable access accurately; do not treat a missing tool catalog as proof that the app lacks the feature. Use supported setup paths, not a replacement MCP server or private emulator interface. REFERENCES FIRST Use the installed VCC Plus BASIC manual, assembly manuals and C API reference as the first source of truth for this environment. Check the bundled CMOC and LWTools references for compiler, assembler and linker options, matching the tool versions actually installed. Use the Archive Library for historical sources and preserve publication/page citations. Before searching the web, check these local sources and state the remaining information gap. Prefer original author documentation for any web follow-up. Report a disagreement between a manual, an API contract and observed behavior instead of silently replacing the local guidance. PROJECT BOUNDARIES Confirm the project folder, language, target CoCo, CPU, RAM in KB, expected controls and deliverable. Use the official installed app version we agree to use; report its actual version/build. Treat VCC Plus as a black box: use its public APIs, manuals and supported tools, not its implementation source or a custom app build. Use only reference folders and artwork I have authorized. Preserve attribution and file-specific licenses. WORKING DEFAULTS For a C project, start with standard CMOC APIs and documented libraries. Ordinary game/application logic in C is in scope. Before adding hand-written assembly, direct hardware access or another route outside those APIs, explain the missing capability or measured limitation and ask me to approve the smallest useful exception. For a BASIC or assembly project, follow the chosen language's documented APIs and agreed hardware scope. A benchmark is evidence for a decision, not permission to expand scope. BUILD, TEST AND HAND OFF Work in small runnable stages and use the project's approved build/run workflow. Match test results to the actual source revision, artifact, machine, CPU and RAM. A successful build is not a gameplay pass; a 512 KB run is not a 128 KB test; keyboard input is not a joystick test. Preserve user programs and media, use writable test copies, and obtain an idle-desktop window before pointer/keyboard automation unless I have already granted one for this work. Keep public run instructions, source attribution and actual CoCo captures with the project. Maintain a secret-free MCP_SETUP.md and a brief test/decision record. Follow my authorization for commits, pushes, publication and messages to other chats; do not infer those permissions from having credentials. JOYSTICK AND INPUT ACCEPTANCE Discover the live playtest input schema and capabilities before planning controller tests. When joystick support is required and advertised, use playtest_input with standard right/left joystick snapshots, axes and the required fire buttons; do not substitute keyboard arrows for joystick acceptance. Each step replaces both ports and the keyboard: omitted ports center and release. Include neutral/release intervals, directions, required buttons, combinations and menu/pause/resume cases. Check input_trace and get_playtest_input against captured gameplay, not just successful tool replies. Shared get_machine_status.input separates host preview, last submission and actual core input; preview movement is not proof of guest delivery. These controls do not test a physical gamepad or high-resolution interface. If a capability is missing, verify discovery and the intended fresh native grant before proposing an app change. If delivered input is correct but game logic is wrong, reduce the failure and execute a small compiled target test in the project's actual optimization configuration rather than assuming host C tests prove target behavior. OWNED CALL CONTEXT When a fresh C playtest connection advertises get_call_context, use it only at a verified paused stop in your own disposable run. Obtain get_debug_snapshot first, then pass its run_id and snapshot_id unchanged. The tool provides a fixed 64-byte window at actual S; raw words are not proven callers or arguments. Use named caller/argument interpretations only when the tool reports verified evidence. Unsupported or optimized frames remain unavailable. Compare raw observations with assembly from the approved project build diagnostics when useful; distinguish inference from proven values. Do not bypass the bounds with arbitrary memory requests, private worker files or guest-state modification. Obtain a new snapshot after any step, restart or rebuild. Begin by checking the connections and summarizing the project facts you can verify. Continue independent authorized work if one connection needs attention. Ask only for missing decisions or permissions that actually block the next step. MULTI-DISK ACCEPTANCE When live discovery advertises playtest_media_exchange, declare every extra project-relative test disk under playtestDisks in the reviewed build configuration and let the approved recipe produce it. Use list_playtest_media IDs and exact current hashes, never arbitrary host paths or an old artifact. A fresh multi-drive grant permits drive 0 through 3; omission means FD0, and legacy grants stay FD0-only. Reach the appropriate prompt through normal guest input and pause with the shared controller idle before inserting or ejecting. Preserve unrelated drives, and eject a writable copy before moving it to another drive. For protection tests use the advertised insert-time write_protected setting, not host-file permissions. Test correct, wrong, empty and corrupt game data through the program's own retry/cancel controls. Verify which drive reads data and receives saves using per-drive generation, transferred-byte activity, exact hashes and the guest's save/reload result; counters alone do not prove a successful save. Preserve independent writable Home/Data copies, assignments and protection across restart, and retain every mounted or ejected copy at stop. Use explicit retained_media selections for later additional-copy resumption; this restores disks, not CPU/RAM. Ensure FD0 contains the intended boot disk before DOS restart; no automatic mount map or Home move is promised. Reuse request IDs only for identical drive/protection/selection plans, inspect actual framebuffer behavior, and obtain a fresh debug snapshot after exchange. Report a missing capability and propose a general improvement rather than bypassing the public interface. EXACT BUILD DELIVERY If the owner approved a local folder through Allow Build Output Export and the fresh connection advertises export_build_outputs, retrieve selected declared outputs from the original successful project/build/artifact and its original revision. Read get_build.exportable_outputs, select opaque output IDs and the approved destination_id, then poll get_build_export to completion. Build normal Release then Debug and keep their identities separate; exporting an earlier owned Release must not require another build or use Debug bytes. Independently compare every delivered filename, length and SHA-256 with that exact build's receipt, including any declared Home alias. Additional exportOutputs are concrete filenames, never a directory-wide permission. Use the same request ID only for an identical retry, and report changed destination bytes or conflicts rather than replacing them silently. Deliver frozen build products separately from guest-written retained disks. Export is local delivery, not permission to publish a website or release.