statusline

# procoder:statusline Thin wrapper over `node <plugin>/bin/procoder.js statusline`. The CLI owns the file handling; this skill only decides which subcommand to run and reports what it printed. ## Procedure 1. **Look first.** Run `statusline status` and report both lines it prints: the settings file, and what is configured there today. | Status says | Do | |---|---| | no statusLine configured | run `statusline install` | | installed | say so, stop — install would be a no-op | | installed, composed with an existing statusLine | say so, stop | | a statusLine that is not procoder's | step 2 | | removal was asked for | run `statusline uninstall` | 2. **Foreign statusLine — ask, do not replace.** Run `statusline install` without flags. It refuses, printing what is configured and what procoder would set. Show the user both and offer the two ways forward, in this order: - `--append` keeps their statusline and prints the badge after it. Both commands get the same session JSON on stdin, so a prompt reading `.cwd` keeps working; `uninstall` restores theirs byte for byte. POSIX only. - `--force` replaces theirs with the bare badge. Recommend `--append`, and re-run only after an explicit yes. That statusLine is their work. 3. **Report the result.** Name the settings file written, and the timestamped `.backup-<ms>` copy the CLI printed. Add one line: the badge appears at the next session start, not in this one. ## Output -...