row224: supply chief Gitea reference in new launch fixture

agents/della/work/queue-224/BUILD.md

@@ -445,3 +445,20 @@ test at packages/cli/tests/thread-launch.test.mjs:1:1
 ✖ packages/cli/tests/thread-launch.test.mjs (40023.3188ms)
   'Promise resolution is still pending but the event loop has already resolved'
 ```
+
+## sage-4204 — chief credential fixture correction (unrun)
+
+Sage's control pair with a 29-byte TMPDIR: base 3e5041b43 passes 14/14;
+ed985c044 passes all 14 existing tests but this row's new CLI fixture refuses
+chief-library-gitea-required before launch. Added only chief.credentials.gitea
+as a copy of the fixture coder's reference in the C2-05b edit callback, matching
+cli/tests/launcher.test.mjs:35 and trackers-boot.test.mjs:17. This is a reference
+to synthetic fixture credentials; no credential value was read or introduced.
+All assertions, old tests and production code unchanged. No run performed.
+
+The earlier 48-byte TMPDIR explains the launch-failed reds through the
+107-byte tools.sock limit, as confirmed by Sage's control. Future named CLEAR
+uses shell TMPDIR=$(mktemp -d /mnt/storage/scratch/tmp/gXXX), 29 bytes with
+alphanumeric suffix, not Python mkdtemp or a canonical node_modules link.
+Next authorized run order: whole thread-launch first, other eight files, whole
+bus/harness suites, M-B1; all await next CLEAR after Fethry/Gyro slots.

packages/cli/tests/thread-launch.test.mjs

@@ -540,6 +540,7 @@ test('C2-09a: terminating one creative thread does not signal an unselected peer
 test("C2-05b a real launched bundle gets lookups for a library project without a library checkout", { skip, timeout: 60000 }, async t => {
   const prepared = prepare(t, { idle: 10, edit: doc => {
     doc.projects.books = mappingEntry();
+    doc.roles.chief.credentials = { gitea: { ...doc.roles.coder.credentials.gitea } };
     return doc;
   } });
   const { f } = prepared;