@techierathore/techieflow 1.0.4 → 1.1.1

package/.tfcore/utils/tf_roadmap.py

@@ -0,0 +1,35 @@
+"""tf_roadmap.py — which checklist rows are roadmap items, out of this phase's scope.
+
+A row is a roadmap item when its acceptance line in the checklist's detail section carries
+"Roadmap — not in this phase's scope" (any dash, any case). Such a row is not work for this
+phase: it stays off the build list and out of the "not built yet" count, and it never makes
+*build-phase the next command. Only the owner moves it, through *amend-docs.
+
+AppManager's REQ-NFR-008 carried the marker at In Progress; tf-build-list.py put it on the
+working list with a builder prompt, a builder built it against the owner's decision, and
+tf-status-facts.py named *build-phase as the next command for it forever (TF-017).
+tests/regression/run.sh am_017. Imported by tf-build-list.py and tf-status-facts.py.
+"""
+import re
+
+MARK = re.compile(r"roadmap\s*[—–-]+\s*not in this phase['’]?s scope", re.I)
+ACCEPTANCE = re.compile(r"\*Acceptance:?\*|^\s*[-*]\s*Acceptance:", re.I)
+OWNER = re.compile(r"<a id=['\"]d-(req-[a-z]+-\d+)['\"]|\*\*`?(REQ-[A-Z]+-\d+)`?\*\*", re.I)
+
+
+def ids(text):
+    """The set of REQ ids whose acceptance line carries the roadmap marker.
+
+    The owner of an acceptance line is the nearest REQ anchor or bold REQ id above it, in the
+    detail section; status-table rows (lines starting with `|`) are never read."""
+    out, owner = set(), None
+    for line in text.splitlines():
+        if line.lstrip().startswith("|"):
+            continue
+        if re.match(r"^#{1,2}\s", line):
+            owner = None
+        for m in OWNER.finditer(line):
+            owner = (m.group(1) or m.group(2)).upper()
+        if owner and ACCEPTANCE.search(line) and MARK.search(line):
+            out.add(owner)
+    return out

package/.tfcore/utils/tf_stack_check.py

