Add posting guardrails to mach6-issue skill

package.json

@@ -39,7 +39,7 @@
 		"node": "22.x"
 	},
 	"packageManager": "npm@11.5.1",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"dependencies": {
 		"@dreb/coding-agent": "*",
 		"@mariozechner/jiti": "^2.6.5",

packages/agent/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/agent-core",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "General-purpose agent with transport abstraction, state management, and attachment support",
 	"type": "module",
 	"main": "./dist/index.js",

packages/ai/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/ai",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Unified LLM API with automatic model discovery and provider configuration",
 	"type": "module",
 	"main": "./dist/index.js",

packages/ai/test/context-overflow.test.ts

@@ -202,8 +202,8 @@ describe("Context overflow error handling", () => {
 	// =============================================================================
 
 	describe.skipIf(process.env.DREB_SKIP_LIVE_API === "1" || !process.env.GEMINI_API_KEY)("Google", () => {
-		it("gemini-2.0-flash - should detect overflow via isContextOverflow", async () => {
-			const model = getModel("google", "gemini-2.0-flash");
+		it("gemini-2.5-flash - should detect overflow via isContextOverflow", async () => {
+			const model = getModel("google", "gemini-2.5-flash");
 			const result = await testContextOverflow(model, process.env.GEMINI_API_KEY!);
 			logResult(result);
 

packages/ai/test/total-tokens.test.ts

@@ -203,10 +203,10 @@ describe("totalTokens field", () => {
 
 	describe.skipIf(process.env.DREB_SKIP_LIVE_API === "1" || !process.env.GEMINI_API_KEY)("Google", () => {
 		it(
-			"gemini-2.0-flash - should return totalTokens equal to sum of components",
+			"gemini-2.5-flash - should return totalTokens equal to sum of components",
 			{ retry: 3, timeout: 60000 },
 			async () => {
-				const llm = getModel("google", "gemini-2.0-flash");
+				const llm = getModel("google", "gemini-2.5-flash");
 
 				console.log(`\nGoogle / ${llm.id}:`);
 				const { first, second } = await testTotalTokensWithCache(llm);

packages/coding-agent/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/coding-agent",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"drebConfig": {

packages/coding-agent/skills/mach6-issue/SKILL.md

@@ -111,10 +111,13 @@ If templates exist, read them and select the most appropriate one.
 
 If codebase context is needed, use Explore subagents only for bounded evidence such as locating named behavior, files, tests, call sites, or exact snippets. The primary agent must interpret that evidence and own the issue's requirements, proposed behavior, scope, and technical conclusions.
 
-### Step 2: Draft the issue
+### Step 2: Draft and approve the issue
+
+An initial request to "create," "post," or "open" an issue is a request to draft it, **not approval to post it**. Never create an issue in the same turn as that initial request, regardless of how imperative or complete it is.
 
 Create a structured issue with:
 - **Title**: Clear, concise, action-oriented (under 80 chars, imperative form)
+- **Original Request**: A clearly identified block quote containing the user's original request/input verbatim; do not paraphrase, correct, or omit any part of it
 - **Summary**: 2-3 sentences describing the problem or feature
 - **Current Behavior** (for bugs/improvements): What happens now
 - **Proposed Behavior**: What should happen
@@ -123,16 +126,35 @@ Create a structured issue with:
 - **Technical Notes**: Implementation hints, relevant files, architectural considerations
 - **Labels**: Suggest appropriate labels based on the issue type
 
-Present the draft to the user for approval.
+Keep the issue limited to what the user explicitly requested. Before adding any acceptance criterion that the user did not explicitly ask for, present the proposed criterion separately with `ask_user` and obtain explicit confirmation that it is valid scope. Do not include an unrequested criterion without that confirmation, and do not treat approval of the completed issue draft as retroactive scope confirmation.
+
+Determine the candidate target repository as an exact `owner/repo`; do not rely on ambient `gh` context when posting. Use `ask_user` to present one Markdown-formatted approval question containing all of the following without summarizing or truncating them:
+- The exact target `owner/repo`
+- The complete issue title
+- The complete Markdown issue body, including the verbatim **Original Request** block quote
+- The complete proposed label list, or an explicit statement that no labels are proposed
+
+The question must offer exactly these three options and allow free-text discussion:
+- **Approve**
+- **Deny/Discuss**
+- **Detailed Explanation with minimal jargon of each acceptance criteria**
+
+Only an explicit selection of **Approve** authorizes posting. Free text, a skipped or unanswered question, cancellation, **Deny/Discuss**, or the explanation option are not approval and must never fall through to issue creation.
+
+If the user selects **Deny/Discuss**, discuss or revise the draft without posting. If the user requests the detailed explanation, explain every acceptance criterion with minimal jargon without posting. After either path, present the complete draft, target, and proposed labels through this approval gate again before posting. Any change to the title, body, target repository, or proposed labels invalidates prior approval and requires a fresh approval.
+
+Stop and wait for the distinct `ask_user` response before continuing to Step 3. The non-interactive `gh` rule applies only to CLI execution; it does not replace this human approval gate.
 
 ### Step 3: Create the issue
 
+Proceed only after the approval gate in Step 2 returned **Approve** for the exact title, body, target, and proposed labels used below.
+
 ```bash
 GH_BODY="$(mktemp /tmp/gh-body.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <body>
 MACH6_EOF
-gh issue create --title "<title>" --body-file "$GH_BODY" [--label "<labels>"]
+gh issue create --repo "<owner/repo>" --title "<title>" --body-file "$GH_BODY" [--label "<labels>"]
 ```
 
 Report the issue number and URL. Suggest next step: `/skill:mach6-plan <number>`

packages/coding-agent/test/skills.test.ts

@@ -539,6 +539,27 @@ describe("skills", () => {
 			}
 		});
 
+		it("mach6-issue should preserve CREATE-mode scope and posting guardrails", () => {
+			const body = readBuiltInSkill("mach6-issue");
+			expect(body).toContain("Never create an issue in the same turn as that initial request");
+			expect(body).toContain("user's original request/input verbatim");
+			expect(body).toContain("do not paraphrase, correct, or omit any part of it");
+			expect(body).toContain("Before adding any acceptance criterion that the user did not explicitly ask for");
+			expect(body).toContain("do not treat approval of the completed issue draft as retroactive scope confirmation");
+			expect(body).toContain("The exact target `owner/repo`");
+			expect(body).toContain("The complete issue title");
+			expect(body).toContain("including the verbatim **Original Request** block quote");
+			expect(body).toContain(
+				"The complete proposed label list, or an explicit statement that no labels are proposed",
+			);
+			expect(body).toContain("- **Approve**");
+			expect(body).toContain("- **Deny/Discuss**");
+			expect(body).toContain("- **Detailed Explanation with minimal jargon of each acceptance criteria**");
+			expect(body).toContain("Free text, a skipped or unanswered question, cancellation");
+			expect(body).toContain("title, body, target repository, or proposed labels invalidates prior approval");
+			expect(body).toContain('gh issue create --repo "<owner/repo>"');
+		});
+
 		it("mach6 CI workflows use watch_github_ci instead of polling or wait", () => {
 			for (const name of ["mach6-implement", "mach6-publish"]) {
 				const body = readBuiltInSkill(name);

packages/dashboard/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/dashboard",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Web dashboard for dreb — fleet overview, chat parity, subagent observability",
 	"license": "MIT",
 	"type": "module",

packages/semantic-search/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "semantic-search",
   "description": "Semantic codebase search — natural language queries over code and docs using embeddings, tree-sitter parsing, and POEM multi-signal ranking",
-  "version": "2.55.0",
+  "version": "2.55.1",
   "author": {
     "name": "Drew Brereton"
   },

packages/semantic-search/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/semantic-search",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Semantic codebase search engine with embedding-based ranking and MCP server",
 	"publishConfig": {
 		"access": "public"

packages/telegram/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/telegram",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Telegram bot frontend for dreb coding agent",
 	"license": "MIT",
 	"type": "module",

packages/tui/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/tui",
-	"version": "2.55.0",
+	"version": "2.55.1",
 	"description": "Terminal User Interface library with differential rendering for efficient text-based applications",
 	"type": "module",
 	"main": "dist/index.js",