chore: mark US-006 as passing, update progress log

Author: LoCoBench Bot

prd.json

@@ -90,8 +90,8 @@
         "Both tasks registered in configs/selected_benchmark_tasks.json and nlqa_2config.sh"
       ],
       "priority": 6,
-      "passes": false,
-      "notes": "VS Code: src/vs/workbench/services/extensions/electron-sandbox/nativeExtensionService.ts, ExtensionHostProcess. Cilium: pkg/datapath/loader/, pkg/policy/, pkg/maps/. Both require understanding process/component isolation boundaries."
+      "passes": true,
+      "notes": "VS Code v1.99.3 (17baf841). Cilium v1.17.9 (a2f97aa8). 4 questions each: process isolation, IPC/deployment, crash handling/policy distribution, isolation mechanisms/map scoping. Ground truth: 8 findings, 5 file refs, 2 causal chains, 2 negative checks per task."
     }
   ]
 }

progress.txt

@@ -128,3 +128,33 @@
   - argoproj/argo-cd repo uses Apache-2.0 license (not BUSL like Terraform)
   - Used exploratory agent to research Argo CD architecture efficiently — comprehensive findings in ~5 minutes
 ---
+
+## 2026-02-16 - US-006
+- Created nlqa-debug-001: VS Code extension host crash isolation Q&A task
+- Created nlqa-debug-002: Cilium eBPF fault isolation Q&A task
+- Files created:
+  - benchmarks/ccb_nlqa/nlqa-debug-001/ (task.toml, instruction.md, Dockerfile, ground_truth.json, test.sh)
+  - benchmarks/ccb_nlqa/nlqa-debug-002/ (task.toml, instruction.md, Dockerfile, ground_truth.json, test.sh)
+- Files modified:
+  - configs/nlqa_2config.sh (added nlqa-debug-001 and nlqa-debug-002 to ALL_TASK_IDS and TASK_SG_REPO_NAMES)
+  - configs/selected_benchmark_tasks.json (added nlqa-debug-001 and nlqa-debug-002 entries, updated total_selected from 192 to 194)
+  - prd.json (marked US-006 as passes=true)
+- **Learnings for future iterations:**
+  - VS Code v1.99.3 commit SHA: 17baf841131aa23349f217ca7c570c76ee87b957
+  - Key VS Code extension host isolation files: nativeExtensionService.ts, abstractExtensionService.ts, extensionHostManager.ts, utilityProcess.ts, extensionHostStarter.ts, localProcessExtensionHost.ts
+  - VS Code extension host runs as Electron utility process (separate PID), not same-process thread or web worker
+  - ExtensionHostCrashTracker implements 5-minute / 3-crash auto-restart policy
+  - IPC via MessagePort/MessageChannelMain, crash detection via onExit event listener
+  - Detached process on Windows (detached: !!platform.isWindows) to prevent cascading termination
+  - Cilium v1.17.9 commit SHA: a2f97aa8d2de4bb360bee1e295e20556ce4166ce
+  - Key Cilium eBPF isolation files: pkg/datapath/loader/base.go, pkg/datapath/linux/config/config.go, pkg/endpoint/endpoint.go, pkg/maps/, pkg/bpf/map_linux.go, bpf/node_config.h
+  - Cilium deployed as DaemonSet (one cilium-agent per node), each agent independently compiles/loads eBPF programs
+  - Per-node eBPF compilation uses node_config.h with node-specific #defines (kernel features, enabled options)
+  - eBPF programs attach to kernel-local TC hooks via netlink, no inter-node coordination
+  - BPF maps pinned to /sys/fs/bpf (node-local filesystem), either PIN_GLOBAL_NS or PIN_OBJECT_NS scoping
+  - CiliumNetworkPolicy CRDs distributed cluster-wide via Kubernetes API, but enforcement is per-node (each agent independently regenerates BPF programs)
+  - Datapath forwarding/policy enforcement doesn't require kvstore (etcd) availability — policies materialized into local BPF
+  - Debugging Q&A tasks require "why does this happen?" framing, not "how do I fix this?" — focus on architectural isolation mechanisms, not bugs
+  - Negative checks should prevent blaming wrong abstraction layers (e.g., same-process vs separate process, centralized vs distributed compilation)
+  - Used parallel exploratory agents (2 concurrent tasks) to research VS Code and Cilium simultaneously — saved significant time
+---