launchpad: row 300 (#1807): run 1 first-run red placed (mos-1272), the test's call helper resolves headers again as granted-user.test does; manifest re-hashed

agents/launchpad/work/queue-300/BUILD.md

@@ -44,3 +44,12 @@ file whole, the webui suite whole, then M12. Logs go to /mnt/storage/scratch/lau
 outside the tree. Not run yet.
 
 MANIFEST.sha256 lists the one new path.
+
+## Run 1 (sage-3408 CLEAR, 12:05Z)
+
+npm ci root and webui were green. The new file was red on its first run (mos-1272, placed by me):
+`TypeError: Cannot read properties of undefined (reading 'set-cookie')` in signIn. When I cut down
+granted-user.test.mjs's `call`, I dropped `headers: res.headers` from what it resolves, so the
+sign-in found no cookies. The fix puts `headers` back, the same as granted-user.test.mjs:40. No
+assertion changed. The new file then passed alone (1/0). The fix is a new commit, and the manifest
+is re-hashed. The gate resumes at new-file on the new head.

agents/launchpad/work/queue-300/MANIFEST.sha256

@@ -1 +1 @@
-e023bb9f8842ca8e6b5b4729ec0cae248627184be539ea1dbae811d78ec4704f  packages/webui/tests/user-option-swap.test.mjs
+03b5d60f68ea2bddd779e1df19519855a5f01cc28ec9ddb26ee7c45fcfe75cf4  packages/webui/tests/user-option-swap.test.mjs

packages/webui/tests/user-option-swap.test.mjs

@@ -41,7 +41,7 @@ function call(port, { method = 'GET', path = '/', headers = {}, body } = {}) {
     const req = request({ host: '127.0.0.1', port, method, path, headers: { host: HOST, ...length, ...headers } }, res => {
       let text = '';
       res.on('data', c => (text += c));
-      res.on('end', () => resolve({ status: res.statusCode, body: text }));
+      res.on('end', () => resolve({ status: res.statusCode, headers: res.headers, body: text }));
     });
     req.on('error', reject);
     req.end(body);