@@ -0,0 +1,93 @@
+#!/usr/bin/env python3
+"""tf_stack_check.py — does the code use the packages the Architecture requires? (2026-10-08)
+
+    bash .tfcore/utils/tf-stack-check.sh <App> [--json-out <file>]
+
+Reads the `Required packages:` line of docs/<App>-Architecture.md (Stack decisions), which copies the
+answer set's own line: each package in backticks, or "none". Then looks for each package in the
+project's dependency files, whatever the stack: .csproj/.fsproj/.vbproj, Directory.*.props,
+packages.config, package.json, requirements*.txt, pyproject.toml, Pipfile, go.mod, Cargo.toml, Gemfile,
+pom.xml, build.gradle(.kts), composer.json, pubspec.yaml. Build output, dependencies, tests/.artifacts
+and the framework itself are not searched.
+
+Why: in the first *develop-end-to-end proof on OpenCode the model searched for a package by the wrong
+name, decided the mandated UI library was not published, built the screen with plain components and
+had every row Verified. Nothing checked that the code used what the Stack decisions named.
+
+Prints PASS (every package referenced), FAIL (with the packages missing), or NONE (no line, or
+"none"). tf-verify-verdict.py runs it itself and fails every row's build check on FAIL.
+Exit 0 PASS or NONE · 1 FAIL · 2 could not run. Python 3 standard library only.
+"""
+import json
+import os
+import re
+import sys
+
+PRUNE = {"bin", "obj", "node_modules", ".git", ".artifacts", ".tfcore", ".claude", ".opencode", "dist",
+         "packages", "TestResults", ".venv", "venv", "target", "vendor", "OldDocs"}
+NAMES = re.compile(r"(?i)^(?:.*\.(?:cs|fs|vb)proj|directory\.(?:packages|build)\.props|packages\.config|package\.json|"
+                   r"requirements[\w.-]*\.txt|pyproject\.toml|pipfile|go\.mod|cargo\.toml|gemfile|pom\.xml|"
+                   r"build\.gradle(?:\.kts)?|composer\.json|pubspec\.yaml)$")
+
+
+def required(root, app):
+    """-> (list of packages, the Architecture path) ; [] when there is no line or it says none."""
+    p = os.path.join(root, "docs", f"{app}-Architecture.md")
+    if not os.path.isfile(p):
+        return [], p
+    for line in open(p, encoding="utf-8", errors="replace"):
+        m = re.match(r"\s*(?:[-*]\s*)?\**Required packages:?\**:?\s*(.*)$", line, re.I)
+        if m:
+            return re.findall(r"`([^`\s]+)`", m.group(1)), p
+    return [], p
+
+
+def manifests(root):
+    for d, dirs, files in os.walk(root):
+        dirs[:] = [x for x in dirs if x not in PRUNE and not x.startswith(".")]
+        for f in files:
+            if NAMES.match(f):
+                yield os.path.join(d, f)
+
+
+def check(root, app):
+    pkgs, arch = required(root, app)
+    if not pkgs:
+        return {"verdict": "NONE", "architecture": os.path.relpath(arch, root), "required": [], "missing": [], "found": {}}
+    found = {}
+    files = list(manifests(root))
+    for f in files:
+        try:
+            text = open(f, encoding="utf-8", errors="replace").read()
+        except OSError:
+            continue
+        for pk in pkgs:
+            if re.search(r"(?<![A-Za-z0-9._-])%s(?![A-Za-z0-9._-])" % re.escape(pk), text, re.I):
+                found.setdefault(pk, os.path.relpath(f, root))
+    missing = [pk for pk in pkgs if pk not in found]
+    return {"verdict": "FAIL" if missing else "PASS", "architecture": os.path.relpath(arch, root),
+            "required": pkgs, "missing": missing, "found": found, "files_searched": len(files)}
+
+
+def main(argv):
+    if len(argv) < 2 or argv[1] in ("-h", "--help"):
+        print(__doc__)
+        return 0 if len(argv) >= 2 else 2
+    app = argv[1]
+    r = check(os.getcwd(), app)
+    if "--json-out" in argv:
+        out = argv[argv.index("--json-out") + 1]
+        os.makedirs(os.path.dirname(out) or ".", exist_ok=True)
+        json.dump(r, open(out, "w"), indent=1)
+    if r["verdict"] == "NONE":
+        print(f"NONE {app}: {r['architecture']} lists no required packages")
+    elif r["verdict"] == "PASS":
+        print(f"PASS {app}: " + ", ".join(f"{k} in {v}" for k, v in r["found"].items()))
+    else:
+        print(f"FAIL {app}: the Architecture requires {', '.join(r['missing'])}; no project file references "
+              + ("it" if len(r["missing"]) == 1 else "them") + f" ({r['files_searched']} searched). Add the package; never replace it with a workaround")
+    return 1 if r["verdict"] == "FAIL" else 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))

package/README.md

@@ -27,6 +27,8 @@ Three things make it different from prompting an agent by hand:
 - **Rules that were ignored became hooks.** Eight guards refuse an action outright and print why: any git write, a malformed status file, `Verified` without a verify run, a hand edit of a telemetry file, a database write outside build and fix, run material at the repository root, a backgrounded build in unattended mode, and ending a turn with the status gate incomplete.
 - **The work is measured.** Five append-only streams per project record what each command cost, which check caught which failure, and what each miss cost to fix.
 
+The framework has an opinion about how agents talk to people. Every project's `AGENTS.md` (written at day-1) tells the agent to tag each claim it is unsure of as Certain, Likely or Guessing; to say the thing you will not want to hear first; to skip warm-up and start with the most useful sentence; and to disagree in a fixed shape ("I disagree because … I would do … The risk in your approach is …") and then do what you decide.
+
 The framework is technology-neutral. It asks a set of stack questions at day-1 and records the answers in the project's Architecture document; an answer set can fill them in (the owner's .NET set ships as `docs/TechieFlow-Stack-Defaults-DotNet.md`).
 
 ---
