[JacobStephens2]

Summary

A README for someone else to run thirdshift, an MIT LICENSE, and credit to mattpocock/skills with its MIT notice shipped alongside the embedded Factory skills.

 ./
+├── README.md        # purpose, what a Run does, status, install, prerequisites,
+│                    # usage, logs, Continuation, Failed runs, credits
+├── LICENSE          # MIT, thirdshift
 ├── skills/
+│   ├── LICENSE      # MIT, Matt Pocock: embedded and written out with the skills
 │   ├── code-review/ …
 └── tests/fresh_run.rs
+    └── ships_the_mattpocock_skills_mit_notice_with_the_factory_skills

Everything from the comment on #11 is in the README: git identity, what sessions leave outside the worktree, installing toolchains up front, libgbm1 for headless Chromium, and subscription usage vs total_cost_usd.

Most of the designed behaviour (pre-flight, Continuation, Failed run, Repairs, progress lines) isn't built yet. The README describes the design, and a Status section says what works today and points to #2.

Tested seam: the thirdshift CLI. The new test runs the binary and checks that the plugin directory handed to claude contains skills/LICENSE with Matt Pocock's MIT notice.

Evidence

• Before: ships_the_mattpocock_skills_mit_notice_with_the_factory_skills fails: license: None
  After: cargo test: 9 passed. cargo fmt --check and cargo clippy --all-targets -- -D warnings are clean.

Note: include_dir! doesn't notice a newly added file under skills/ until the crate recompiles. Locally that took touch src/plugin.rs. CI and cargo install --path . build fresh, so they are unaffected.

Merge Danger

Door: two-way

Docs, license files and one test. The only runtime change is one extra file, skills/LICENSE, in the temp plugin directory.

Blast Radius: negligible

Unaddressed findings

Standards

• Duplicated Code / Message Chains (claude_calls()[0]["plugin_files"][…] in two tests): only two call sites. A Scenario::plugin_file helper can wait for a third, as the reviewer also suggested.
• README restates the CONTEXT.md definitions of Failed run and Continuation: the README is for users and CONTEXT.md is the glossary. A short restatement keeps the README readable on its own, and the bold terms link back to CONTEXT.md.

Spec

• Step 7 says cleanup happens "whether the Run succeeded or not", but Ctrl-C skips it today: that is the designed behaviour (The Failed run path #5), and the Status section already lists the Failed run path as not yet built.
• A malformed Issue URL exits 1 without the usage message: that's a code gap for pre-flight (Pre-flight checks #4), not a README error. The README describes the exit codes as they are today.

Closes #11

🤖 Generated with Claude Code