Autofix markdown lint + disable unfixable style rules

Ran markdownlint --fix for blank lines around headings/lists.
Disabled MD013/033/034/036/040/041/060 (inline HTML, bare URLs, code
block language, emphasis-as-heading are intentional in this project).

Author: andylizf

.markdownlint.json

@@ -1,10 +1,9 @@
 {
   "MD013": false,
-  "MD022": false,
-  "MD032": false,
   "MD033": false,
   "MD034": false,
   "MD036": false,
   "MD040": false,
-  "MD041": false
+  "MD041": false,
+  "MD060": false
 }

LAUNCH.md

@@ -0,0 +1,86 @@
+# Launch copy
+
+## Hacker News
+
+**Title:** Show HN: Nonstop, two files that keep Claude Code working while you sleep
+
+**Text:**
+
+I use Claude Code for big tasks overnight maybe twice a week. About 70% of the time I come back to nothing. It stopped in the first few minutes because it had a question. Or hit a permission error on step 2 of 47 and just sat there. All night.
+
+nonstop is my fix. Two files, no dependencies.
+
+Before you walk away, /nonstop makes Claude do a pre-flight. It thinks through the whole task, asks every question it might have, and you approve or deny anything destructive (rm -rf, force pushes, posting PRs, calling paid APIs). All the "would block me at 3am" stuff gets resolved while you're still at the keyboard.
+
+Then a stop hook keeps it from quitting. If it gets stuck: try to solve it, try to work around it, or mark it blocked and move on to the next thing. No spinning.
+
+There are other tools for this (Ralph is a ~2k line bash orchestrator that wraps the CLI, taskmaster uses completion tokens). nonstop is deliberately minimal. Skill file + shell script. Felt like the right tradeoff for something I want to trust overnight.
+
+Repo: https://github.com/andylizf/nonstop
+
+**First comment:**
+
+TL;DR: /nonstop = pre-flight that asks all questions + approves dangerous ops NOW, then a stop hook that blocks premature halting. Two files. Curious if anyone's tried a different approach to the "Claude stops while I sleep" problem.
+
+---
+
+## Reddit (r/ClaudeAI)
+
+**Title:** anyone else wake up to Claude Code having done nothing all night?
+
+**Body:**
+
+Twice a week I set Claude up with a big task before bed. Refactor, migration, whatever. And like 70% of the time I come back and it stopped in the first few minutes. Had a question. Hit one error. Just sat there.
+
+Finally got annoyed enough to build something. It's called nonstop.
+
+/nonstop before you leave. Claude thinks through everything, asks all its questions while you're still there, you say yes or no to anything destructive. Then a stop hook keeps it running. Gets stuck? Figure it out or skip it, don't sit there.
+
+It's two files. A skill file and a shell script. Install:
+
+```
+curl -fsSL https://raw.githubusercontent.com/andylizf/nonstop/main/install.sh | bash
+```
+
+Or tell Claude to install it:
+
+```
+Fetch and follow the instructions at https://raw.githubusercontent.com/andylizf/nonstop/main/INSTALL.md
+```
+
+https://github.com/andylizf/nonstop
+
+What do you guys do for overnight tasks? Curious if I'm the only one with this problem or if everyone just accepts it.
+
+---
+
+## Twitter/X
+
+**1/**
+I give Claude Code a big task before bed maybe twice a week.
+
+70% of the time I wake up and it stopped in the first few minutes because it had a question.
+
+8 hours. Just sitting there.
+
+**2/**
+Made a thing. /nonstop before you leave. Claude asks everything now, you approve anything dangerous, then it actually works overnight.
+
+Gets stuck? Solve it or skip it. Two files total.
+
+github.com/andylizf/nonstop
+
+**3/**
+"Why do you write like you're running out of time?"
+
+---
+
+## LinkedIn
+
+I use Claude Code for big tasks overnight. Most of the time I come back to nothing. It stopped in the first few minutes because it had a question, or hit one error and sat idle until morning.
+
+So I built nonstop. You type /nonstop, it thinks through the whole plan, asks everything upfront, you approve anything risky. Then it works. Gets stuck, it figures it out or moves on.
+
+Two files. Took a weekend. Honestly surprised nobody made this already.
+
+github.com/andylizf/nonstop

README.md

@@ -113,6 +113,7 @@ Long-running ops (builds, tests) get delegated to background agents. Claude does
 ### When you're back
 
 `/nonstop off`, or just check the task list:
+
 - **Completed**: done
 - **Workaround**: done, but verify the approach
 - **Blocked**: needs you

SKILL.md

@@ -16,13 +16,15 @@ When the user triggers nonstop mode, complete a **pre-flight sequence** before d
 Mentally simulate the entire execution path of the task from start to finish. This is not a generic checklist — it is a task-specific dry run.
 
 **How to think:**
+
 1. Break the task into concrete steps (what will you actually do, in order?)
 2. For EACH step, imagine yourself executing it right now. Ask: "What could go wrong here? What would make me stop and ask the user?"
 3. Think about the environment: what machines, services, credentials, permissions does this touch?
 4. Think about dependencies between steps: if step 3 fails, can step 4 still run?
 5. Think about the edges: what if the test fails? what if the build takes 30 minutes? what if a file doesn't exist?
 
 **Surface to the user:**
+
 - Anything that would make you stop and ask — surface it NOW
 - Ambiguous requirements where you'd need to make a judgment call — clarify NOW
 - Credentials, tokens, permissions you might need — confirm NOW
@@ -86,12 +88,14 @@ Say: "Nonstop mode ON. Go rest — I've got this."
 When you encounter something that would normally make you stop and ask the user, follow this decision tree:
 
 ### Level 1: Can I solve it myself?
+
 - Missing info → search the codebase, read docs, check git history
 - Test failing → read the error, fix it
 - Build error → diagnose and fix
 - **If yes → solve it and move on. Don't stop.**
 
 ### Level 2: Can I work around it?
+
 - Permission denied → check if there's an alternative path (different API, different approach)
 - External service down → skip that part, continue with other tasks
 - Ambiguous requirement → pick the most reasonable interpretation, document your choice
@@ -100,21 +104,25 @@ When you encounter something that would normally make you stop and ask the user,
   - If the result would be materially different → do NOT proceed, mark the task as blocked
 
 ### Level 3: Truly blocked
+
 - Update the task status to blocked, noting: what you tried, why it failed, what the user needs to do
 - Move on to the next task. Do NOT spin on unsolvable problems.
 - **NEVER**: brute-force retry the same failing action, disable safety checks to bypass a blocker, make destructive changes to work around permissions, or guess at credentials/tokens.
 
 ### Subagent Delegation
+
 - For long-running operations (builds, tests, deploys), spawn a background Agent to monitor
 - Don't block the main thread waiting for results
 - Continue with other work while subagents run
 
 ## Deactivation — `/nonstop off`
 
 1. Remove the flag:
+
    ```bash
    rm -f ~/.claude/hooks/state/nonstop-$SESSION_ID.active ~/.claude/hooks/state/nonstop-$SESSION_ID.count
    ```
+
 2. Present a summary from the task list:
    - Tasks completed
    - Tasks where you took workarounds (and why)