Fix generated workflow worktree gates

.agentworkforce/trajectories/compacted/compact_l8eucbhnomb2_2026-04-27.json

@@ -0,0 +1,44 @@
+{
+  "id": "compact_l8eucbhnomb2",
+  "version": 1,
+  "type": "compacted",
+  "compactedAt": "2026-04-27T23:46:58.498Z",
+  "sourceTrajectories": [
+    "traj_148avjxsj8d4"
+  ],
+  "dateRange": {
+    "start": "2026-04-27T23:45:10.852Z",
+    "end": "2026-04-27T23:46:58.341Z"
+  },
+  "summary": {
+    "totalDecisions": 0,
+    "totalEvents": 0,
+    "uniqueAgents": []
+  },
+  "decisionGroups": [],
+  "keyLearnings": [],
+  "keyFindings": [],
+  "filesAffected": [],
+  "commits": [],
+  "narrative": "Single short session (≈1m) that added a wave10 executor workflow under `workflows/wave10-agent-assistant-adoption/` for agent-assistant adoption tasks, supporting both parallel and sequential modes, and updated `workflows/README.md` with usage notes. The trajectory captures only the retrospective summary — no decisions, findings, file diffs, or commits were recorded in the trail itself, though `git status` shows the untracked `workflows/wave10-agent-assistant-adoption/` directory and modified `workflows/README.md` consistent with the summary. The work fits the broader wave10 agent-assistant adoption initiative referenced in recent commits (e.g. a61a649 evaluating local execution contract reuse boundaries). Because the session was completed but not committed, the changes remain staged in the working tree awaiting review or follow-up. No retrospective confidence was logged and no challenges surfaced, suggesting this was a routine scaffolding task rather than an investigation.",
+  "decisions": [],
+  "conventions": [
+    {
+      "pattern": "Wave-scoped workflow directories under `workflows/<wave-slug>/` with parallel and sequential execution modes, indexed in `workflows/README.md`",
+      "rationale": "Keeps adoption-wave work discoverable alongside prior waves and consistent with the existing workflows layout",
+      "scope": "workflows/ directory; future wave executor additions"
+    }
+  ],
+  "lessons": [
+    {
+      "lesson": "Trajectories with only a retrospective and no recorded decisions/findings/commits provide little value for future agents",
+      "context": "This session logged only a one-line summary — file changes were visible only via `git status`, not the trail",
+      "recommendation": "For non-trivial scaffolding, record at least the target paths and the parallel-vs-sequential mode rationale via `trail decision`, and commit before `trail complete` so the trajectory links to a SHA"
+    }
+  ],
+  "openQuestions": [
+    "Were the wave10 workflow files committed after the session, or do they remain untracked in `workflows/wave10-agent-assistant-adoption/`?",
+    "What distinguishes the parallel vs sequential modes for this wave — task independence, rate limits, or ordering constraints?",
+    "Does this workflow integrate with the local execution contract reuse boundary evaluated in commit a61a649?"
+  ]
+}

.agentworkforce/trajectories/compacted/compact_l8eucbhnomb2_2026-04-27.md

@@ -0,0 +1,24 @@
+# Trajectory Compaction: 2026-04-27 - 2026-04-27
+
+## Summary
+Single short session (≈1m) that added a wave10 executor workflow under `workflows/wave10-agent-assistant-adoption/` for agent-assistant adoption tasks, supporting both parallel and sequential modes, and updated `workflows/README.md` with usage notes. The trajectory captures only the retrospective summary — no decisions, findings, file diffs, or commits were recorded in the trail itself, though `git status` shows the untracked `workflows/wave10-agent-assistant-adoption/` directory and modified `workflows/README.md` consistent with the summary. The work fits the broader wave10 agent-assistant adoption initiative referenced in recent commits (e.g. a61a649 evaluating local execution contract reuse boundaries). Because the session was completed but not committed, the changes remain staged in the working tree awaiting review or follow-up. No retrospective confidence was logged and no challenges surfaced, suggesting this was a routine scaffolding task rather than an investigation.
+
+## Key Decisions (0)
+| Question | Decision | Impact |
+|----------|----------|--------|
+| None identified |  |  |
+
+## Conventions Established
+- **Wave-scoped workflow directories under `workflows/<wave-slug>/` with parallel and sequential execution modes, indexed in `workflows/README.md`**: Keeps adoption-wave work discoverable alongside prior waves and consistent with the existing workflows layout (scope: workflows/ directory; future wave executor additions)
+
+## Lessons Learned
+- Trajectories with only a retrospective and no recorded decisions/findings/commits provide little value for future agents (This session logged only a one-line summary — file changes were visible only via `git status`, not the trail) - For non-trivial scaffolding, record at least the target paths and the parallel-vs-sequential mode rationale via `trail decision`, and commit before `trail complete` so the trajectory links to a SHA
+
+## Open Questions
+- Were the wave10 workflow files committed after the session, or do they remain untracked in `workflows/wave10-agent-assistant-adoption/`?
+- What distinguishes the parallel vs sequential modes for this wave — task independence, rate limits, or ordering constraints?
+- Does this workflow integrate with the local execution contract reuse boundary evaluated in commit a61a649?
+
+## Stats
+- Sessions: 1, Agents: None, Files: 0, Commits: 0
+- Date range: 2026-04-27T23:45:10.852Z - 2026-04-27T23:46:58.341Z