@@ -35,6 +37,8 @@ The framework is technology-neutral. It asks a set of stack questions at day-1 a
 
 Prerequisites are one-time per machine and live in [`docs/TechieFlow-Setup.md`](docs/TechieFlow-Setup.md): the toolchain, headless Chromium, and — for mobile heads — the Appium device hosts. **`python3` is required**; the guard hooks fail open without it.
 
+It runs on Linux, WSL and a stock Mac. On a Mac the scripts use Apple's own bash 3.2 and BSD tools, so Homebrew, a newer bash and GNU coreutils are not needed; `python3` comes with the Command Line Tools (`xcode-select --install`).
+
 Copy the framework in; never `npm install` it. All three scripts locate the framework from their own directory, so invoke whichever machine's copy you are on.
 
 ```bash
@@ -82,7 +86,7 @@ flowchart TD
 
 **An existing application** is the same after day-1: `*day1-brownfield` reads the code, writes the same documents plus the DevGuide, and migrates any existing plan into the one checklist.
 
-**Which command next?** Pick by the weakest open row: anything unbuilt means `*build-phase`; all built but not verified means `*verify all`; all verified means `*handoff-phase`. When in doubt, build. If a session died mid-phase, the status file is stale — run `*refresh-status {App}` first, which rebuilds it from the checklist, the working tree and a fresh build.
+**Which command next?** Pick by the weakest open row: anything unbuilt means `*build-phase`; all built but not verified means `*verify all`; all verified means `*handoff-phase`. When in doubt, build. A project in phases verifies one phase at a time: `*verify all {App} --phase 1` grades phase 1's checklist, and `--phase all` grades every phase in turn. Without `--phase` it grades the phase in progress. PROJECT-STATUS prints the exact line to paste. If a session died mid-phase, the status file is stale — run `*refresh-status {App}` first, which rebuilds it from the checklist, the working tree and a fresh build.
 
 **Running unattended.** Do not start a long run as a bare harness command. The supervisor survives a usage limit, a crash and an agent that stops early:
 
@@ -106,7 +110,7 @@ Replace `{App}` with your application name. Claude Code takes the long persona p
 | A change to an existing project | `… analyst *amend-docs {App} "<what changed>"` | `/flow-analyst *amend-docs {App} "…"` |
 | Brainstorm, brief, research | `… analyst *brainstorm {topic}` · `*create-project-brief` · `*research-prompt {topic}` | same, on `/flow-analyst` |
 | Build everything open | `/TechieFlow:agents:flow-master *build-phase {App}` | `/flow-master *build-phase {App}` |
-| Verify | `/TechieFlow:agents:verifier *verify ui\|functional\|all` | `/flow-verifier *verify all` |
+| Verify | `/TechieFlow:agents:verifier *verify ui\|functional\|all {App} [--phase N\|all]` | `/flow-verifier *verify all {App} [--phase N\|all]` |
 | Bugs: log and analyse only | `… flow-master *triage-issues {App} {evidence} [verify]` | `/flow-master *triage-issues …` |
 | Bugs: fix them | `… flow-master *fix-issues {App} {folder}` | `/flow-master *fix-issues …` |
 | Bugs: the whole sequence unattended | `… flow-master *triage-and-fix {App} {evidence}` | `/flow-master *triage-and-fix …` |

package/docs/TechieFlow-Installation.md

@@ -16,14 +16,16 @@ You need four things on the machine.
 | Tool | Why | Check |
 |---|---|---|
 | Node.js 20 or newer | Runs the installer. Nothing is added to your project. | `node --version` |
-| bash | The framework's guard hooks and helper scripts run under bash. macOS and Linux have it. On Windows, work inside WSL or Git Bash. | `bash --version` |
+| bash | The framework's guard hooks and helper scripts run under bash. macOS and Linux have it; the bash 3.2 that comes with macOS is enough. On Windows, work inside WSL or Git Bash. | `bash --version` |
 | Python 3 | Powers the HTML renderer, the telemetry writer and the guard hooks. | `python3 --version` |
-| Claude Code or OpenCode | The harness that runs the agents. Either one. Both work from the same install. | `claude --version` or `opencode --version` |
+| Claude Code or OpenCode | The harness that runs the agents. Either one. Both work from the same install. The framework targets OpenCode 2; its plugin still loads on OpenCode 1.x. | `claude --version` or `opencode --version` |
 
 For a .NET project you also need the .NET SDK. Run `dotnet --version` to check.
 
 You do not need rsync, git on the command line, or a clone of this repository.
 
+**On a Mac.** A stock Mac is enough. The scripts run on Apple's own bash 3.2 and the `sed`, `date`, `stat` and `xargs` that come with macOS. You do not need Homebrew, a newer bash or GNU coreutils for them. The one thing to add is Python 3: it comes with Apple's Command Line Tools, so run `xcode-select --install` once if `python3 --version` asks for them. perl and rsync already ship with macOS. Your project's own tools, such as the .NET SDK, are installed as usual.
+
 ---
 
 ## 1. What gets installed
@@ -312,7 +314,7 @@ It installs the framework if it is not there yet, then removes the leftover pack
 |---|---|
 | The framework is under `node_modules/@techierathore/techieflow/` and nowhere else | You ran `npm install`. See section 9. Run `npx @techierathore/techieflow@latest install`. |
 | `bash was not found` | On Windows, run the command inside WSL or Git Bash. |
-| `python3 was not found` | Install Python 3 and run the command again. On macOS: `brew install python3`. On Ubuntu or WSL: `sudo apt-get install -y python3`. |
+| `python3 was not found` | Install Python 3 and run the command again. On macOS: `xcode-select --install` (Apple's Command Line Tools include python3), or `brew install python3`. On Ubuntu or WSL: `sudo apt-get install -y python3`. |
 | `Refusing to install into the framework itself` | You ran the command inside a clone of this repository. Pass `--target=<your project>`. |
 | `does not look installed` on update | The folder has no `.tfcore/`. Run `install` first. |
 | Claude Code does not show the `/TechieFlow:agents:analyst` command | Restart Claude Code in the project folder. Check that `.claude/commands/TechieFlow/agents/analyst.md` exists. |

package/opencode.jsonc

@@ -589,7 +589,7 @@
           "sudo *": "ask"
         }
       },
-      "description": "Vidur — autonomous verification (*verify ui|functional|all); writes verdicts into the checklist Requirements Status tables"
+      "description": "Vidur — autonomous verification (*verify ui|functional|all [--phase N|all]); writes verdicts into the checklist Requirements Status tables"
     },
     "trblazeui": {
       "prompt": "You are the TrBlazeUI sub-agent. Read `.opencode/command/trblazeui.md` (fall back, in order, to `.claude/commands/trblazeui.md`, `.claude/trblazeui.md`, `.trblazeui/TrBlazeUI-AI-Reference.md`) and fully adopt that persona and its operating guidelines — it is the authoritative persona. NuGet credentials are user-level (Windows native `%AppData%\\NuGet\\NuGet.Config`, macOS/Linux `$HOME/.nuget/NuGet/NuGet.Config`, Docker `/root/.nuget/NuGet/NuGet.Config` from `%USERPROFILE%\\.opencode-docker\\nuget\\NuGet.Config`); never put a PAT in the repository. In Docker, never assume a Windows config is decryptable and never install `maui-tizen`; verify the mounted config and use the Docker build ladder. If neither file exists (TrBlazeUI NuGet not yet deployed), report the exact source/auth failure instead of blindly running `dotnet build`. Otherwise act as an expert .NET/Blazor developer specializing in the TrBlazeUI component library: build UI screens to match the approved mockups (`docs/{AppName}-UIDesign.md` + `docs/mockups/*.html`), follow `docs/{AppName}-Coding-Standards.md`, tag work with `[REQ-UI-N]` in the checklist Remarks, log TrBlazeUI gaps to `docs/{AppName}-TrBlazeUI-Feedback.md`. Never run git or gh.",
@@ -833,6 +833,10 @@
       "template": "{file:./.tfcore/tasks/split-brd.md}",
       "description": "Split the BRD into the one docs/{App}-Checklist.md (REQ-UI/FN/RAG/NFR-* in a single Requirements Status table)."
     },
+    "techieflow:tasks:develop-end-to-end": {
+      "template": "{file:./.tfcore/tasks/develop-end-to-end.md}",
+      "description": "A new app from a brief to UAT, unattended: Day 1 both stages, build with inline verify and fixes, handoff; tf-develop.sh commits and pushes after each phase and writes the Build Report with time and tokens per phase. Driven by /flow-master."
+    },
     "techieflow:tasks:build-phase": {
       "template": "{file:./.tfcore/tasks/build-phase.md}",
       "description": "The single unified build: implement every open REQ (UI/FN/RAG/NFR) from the one Checklist by clustering and calling /trblazeui (from mockups) + /techierag as sub-agents; self-smoke (data + visual); chain the verifier. Driven by /flow-master."
@@ -855,7 +859,7 @@
     },
     "techieflow:tasks:verify-phase": {
       "template": "{file:./.tfcore/tasks/verify-phase.md}",
-      "description": "Verifies every checklist row in a scope (ui | functional | all | REQ list) against the running app: boots it, runs the seven checks in order through the tf-verify-* scripts, writes the verdicts into the checklist and the telemetry. YOLO by default. Driven by /verifier."
+      "description": "Verifies every checklist row in a scope (ui | functional | all | REQ list) of one phase's checklist, or each phase in turn with --phase all, against the running app: boots it, runs the seven checks in order through the tf-verify-* scripts, writes the verdicts into the checklist and the telemetry. YOLO by default. Driven by /verifier."
     },
     "techieflow:tasks:handoff-phase": {
       "template": "{file:./.tfcore/tasks/handoff-phase.md}",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techierathore/techieflow",
-  "version": "1.0.4",
+  "version": "1.1.1",
   "description": "TechieFlow: a spec-driven development framework for AI coding agents, for Claude Code and OpenCode. One command installs it into any project.",
   "license": "Apache-2.0",
   "repository": {

package/scripts/install.mjs

@@ -392,6 +392,15 @@ const canonicalSettings = String.raw`{
             "command": "bash \"$CLAUDE_PROJECT_DIR/.tfcore/hooks/guard-verify.sh\""
           }
         ]
+      },
+      {
+        "matcher": "*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"$CLAUDE_PROJECT_DIR/.tfcore/hooks/yolo-allow.sh\""
+          }
+        ]
       }
     ],
     "SessionStart": [
@@ -723,7 +732,9 @@ function migrateLegacyLayout() {
   const rootConfig = join(target, "opencode.jsonc");
   if (existsSync(rootConfig) && legacyConfigPattern.test(read(rootConfig))) {
     copyFileSync(rootConfig, `${rootConfig}.bak`);
-    copyFileSync(join(sourceRoot, "opencode.jsonc"), rootConfig);
+    // the content only, as the shell's `cp` onto an existing file does: copyFileSync also copies the
+    // template's mode, so an executable checkout of opencode.jsonc gave a different file (CI, 2026-10-04)
+    writeFileSync(rootConfig, readFileSync(join(sourceRoot, "opencode.jsonc")));
     say("  opencode.jsonc — legacy version backed up to opencode.jsonc.bak, replaced with current template");
   }
   say("");
@@ -742,7 +753,7 @@ function refreshRootOpenCodeConfig() {
     if (dryRun) say("  opencode.jsonc — WOULD refresh from template (no project-only content; old file → .bak)");
     else {
       copyFileSync(rootConfig, `${rootConfig}.bak`);
-      copyFileSync(join(sourceRoot, "opencode.jsonc"), rootConfig);
+      writeFileSync(rootConfig, readFileSync(join(sourceRoot, "opencode.jsonc")));   // keeps its mode, as `cp` does
       say("  opencode.jsonc — refreshed from template (no project-only content; old file → opencode.jsonc.bak)");
       replaced = true;
     }