office: --new creates the Paperclip project, --remote adopts a folder on another machine

.harness/NOTES.md

@@ -0,0 +1,4 @@
+# harness-repo
+
+What this project is, what finished looks like, and anything a person
+picking it up next week needs to know. Notes only: tasks live in Paperclip.

.harness/check.sh

@@ -0,0 +1,15 @@
+#!/bin/sh
+# This project's own check, run by bin/merge before and after it puts a task's
+# work on the base branch. Exit 0 means "the project still passes".
+#
+# It does not decide that a task is finished: an agent sets a task's status, and
+# the review decides whether the change is good. This is the regression check,
+# the same thing a CI pipeline would run.
+#
+# Leave it as it is while the project has no tests. bin/merge will say there is
+# no check and let the review decide. Replace the body when tests exist:
+#
+#   exec go test ./...
+#   exec make test
+echo "this project has no check yet"
+exit 0

.harness/harness.toml

@@ -0,0 +1,14 @@
+# Written by bin/office. One project, one folder, one machine.
+# Paperclip owns the project, its tasks and its worktrees; this file only
+# remembers where the work is and what to show.
+
+session = "harness-repo"
+watching = ""
+
+[paperclip]
+company = "d4921013-e5da-4d88-8016-57d5746e2d03"
+project = "4e4bf84e-a0d6-4e40-94ae-ab2ac2fdc53c"
+
+[machine]
+host = "nixos-desktop"
+folder = "/home/sam/paseo/projects/paperclip-harness"