Harness spec 3.0.0-draft: context ids in the cases are hex; several files in one patch

conformance/context.json named results #g001…#k001, which are not the
lowercase hex context.md requires (an implementation that finds a result's id
at the head of the result by that rule cannot see them); they are #1001…#5001
now, with the same answers. Its `about` names the CLI's module,
session/results.ts.

context.md §5 says what it left open: a deleted file's bracket, and an
apply_patch over several files — the id alone, then each file in its own
bracket with its change, in the patch's order; a tool's note after the diff.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

harness/context.md

@@ -86,7 +86,20 @@ naming the path and the new content's hash:
 ```
 
 `write` of a new file answers `[#e202 docs/new.md sha 52b6e3a0] Created, 14 lines.` — the model
-wrote the content and has it. The diff is capped like any output.
+wrote the content and has it. A deleted file is `[#e203 old.md deleted]`. An `apply_patch` over
+several files answers the id alone, then each file in its own bracket with its change, in the
+patch's order:
+
+```
+[#e204]
+[src/a.ts sha 7d0a91c3]
+@@ -1,2 +1,2 @@
+[docs/new.md sha 52b6e3a0] Created, 14 lines.
+[old.md deleted]
+```
+
+A note the tool adds (a skill file written outside skill_manage) follows the diff. The diff is
+capped like any output, the first line kept.
 
 ## 6. The same search or listing twice is a stub