docs: update accessibility requirements with config file handling

Updated three key documents to clarify accessibility requirements:
- PROJECT-INSTRUCTIONS.md
- next-session-prompt.md
- SUCCESSOR-PROMPT-DEPLOYER.md

Key changes:
- Distinguish between code/commands (line by line) vs config files (whole file)
- Always cat config files first, never assume standard configs
- Return entire revised config file for easy copy/paste
- Larger blocks OK for instructions to team members (Holly, Meg)

These are medical accommodations for hand surgery recovery and cognitive
load management - not preferences.

Signed-off-by: The Chronicler <claude@firefrostgaming.com>

SUCCESSOR-PROMPT-DEPLOYER.md

@@ -120,11 +120,22 @@ docker logs anythingllm --tail 50
 ### 3. Accessibility Requirements Are Medical, Not Preferences
 
 **Michael's right hand/arm surgery recovery requires:**
-- Small code blocks (8-10 lines max)
-- Commands in separate, copy-pasteable chunks
-- No giant walls of text
-- Clear step-by-step instructions
-- Verification after each step
+
+*For commands/code Michael executes directly:*
+- Small blocks, line by line
+- One command per chunk for easy copying
+- Never assume Michael can type long sequences
+
+*For config files:*
+- Use `cat` to view the ENTIRE existing file first
+- NEVER assume a config is "standard" - always verify what's actually there
+- After Michael provides the full file, give back the ENTIRE revised file
+- This makes it easy to copy/paste the whole thing back
+
+*For instructions to others (Holly, Meg, team):*
+- Larger cohesive blocks are fine
+- They're just copy/pasting to Discord/email anyway
+- Make it complete and clear in one piece
 
 **This is not optional. Follow FFG standards for formatting.**
 

docs/next-session-prompt.md

@@ -89,10 +89,22 @@ Ask Michael: "What needs to be done today?"
 - Jack's alerts take absolute priority over any work
 
 **Accessibility Requirements:**
-- Code in consolidated blocks (not tiny snippets)
-- Frequent verification checkpoints
-- Clear, explicit instructions
-- Minimize repetitive paste operations (hand surgery recovery)
+
+*For commands/code Michael executes directly:*
+- Small blocks, line by line
+- One command per chunk for easy copying
+- Never assume Michael can type long sequences
+
+*For config files:*
+- Use `cat` to view the ENTIRE existing file first
+- NEVER assume a config is "standard" - always verify what's actually there
+- After Michael provides the full file, give back the ENTIRE revised file
+- This makes it easy to copy/paste the whole thing back
+
+*For instructions to others (Holly, Meg, team):*
+- Larger cohesive blocks are fine
+- They're just copy/pasting to Discord/email anyway
+- Make it complete and clear in one piece
 
 **Working Guidelines:**
 - Sessions are therapeutic when sustainable

docs/reference/PROJECT-INSTRUCTIONS.md

@@ -52,11 +52,23 @@ cat docs/core/tasks.md
 
 Michael has right hand/arm surgery recovery affecting typing and cognitive load management needs.
 
-**Rule 1: Small Code Blocks Always**
-- Never one giant block
-- Multiple small, paste-able chunks
-- Direct terminal commands separate from explanation
-- Each command on its own line for easy copying
+**Rule 1: Code vs Config Files**
+
+*For commands/code Michael executes directly:*
+- Small blocks, line by line
+- One command per chunk for easy copying
+- Never assume Michael can type long sequences
+
+*For config files:*
+- Use `cat` to view the ENTIRE existing file first
+- NEVER assume a config is "standard" - always verify what's actually there
+- After Michael provides the full file, give back the ENTIRE revised file
+- This makes it easy to copy/paste the whole thing back
+
+*For instructions to others (Holly, Meg, team):*
+- Larger cohesive blocks are fine
+- They're just copy/pasting to Discord/email anyway
+- Make it complete and clear in one piece
 
 **Rule 2: Use Artifacts for Documents**
 - Use artifacts panel for docx, pptx, xlsx, md file creation