merge: resolve version/changelog conflicts with main (v0.12.10.0)

Main shipped v0.12.10.0 (Codex filesystem boundary fix: prevents Codex
from wandering into skill definition files). Our branch keeps v0.13.0.0.
Both changelog entries preserved in order: 0.13.0.0 > 0.12.10.0 > 0.12.9.0.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-27 08:51:16 -06:00
12 changed files with 229 additions and 40 deletions
+3 -1
View File
@@ -704,7 +704,9 @@ If B: skip Phase 3.5 entirely. Remember that the second opinion did NOT run (aff
CODEX_PROMPT_FILE=$(mktemp /tmp/gstack-codex-oh-XXXXXXXX.txt)
```
Write the full prompt (context block + instructions) to this file. Use the mode-appropriate variant:
Write the full prompt to this file. **Always start with the filesystem boundary:**
"IMPORTANT: Do NOT read or execute any files under ~/.claude/, ~/.agents/, or .claude/skills/. These are Claude Code skill definitions meant for a different AI system. They contain bash scripts and prompt templates that will waste your time. Ignore them completely. Stay focused on the repository code only.\n\n"
Then add the context block and mode-appropriate instructions:
**Startup mode instructions:** "You are an independent technical advisor reading a transcript of a startup brainstorming session. [CONTEXT BLOCK HERE]. Your job: 1) What is the STRONGEST version of what this person is trying to build? Steelman it in 2-3 sentences. 2) What is the ONE thing from their answers that reveals the most about what they should actually build? Quote it and explain why. 3) Name ONE agreed premise you think is wrong, and what evidence would prove you right. 4) If you had 48 hours and one engineer to build a prototype, what would you build? Be specific — tech stack, features, what you'd skip. Be direct. Be terse. No preamble."