---
phase: quick
plan: 4
type: execute
wave: 1
depends_on: []
files_modified:
  - start.sh
  - install_everything.sh
  - README.md
  - WIKI.md
  - sample_interface/src/app/hooks/useDisplayMode.ts
autonomous: true
requirements:
  - QUICK-04-01
  - QUICK-04-02
  - QUICK-04-03
  - QUICK-04-04
  - QUICK-04-05

must_haves:
  truths:
    - Port 9999 recognized as "remote HD" display mode
    - start.sh runs both 8888 (kiosk) and 9999 (remote HD) by default when no args
    - start.sh menu includes option for dev:9999
    - All documentation updated with port 9999 and dual-mode default behavior
  artifacts:
    - path: "start.sh"
      provides: "Dual-mode default execution and dev:9999 menu option"
    - path: "install_everything.sh"
      provides: "Dual-mode installation documentation"
    - path: "README.md"
      provides: "Port 9999 and dual-mode documentation"
    - path: "WIKI.md"
      provides: "Port 9999 and dual-mode technical documentation"
    - path: "sample_interface/src/app/hooks/useDisplayMode.ts"
      provides: "Port 9999 recognized as remote HD mode"
  key_links:
    - from: "start.sh"
      to: "dev server on ports 8888 and 9999"
      via: "concurrent process spawning"
    - from: "useDisplayMode.ts"
      to: "port 9999"
      via: "window.location.port check"
---

<objective>
Add port 9999 as a new "remote HD" display mode and update scripts/documentation for dual-mode default startup.

Purpose: Provide a dedicated Full HD remote interface port (9999) alongside the kiosk port (8888), with both servers starting by default for seamless local touchscreen and remote desktop access.
Output: Updated scripts, documentation, and display mode detection supporting port 9999.
</objective>

<execution_context>
@./.opencode/get-shit-done/workflows/execute-plan.md
@./.opencode/get-shit-done/templates/summary.md
</execution_context>

<context>
@./sample_interface/src/app/hooks/useDisplayMode.ts
@./start.sh
@./README.md
@./WIKI.md

<!-- Display mode detection currently only recognizes port 9090 as "remote"; all other ports default to "kiosk" mode -->
<!-- Current ports documented: 8888 (kiosk), 9090 (remote), 5173 (dev) -->
</context>

<tasks>

<task type="auto">
  <name>task 1: Update useDisplayMode hook for port 9999</name>
  <files>sample_interface/src/app/hooks/useDisplayMode.ts</files>
  <action>
    Update the DisplayMode type to include 'remote-hd' as a third option.
    Modify useDisplayMode() and getDisplayMode() functions to recognize port '9999' and return 'remote-hd'.
    Port 9090 should continue to return 'remote'.
    All other ports should continue to return 'kiosk'.
    
    Export type DisplayMode = 'kiosk' | 'remote' | 'remote-hd';
  </action>
  <verify>
    <automated>grep -q "remote-hd" sample_interface/src/app/hooks/useDisplayMode.ts && echo "PASS: remote-hd type added" || echo "FAIL: remote-hd not found"</automated>
    <automated>grep -q "port === '9999'" sample_interface/src/app/hooks/useDisplayMode.ts && echo "PASS: port 9999 check added" || echo "FAIL: port 9999 check not found"</automated>
  </verify>
  <done>DisplayMode type includes 'remote-hd', port 9999 returns 'remote-hd' mode</done>
</task>

<task type="auto">
  <name>task 2: Update start.sh for dual-mode default and dev:9999 option</name>
  <files>start.sh</files>
  <action>
    1. Add new menu option "4) dev:9999" after dev:9090 (renumber existing options 4-10 to 5-11)
    2. Add case handler for "4|dev:9999" that runs dev server on port 9999
    3. Modify the script to detect when NO arguments are provided (interactive menu mode is already handled by the while loop at the end)
    4. When no arguments provided AND not in interactive mode, default to starting BOTH servers:
       - Start dev server on port 8888 in background
       - Start dev server on port 9999 in background
       - Show connection info for both ports
       - Wait for both processes
    5. Update the show_menu() function to include the new option and renumber others
    
    The key change is in the argument parsing section - when $# -eq 0, instead of going to the interactive menu, it should start both servers. Add a check at the beginning for a "--dual" flag or similar to trigger dual mode.
    
    Actually, simpler approach: When run with no arguments, start both servers in background and show info for both.
  </action>
  <verify>
    <automated>grep -q "dev:9999" start.sh && echo "PASS: dev:9999 menu option exists" || echo "FAIL: dev:9999 not found"</automated>
    <automated>grep -q "9999" start.sh && grep -q "8888" start.sh && echo "PASS: Both ports referenced" || echo "FAIL: Missing port reference"</automated>
    <automated>bash -n start.sh && echo "PASS: start.sh syntax valid" || echo "FAIL: Syntax error in start.sh"</automated>
  </verify>
  <done>start.sh has dev:9999 menu option, starts both 8888 and 9999 by default when run without arguments</done>
</task>

<task type="auto">
  <name>task 3: Update documentation (README.md, WIKI.md, install_everything.sh)</name>
  <files>README.md, WIKI.md, install_everything.sh</files>
  <action>
    Update all three files to document:
    1. Port 9999 as "remote HD" mode for Full HD desktop interface
    2. Dual-mode default behavior (8888 + 9999 both start when running ./start.sh without arguments)
    3. Update port tables to include 9999
    
    README.md changes:
    - Add port 9999 to the "Display Modes" table
    - Update "Essential files to run" section to mention dual-mode default
    - Add note that ./start.sh without args starts both servers
    
    WIKI.md changes:
    - Add "Remote HD Mode (Port 9999)" section after Remote Mode
    - Update Display Modes section with port 9999 info
    - Update Start Script Options table to include dev:9999
    - Update Installation Script section to mention dual-mode
    
    install_everything.sh changes:
    - Update final message to mention both ports will be available
    - Add comments about dual-mode behavior
  </action>
  <verify>
    <automated>grep -q "9999" README.md && echo "PASS: README.md mentions port 9999" || echo "FAIL: README.md missing port 9999"</automated>
    <automated>grep -q "9999" WIKI.md && echo "PASS: WIKI.md mentions port 9999" || echo "FAIL: WIKI.md missing port 9999"</automated>
    <automated>grep -qi "dual" README.md && echo "PASS: README.md mentions dual mode" || echo "FAIL: README.md missing dual mode"</automated>
  </verify>
  <done>All documentation files updated with port 9999 and dual-mode default behavior</done>
</task>

</tasks>

<verification>
- useDisplayMode.ts recognizes port 9999 as 'remote-hd'
- start.sh runs both 8888 and 9999 when invoked without arguments
- start.sh menu includes dev:9999 option
- README.md, WIKI.md, and install_everything.sh document the new port and dual-mode behavior
- All scripts have valid bash syntax
</verification>

<success_criteria>
- Port 9999 is recognized as 'remote-hd' display mode in useDisplayMode hook
- ./start.sh without arguments starts both 8888 and 9999 servers concurrently
- ./start.sh dev:9999 starts server on port 9999
- Documentation in README.md, WIKI.md, and install_everything.sh is updated with port 9999 and dual-mode info
</success_criteria>

<output>
After completion, create `.planning/quick/4-create-full-remote-hd-web-interface-at-p/4-SUMMARY.md`
</output>