fix: align feature marker seeding with GStack state

Wave-amended: seeding relocation re-applied to the composite action (v1.77 moved CI seeding out of the inline workflow steps the original commit edited); wiring tripwire re-pointed accordingly; stale marker comment updated

test/helpers/e2e-helpers.ts

@@ -324,7 +324,15 @@ if (evalsEnabled) {
   fs.mkdirSync(gstackDir, { recursive: true });
   // Marker list kept at parity with hermetic-env.ts's child-GSTACK_HOME seed
   // (the canonical set for the emission layer's gates).
-  for (const f of ['.activated', '.completeness-intro-seen', '.telemetry-prompted', '.proactive-prompted', '.first-loop-tip-shown']) {
+  for (const f of [
+    '.activated',
+    '.completeness-intro-seen',
+    '.telemetry-prompted',
+    '.proactive-prompted',
+    '.first-loop-tip-shown',
+    '.feature-prompted-continuous-checkpoint',
+    '.feature-prompted-model-overlay',
+  ]) {
     const p = path.join(gstackDir, f);
     if (!fs.existsSync(p)) fs.writeFileSync(p, '');
   }

test/helpers/hermetic-env.ts

@@ -217,7 +217,15 @@ export function getHermeticDirs(): HermeticDirs {
     // children — without these, the emission layer fires lake-intro/telemetry
     // prompts that burn turns and can stall PTY tests waiting on an answer.
     // Tests that exercise onboarding itself override GSTACK_HOME per-test.
-    for (const f of ['.activated', '.completeness-intro-seen', '.telemetry-prompted', '.proactive-prompted', '.first-loop-tip-shown']) {
+    for (const f of [
+      '.activated',
+      '.completeness-intro-seen',
+      '.telemetry-prompted',
+      '.proactive-prompted',
+      '.first-loop-tip-shown',
+      '.feature-prompted-continuous-checkpoint',
+      '.feature-prompted-model-overlay',
+    ]) {
       fs.writeFileSync(path.join(gstackHome, f), '');
     }
     // The privacy stop-gate is config-keyed, not marker-keyed: on machines