nobrainer-tech-flow 2.5.0 → 2.7.0

package/.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
     {
       "name": "nobrainer-tech-flow",
       "description": "From task to done. nobrainer-tech-flow is one workflow of 18 modules for AI coding agents: it scopes the task, delegates ready work, checks the result and hands over the evidence, including what was not checked.",
-      "version": "2.5.0",
+      "version": "2.7.0",
       "source": "./",
       "author": {
         "name": "NoBrainer Tech"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "nobrainer-tech-flow",
   "description": "From task to done. nobrainer-tech-flow is one workflow of 18 modules for AI coding agents: it scopes the task, delegates ready work, checks the result and hands over the evidence, including what was not checked.",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "author": {
     "name": "NoBrainer Tech"
   },

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "nobrainer-tech-flow",
   "description": "From task to done. nobrainer-tech-flow is one workflow of 18 modules for AI coding agents: it scopes the task, delegates ready work, checks the result and hands over the evidence, including what was not checked.",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "author": {
     "name": "NoBrainer Tech",
     "url": "https://nobrainer.tech"

package/AGENTS.md

@@ -7,7 +7,7 @@ Respect host hierarchy; user instructions override skill guidelines. Apply [deli
 <!-- NOBRAINER-WORKFLOW:START -->
 ## nobrainer-tech-flow
 
-- Use [nobrainer-tech-flow](https://github.com/nobrainer-tech/nobrainer-tech-flow) through the `nobrainer-tech-flow` module, by the exact name the client lists (in Codex `$nobrainer-tech-flow:nobrainer-tech-flow` when it lists modules under the plugin name). Preserve the selected MAIN model and effort. Inspect native worker models and capacity, then delegate every independent ready unit with exact scope and proof; MAIN integrates. Use `nobrainer-auto-fine-tune` when measured route calibration would help.
+- Use [nobrainer-tech-flow](https://github.com/nobrainer-tech/nobrainer-tech-flow) through the `nobrainer-tech-flow` module, by the exact name the client lists (in Codex `$nobrainer-tech-flow:nobrainer-tech-flow` when it lists modules under the plugin name). Preserve the selected MAIN model and effort. Work in one MAIN loop; delegate only qualifying units with exact scope and proof; MAIN integrates. Use `nobrainer-auto-fine-tune` when measured route calibration would help.
 - Start substantial work from an observable short-term goal grounded in the owner's direction; inspect project layers and the relevant wiki. Check once per active day for a newer stable release. Keep session checkpoints and verify takeover before authorized archival. Load only relevant specialist skills and verify the delivery layer.
 - Product name: nobrainer-tech-flow; repository and skill ID: `nobrainer-tech-flow`. No ritual preamble. X: `#NoBrainerTechFlow`.
 <!-- NOBRAINER-WORKFLOW:END -->
@@ -59,8 +59,8 @@ For non-trivial work:
 `DRIFT_CHECK -> BUDDY -> SCOPE -> AUTOPILOT -> VERIFY -> RECEIVE_AUDIT -> LEARN`
 
 Before planning, inspect checkout, nearest instructions, dirty state, callers, tests, runtime
-and durable decisions. Delegate every independent ready unit promptly within
-native capacity and quota; MAIN coordinates, integrates, verifies and refills slots.
+and durable decisions. Delegate only units that gain from parallel work, isolated
+context, independent review or specialization; MAIN coordinates, integrates and verifies.
 
 ### Minimum sufficient change
 
@@ -103,9 +103,9 @@ Update at meaningful transitions, blockers and closeout, not before and
 after every command. The canonical plan or tracker owns TODO state; summaries,
 exit codes and worker reports cannot advance it.
 
-Use a detailed execution ledger only when work is multi-session, dependency-rich,
-consequential, explicitly resumable after context loss or requested by the owner. It
-must record exact identity, dependencies, write ownership, evidence, checkpoint,
+Use a detailed execution ledger only for multi-session, dependency-rich, consequential
+or resumable work, on owner request, or while owner requests keep arriving
+mid-run. It records identity, dependencies, write ownership, evidence, checkpoint,
 retry/stop conditions and rollback; ordinary single-session work uses a short checklist.
 
 ## Routing without ceremony
@@ -128,7 +128,7 @@ Load a specialist only when its boundary is active:
 - Autoimprove owns frozen baseline/candidate/holdout experiments.
 - Writing owns material user-facing prose; tiny clear answers stay direct.
 
-MAIN coordinates, integrates and verifies scoped worker edits. Use subagents. Visible conversations require explicit request or authorized MAIN restart; workers cannot spawn successors.
+MAIN coordinates, integrates and verifies scoped worker edits. Visible conversations require explicit request or authorized MAIN restart; workers cannot spawn successors.
 On Flow entry, date the title from verified creation time, preserve it on resume and assess context. Health benefit can qualify restart without economic payback; verify takeover by ID and never resume a retired writer. See Sessions for ` | started DD-MM` formatting and timezone.
 
 ## Problems and research
@@ -149,7 +149,7 @@ runtime, deployed runtime, production behavior, external delivery and user
 usefulness distinct. Partial output, timeout, stale state, dead session, failed
 test or missing required access is not success.
 
-When the owner changes a decision, supersede the old requirement and invalidate
+When the owner changes a decision, supersede the old requirement at once and invalidate
 only dependent work and evidence. A verified review failure returns to Build;
 rerun affected proof and review. Stop blind retries after the same failure and
 route causal uncertainty to RCA.

package/CLAUDE.md

@@ -7,7 +7,7 @@ Respect host hierarchy; user instructions override skill guidelines. Apply [deli
 <!-- NOBRAINER-WORKFLOW:START -->
 ## nobrainer-tech-flow
 
-- Use [nobrainer-tech-flow](https://github.com/nobrainer-tech/nobrainer-tech-flow) through the `nobrainer-tech-flow` module, by the exact name the client lists (in Codex `$nobrainer-tech-flow:nobrainer-tech-flow` when it lists modules under the plugin name). Preserve the selected MAIN model and effort. Inspect native worker models and capacity, then delegate every independent ready unit with exact scope and proof; MAIN integrates. Use `nobrainer-auto-fine-tune` when measured route calibration would help.
+- Use [nobrainer-tech-flow](https://github.com/nobrainer-tech/nobrainer-tech-flow) through the `nobrainer-tech-flow` module, by the exact name the client lists (in Codex `$nobrainer-tech-flow:nobrainer-tech-flow` when it lists modules under the plugin name). Preserve the selected MAIN model and effort. Work in one MAIN loop; delegate only qualifying units with exact scope and proof; MAIN integrates. Use `nobrainer-auto-fine-tune` when measured route calibration would help.
 - Start substantial work from an observable short-term goal grounded in the owner's direction; inspect project layers and the relevant wiki. Check once per active day for a newer stable release. Keep session checkpoints and verify takeover before authorized archival. Load only relevant specialist skills and verify the delivery layer.
 - Product name: nobrainer-tech-flow; repository and skill ID: `nobrainer-tech-flow`. No ritual preamble. X: `#NoBrainerTechFlow`.
 <!-- NOBRAINER-WORKFLOW:END -->
@@ -59,8 +59,8 @@ For non-trivial work:
 `DRIFT_CHECK -> BUDDY -> SCOPE -> AUTOPILOT -> VERIFY -> RECEIVE_AUDIT -> LEARN`
 
 Before planning, inspect checkout, nearest instructions, dirty state, callers, tests, runtime
-and durable decisions. Delegate every independent ready unit promptly within
-native capacity and quota; MAIN coordinates, integrates, verifies and refills slots.
+and durable decisions. Delegate only units that gain from parallel work, isolated
+context, independent review or specialization; MAIN coordinates, integrates and verifies.
 
 ### Minimum sufficient change
 
@@ -103,9 +103,9 @@ Update at meaningful transitions, blockers and closeout, not before and
 after every command. The canonical plan or tracker owns TODO state; summaries,
 exit codes and worker reports cannot advance it.
 
-Use a detailed execution ledger only when work is multi-session, dependency-rich,
-consequential, explicitly resumable after context loss or requested by the owner. It
-must record exact identity, dependencies, write ownership, evidence, checkpoint,
+Use a detailed execution ledger only for multi-session, dependency-rich, consequential
+or resumable work, on owner request, or while owner requests keep arriving
+mid-run. It records identity, dependencies, write ownership, evidence, checkpoint,
 retry/stop conditions and rollback; ordinary single-session work uses a short checklist.
 
 ## Routing without ceremony
@@ -128,7 +128,7 @@ Load a specialist only when its boundary is active:
 - Autoimprove owns frozen baseline/candidate/holdout experiments.
 - Writing owns material user-facing prose; tiny clear answers stay direct.
 
-MAIN coordinates, integrates and verifies scoped worker edits. Use subagents. Visible conversations require explicit request or authorized MAIN restart; workers cannot spawn successors.
+MAIN coordinates, integrates and verifies scoped worker edits. Visible conversations require explicit request or authorized MAIN restart; workers cannot spawn successors.
 On Flow entry, date the title from verified creation time, preserve it on resume and assess context. Health benefit can qualify restart without economic payback; verify takeover by ID and never resume a retired writer. See Sessions for ` | started DD-MM` formatting and timezone.
 
 ## Problems and research
@@ -149,7 +149,7 @@ runtime, deployed runtime, production behavior, external delivery and user
 usefulness distinct. Partial output, timeout, stale state, dead session, failed
 test or missing required access is not success.
 
-When the owner changes a decision, supersede the old requirement and invalidate
+When the owner changes a decision, supersede the old requirement at once and invalidate
 only dependent work and evidence. A verified review failure returns to Build;
 rerun affected proof and review. Stop blind retries after the same failure and
 route causal uncertainty to RCA.

package/README.md

@@ -59,9 +59,11 @@
   guards ask before `git push --force`, `git reset --hard`, a recursive delete
   outside temporary folders, a production deploy or a publish. A turn that
   changed files and ends without a proof line or an explicit `UNVERIFIED` is
-  sent back once. Opt-in, with preview and undo.
-- **Parallel work, checked in one place.** Independent ready parts go to native
-  workers; the main session checks each one.
+  sent back once. After compaction, resume or clear, the agent is pointed back
+  to the active goal file. Opt-in, with preview and undo.
+- **One main loop, workers only where they pay.** The main session does the work
+  with skills and hands a part to a native worker only for parallel work, context
+  isolation, independent review or specialization, then checks each result.
 
 Free, MIT. The Git install previews every change and has undo. Your coding client's usage costs still apply.
 
@@ -103,13 +105,28 @@ The mode is informed by ASD-STE100; it does not claim full standard compliance.
 
 ## Install and use the plugin
 
-Claude Code and Codex add nobrainer-tech-flow as a plugin straight from this
-repository. Any coding agent can use the Git install, which previews every
-change and has undo. Both are under [Install safely](#install-safely). The
-[npm command](docs/INSTALL.md#npm-command) is coming soon: the package is not
-yet published on npm. The [portable plugin ZIP](docs/CHAT_PLUGINS.md) brings the
-same 18 modules to supported ChatGPT/Codex and Claude surfaces. Public directory
-approval remains a separate step.
+Pick the channel that fits your client. The first five install the same 18 modules;
+the MCP server needs no install:
+
+- **Claude Code plugin:** `claude plugin marketplace add nobrainer-tech/nobrainer-tech-flow`,
+  then `claude plugin install nobrainer-tech-flow@nobrainer-tech`.
+- **Codex plugin:** `codex plugin marketplace add nobrainer-tech/nobrainer-tech-flow`,
+  then `codex plugin add nobrainer-tech-flow@nobrainer-tech`.
+- **npm:** [`npx nobrainer-tech-flow --client codex`](https://www.npmjs.com/package/nobrainer-tech-flow)
+  previews the setup for Codex, Claude Code (`claude`), OpenCode or GitHub Copilot;
+  add `--apply` to install.
+- **Git, for any coding agent:** a setup prompt or `scripts/install.sh`, with a
+  preview of every change and undo.
+- **Chat apps:** the [portable plugin ZIP](docs/CHAT_PLUGINS.md) for supported
+  ChatGPT/Codex and Claude surfaces.
+- **MCP server, no install:** add the free remote server `https://mcp.nobrainer.tech/mcp`
+  (no sign-in, stateless) in claude.ai, ChatGPT or any MCP client. Its six read-only
+  tools give the agent a task contract, an evidence check, a done gate and a model
+  advisor; it does not install the 18 modules. Per-client steps and what is verified:
+  [MCP server README](mcp/README.md#install).
+
+Details for each are under [Install safely](#install-safely). Listing in the
+public Claude and OpenAI plugin directories is a separate review step.
 
 ## How it works
 
@@ -143,7 +160,7 @@ next unblock action.
 A quick answer stays a quick answer. The model-neutral workflow uses one plan,
 bounded corrective attempts and a Markdown checkpoint for longer work. Native
 goals, telemetry and client-specific tools are optional. Available native workers
-handle independent ready units; unavailable workers leave safe work in MAIN.
+take a unit only when it pays; unavailable workers leave the work in MAIN.
 
 **One model is enough.** Optional Jev (remote) and Laya (local) profiles add
 typed suggestions for bounded classification, ranking and evaluation. Setup
@@ -187,11 +204,11 @@ flowchart TD
     P --> G
     J -. independent authorized work remains .-> P
     F -. optional .-> L[Markdown goal for resume]
-    G -. every independent ready unit within capacity and quota .-> M[Bounded native subagents; owner-approved model and effort]
+    G -. only units that gain from parallel work, isolated context, review or specialization .-> M[Bounded native subagents; owner-approved model and effort]
     G -. configured shadow only .-> Q[Jev remote or Laya local: advisory typed decisions]
     Q -. unavailable or invalid: core fallback .-> G
     M -->|Plain technical English reports| H
-    H -. audited unit; refill ready native slots .-> M
+    H -. audited unit; dispatch the next qualifying unit .-> M
     F -. first project use .-> R[Inspect layers and relevant wiki]
     R --> G
     M -. recurring workload .-> T[Auto Fine Tune: measured worker route]
@@ -260,12 +277,24 @@ sh ~/.nobrainer-tech-flow/scripts/install.sh --client claude --apply   # link th
 `--client` is `claude`, `codex`, `opencode` or `copilot`. Cursor, Gemini CLI, Pi and Kimi Code
 use a plugin or extension instead: see their sections in
 [docs/INSTALL.md](docs/INSTALL.md#client-channels). The script links all eighteen skills and adds
-one instruction block, shows the exact text first, refuses anything that is not its own, grants
-no authorization and undoes itself with `--undo --apply`. To update, run `git pull` in
+one instruction block, shows the exact text first, refuses anything that is not its own and
+undoes itself with `--undo --apply`. The block lets Flow update itself to verified stable
+releases once a day; `install_personalization.py --no-auto-update` turns that into a
+notification only. No other authorization is granted. To update, run `git pull` in
 `~/.nobrainer-tech-flow` and the same two commands again, or paste the prompt again. With Python,
 `python3 scripts/install.py` takes the same flags.
 
-**npm:** coming soon. The package is not published yet.
+**npm** (Node 18+ and Python 3.11+; [package page](https://www.npmjs.com/package/nobrainer-tech-flow)):
+
+```sh
+npx nobrainer-tech-flow@2.7.0 --client codex            # preview: changes nothing
+npx nobrainer-tech-flow@2.7.0 --client codex --apply    # install
+npx nobrainer-tech-flow@2.7.0 --client codex --undo --apply
+```
+
+`--client` is `codex`, `claude`, `opencode` or `copilot`. The files are copied to a
+stable folder in your home directory, so nothing points into npx's cache; see the
+[npm command](docs/INSTALL.md#npm-command).
 
 **Next step:** in a fresh session, give it one small task with a checkable result:
 
@@ -303,7 +332,8 @@ next command.
 `install.py`, like `scripts/install.sh` without Python, links all eighteen skills
 and adds one managed instruction block for `claude`, `codex`, `opencode` or
 `copilot`. The preview shows the exact text it would write, a target that is not
-its own link is refused, no authorization is ever granted, and
+its own link is refused, the only standing authorization is the default daily Flow
+update (opt out with `install_personalization.py --no-auto-update`), and
 `python3 scripts/install.py --client codex --undo --apply` reverses it. It needs
 symbolic links (Windows: Developer Mode). For a subset, a copy install, the shared
 `agents` folder or another client, use the individual scripts in
@@ -363,7 +393,7 @@ Use nobrainer-tech-flow through the canonical skill
 outcome. A small reversible edit without a public contract, routing, workflow or
 portfolio change can use its quick path; other changes use the full path and its
 coherence gate.
-In Codex, type the exact name it lists for the module: `$nobrainer-tech-flow:nobrainer-tech-flow` after the installer or a plugin install (and after the npm package, once it is published), and `$nobrainer-tech-flow` for a copy made with `install_skills.py --mode copy`. Say
+In Codex, type the exact name it lists for the module: `$nobrainer-tech-flow:nobrainer-tech-flow` after the installer, a plugin install or the npm package, and `$nobrainer-tech-flow` for a copy made with `install_skills.py --mode copy`. Say
 `Use NBFlow`, `Use NBF` or `Use nobrainer-tech-flow` in natural language;
 older trigger phrases are migration context only and
 depend on a client's implicit description matching.
@@ -378,11 +408,13 @@ DRIFT_CHECK -> BUDDY -> SCOPE -> AUTOPILOT -> VERIFY -> RECEIVE_AUDIT -> LEARN
 - One canonical plan owns TODO state; the owner sees only a compact Progress
   checklist and one next action.
 - A durable ledger adds exact identity, dependencies, checkpoints, retries and
-  rollback only for cross-session, dependency-rich or consequential work.
+  rollback only for cross-session, dependency-rich or consequential work, or
+  when the owner keeps adding requests in one long conversation.
 - `AUTOPILOT` continues through routine approved work without repeated check-ins.
-- Delegate every independent ready unit to native workers within verified capacity
-  and quota under the [delegation contract](skills/nobrainer-tech-flow/references/delivery.md#coordinated-team-execution).
-  MAIN coordinates, integrates, verifies and refills freed slots. Team supplies
+- Work in one MAIN loop with skills. Delegate a unit to a native worker only for parallel
+  work, context isolation, independent review or specialization, under the
+  [delegation contract](skills/nobrainer-tech-flow/references/delivery.md#coordinated-team-execution).
+  MAIN coordinates, integrates and verifies. Team supplies
   capabilities; Dispatcher schedules real queues. Visible sessions require an
   explicit owner request or authorized MAIN restart.
 - Failed review returns to `nobrainer-build`; changed code invalidates old proof.
@@ -402,7 +434,7 @@ configured limits. Missing optional telemetry lowers the health claim and still
 allows bounded safe work. An explicitly required hard budget must be enforceable.
 `RUNTIME_RELEASE` concerns actual task-owned workers; a completed result does not
 prove they stopped. `GOAL_FILE` is optional Markdown recovery state. A native goal
-is used only when available and authorized; the file alone suffices.
+mirrors the DoD where the host offers one; the file alone suffices.
 
 Autopilot works with one visible MAIN coordinator and bounded native workers.
 Ordinary native assignments use the compact packet in the delegation contract,
@@ -531,15 +563,26 @@ prove production. See [Compatibility](docs/COMPATIBILITY.md) for current proof
 and [Testing](docs/TESTING.md) for acceptance evidence.
 
 
-**What's new in 2.5.0:** `nobrainer-context` (`nb-context`) keeps one set of project
-instructions for every coding agent: it shows what Codex, Claude Code, Gemini CLI,
-Cursor, Copilot and OpenCode load, and proposes one source of truth with pointers.
-See [RELEASE-NOTES.md](RELEASE-NOTES.md).
-
-Current source version: **2.5.0**. Check the
+**What's new in 2.7.0:** before substantial work the agent shows what done means and sets
+it as the host's native goal where one exists, and the TODO stays visible. Flow delegates only where it pays: one MAIN loop with skills does
+the work, and a unit goes to a native worker only for parallel work, context isolation,
+independent review or specialization. When the owner keeps adding requests in one long conversation,
+Flow records each one in the goal file as it arrives instead of leaving it only in the
+transcript, where compaction can drop it; a changed decision updates the goal file at once
+and, as the project's learning policy allows, the instruction-file lines that still state
+the old rule. The optional Claude Code guards point the agent back to the active goal file
+after compaction, resume or clear, and `nobrainer-team` fills a capability gap with a
+task-local specialist brief instead of third-party skills. A security review needs a second
+independent pass before it can report a clean result. After fixing a defect that was public
+or reachable before the fix, the agent checks for exploitation during that window or reports
+it as untested. When docs and code disagree on a coding convention, `nobrainer-build`
+follows the code unless an owner rule or a deliberate migration says otherwise, and reports
+each disagreement, with the edit that fixes a stale file when the code wins. See [RELEASE-NOTES.md](RELEASE-NOTES.md).
+
+Current source version: **2.7.0**. Check the
 [latest published GitHub release](https://github.com/nobrainer-tech/nobrainer-tech-flow/releases/latest)
-for distribution and the [2.5.0](docs/releases/v2.5.0.md) and
-[2.4.0 verification records](docs/releases/v2.4.0.md) for
+for distribution and the [2.7.0](docs/releases/v2.7.0.md), [2.6.0](docs/releases/v2.6.0.md) and
+[2.5.0 verification records](docs/releases/v2.5.0.md) for
 the current scope, reproducible checks and client-runtime limits. The unchanged command runner keeps its
 [v1.7.0 verification scope](docs/releases/v1.7.0.md). Source publication does not
 imply client marketplace discovery or improved model reasoning. The earlier
@@ -600,11 +643,10 @@ docs/                 compatibility, curation, eval and release evidence
 assets/               brand and workflow diagrams
 ```
 
-Client-specific forks of a skill are prohibited. External skills discovered by
-Team are untrusted input: inspect the exact source/ref, instructions, scripts,
-permissions, network/credential behavior, trigger overlap and rollback. Prefer
-temporary project-scoped use; persistent or global installation is an owner
-gate.
+Client-specific forks of a skill are prohibited. Team fills a capability gap
+with a task-local specialist brief for a native worker; it never searches for,
+installs or runs third-party skills. Installing anything is the owner's own
+separate decision.
 
 </details>
 

package/adapters/bootstrap.md

@@ -10,8 +10,8 @@ selection; install chosen items plus required dependencies. Preserve MAIN; mark
 unknown runtime facts `UNKNOWN`. Back up, read back and keep rollback. Load skills
 on demand; never execute linked installers.
 
-Keep updates brief, outcome-first and non-repetitive. Delegate every independent ready unit to native
-workers within verified capacity and quota; MAIN integrates, verifies and refills freed slots.
+Keep updates brief, outcome-first and non-repetitive. Work in one MAIN loop; delegate only for
+parallel work, context isolation, independent review or specialization; MAIN integrates and verifies.
 
 `PROBLEM_GATE`: start from the literal failure, local evidence and smallest
 reproducer. Query useful wiki decisions. Use current internet research when the

package/assets/nobrainer-workflow.svg

@@ -1,6 +1,6 @@
 <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1600 900" role="img" aria-labelledby="title desc">
   <title id="title">nobrainer-tech-flow delivery workflow</title>
-  <desc id="desc">Check the nobrainer-tech-flow release on first active use each day. Clear tasks use the QUICK PATH. Larger work derives a short-term goal from the owner's direction, inspects project layers and wiki, executes the authorized scope and verifies the result. Model policy preserves the selected MAIN model and effort. Native workers handle every useful independent ready unit within verified capacity and authorized usage. MAIN coordinates, integrates and verifies each result, then refills ready slots. Auto Fine Tune calibrates routes when useful; it is not a dispatch prerequisite. A Markdown GOAL_FILE supports recovery. A fresh session takes over before authorized archival of the old one. RUNTIME_RELEASE readback verifies owned workers. The full goal remains open until acceptance and delivery proof pass.</desc>
+  <desc id="desc">Check the nobrainer-tech-flow release on first active use each day. Clear tasks use the QUICK PATH. Larger work derives a short-term goal from the owner's direction, inspects project layers and wiki, executes the authorized scope and verifies the result. Model policy preserves the selected MAIN model and effort. One MAIN loop does the work with skills; native workers take only units that gain from parallel work, context isolation, independent review or specialization. MAIN coordinates, integrates and verifies each result. Auto Fine Tune calibrates routes when useful; it is not a dispatch prerequisite. A Markdown GOAL_FILE supports recovery. A fresh session takes over before authorized archival of the old one. RUNTIME_RELEASE readback verifies owned workers. The full goal remains open until acceptance and delivery proof pass.</desc>
   <defs>
     <linearGradient id="background" x1="0" y1="0" x2="1" y2="1">
       <stop offset="0" stop-color="#0F1319"/>
@@ -84,7 +84,7 @@
     <rect x="1186" y="304" width="90" height="34" rx="0" class="chip"/>
     <text x="1211" y="326" class="chip-text">SDD</text>
     <rect x="1288" y="304" width="198" height="34" rx="0" class="chip"/>
-    <text x="1300" y="326" class="chip-text-small">READY NATIVE WORKERS</text>
+    <text x="1300" y="326" class="chip-text-small">QUALIFYING WORKERS</text>
   </g>
 
   <g filter="url(#soft-shadow)">

package/docs/CHAT_PLUGINS.md

@@ -10,7 +10,9 @@ In Claude, open Customize > Plugins, choose Add > Upload plugin and select the Z
 
 In ChatGPT Work or Codex, install from a supported local/repository marketplace or from the public Plugins directory once the listing is approved. The repository marketplace identifies this source package. A downloadable ZIP is a release artifact, not proof of directory approval. OpenAI's public directory requires a verified developer identity, package scans and platform review before publication.
 
-Once the npm package is published (it is not yet), it can also serve as a plugin source. A marketplace can then reference source type npm, package nobrainer-tech-flow and an exact published version. The client downloads the package without running npm lifecycle scripts.
+The npm package `nobrainer-tech-flow` is published, so it can also serve as a plugin source. A marketplace can reference source type npm, package nobrainer-tech-flow and an exact published version. The client downloads the package without running npm lifecycle scripts.
+
+To use Flow without installing anything, add the free remote MCP server `https://mcp.nobrainer.tech/mcp` in claude.ai (custom connector) or ChatGPT (custom MCP server), or in any MCP client. It needs no sign-in, is stateless and offers six read-only tools: `start_flow_task`, `get_flow_step`, `check_flow_evidence`, `check_flow_done`, `draft_flow_handoff` and `recommend_flow_model`. It gives the agent a task contract, an evidence check and a done gate plus a model advisor; it does not install the 18 modules. Per-client steps and which clients are verified: [MCP server README](../mcp/README.md#install).
 
 ## Check the installation
 
@@ -26,4 +28,4 @@ If browser, shell, workers or local files are unavailable, the workflow must rep
 - Claude supported surfaces: https://claude.com/docs/plugins/platform-support
 - Claude publication: https://claude.com/docs/directory/publish
 
-The inFakt integration uses an MCP server and OAuth to access an existing account: https://www.infakt.pl/integracje-z-infakt-za-pomoca-api/#asystenci-ai . nobrainer-tech-flow currently needs skills and the client's existing tools, so this distribution does not add an MCP backend or require account access.
+The inFakt integration uses an MCP server and OAuth to access an existing account: https://www.infakt.pl/integracje-z-infakt-za-pomoca-api/#asystenci-ai . The plugin ZIP and the npm package need skills and the client's existing tools, so they do not add an MCP backend or require account access. The MCP server above is a separate, optional path.

package/docs/INSTALL.md

@@ -14,17 +14,18 @@ upgraded merely because the new source is installed nearby.
 Node 18+ and Python 3.11+ are prerequisites. Preview the setup first:
 
 ```sh
-npx nobrainer-tech-flow@2.5.0 --client codex
-npx nobrainer-tech-flow@2.5.0 --client codex --apply
-npx nobrainer-tech-flow@2.5.0 --client codex --undo --apply
+npx nobrainer-tech-flow@2.7.0 --client codex
+npx nobrainer-tech-flow@2.7.0 --client codex --apply
+npx nobrainer-tech-flow@2.7.0 --client codex --undo --apply
 ```
 
 Use claude for Claude Code, opencode or copilot for those clients. Add --home PATH
-for an isolated profile. These commands become available once this version is
-published on npm; a source candidate is not registry availability.
+for an isolated profile. The package is published on
+[npm](https://www.npmjs.com/package/nobrainer-tech-flow); each release lists its
+version there.
 
 Application copies the release files into the chosen home directory's
-.nobrainer-tech-flow-npm/2.5.0 and verifies the copy. That folder sits beside
+.nobrainer-tech-flow-npm/2.7.0 and verifies the copy. That folder sits beside
 ~/.nobrainer-tech-flow, where the Git installation suggests a clone, so cleaning
 the clone cannot delete the files the skill links point to. Releases before 2.3.2
 kept their copy in .nobrainer-tech-flow/npm; undo such a setup with the command of
@@ -106,14 +107,18 @@ flags). The two share the setup record, so either one undoes what the other did.
 - Running `--apply` again when nothing needs to change prints `UP TO DATE` and no
   restart hint. `INSTALLED` and the restart hint appear only when a link or the
   instruction file was written.
-- It never grants a standing authorization. When the block in the instruction file
-  is the text of an earlier version, both scripts replace it with this version's
-  text, keep everything outside the two markers byte for byte and save the file as
-  it was as a `.bak` copy first. `install.py` also keeps earlier auto-update,
-  session-restart and wiki-root settings in the block as `--keep-options` keeps
-  them; `install.sh` leaves a block that carries one of those options, or whose
-  markers do not stand on lines of their own, exactly as it is and says so. Change
-  options with `install_personalization.py`.
+- The only standing authorization it writes is the default one-line daily update of
+  Flow itself to a verified stable release; session rotation still needs its own
+  opt-in. When the block in the instruction file is the text of an earlier version,
+  both scripts replace it with this version's text, keep everything outside the two
+  markers byte for byte and save the file as it was as a `.bak` copy first. Both keep
+  the update choice: an existing block updates itself again only when it holds the
+  update line as its own line, and a notify-only, edited or unknown update line is
+  replaced by the one-line notify-only rule. `install.py` also keeps session-restart
+  and wiki-root settings as `--keep-options` keeps them; `install.sh` leaves a block
+  that carries one of those options or a preference, or whose markers do not stand on
+  lines of their own, exactly as it is and says so. Change options with
+  `install_personalization.py`.
 - `--undo` (a preview until `--apply` is added) removes exactly the links the setup
   created and puts the managed block back as it was before the first setup:
   removed, or the block that was there before. The rest of the instruction file
@@ -276,17 +281,24 @@ the instructions. A guided setup recorded earlier for the Codex file asks for an
 undo before it writes the Claude file. `agents` needs an explicit verified
 `--path`. For a resolved global wiki,
 pass `--wiki-root PATH` pointing at a directory containing `WIKI.md`; this
-records the actual location in the personalization block. `--auto-update`
-opts into safe checked `nobrainer-tech-flow`-only upgrades where standing owner
-authorization exists, and `--auto-session-restart` opts into evidence-gated
-session rotation. A later run without those flags writes the default block
-again; add `--keep-options` to keep the update, session-restart and wiki-root
-settings already in the block (the guided setup always does). A grant counts
+records the actual location in the personalization block. Since 2.6.0 the
+block keeps Flow updated by default with one line: once a day on first use,
+update to the latest verified stable release from the canonical source, with a
+backup, changing nothing else. `--no-auto-update` writes a one-line notify-only
+rule instead; `--auto-update` is still accepted and means the default. With
+`--keep-options` an opt-out already in the block stays, and the longer update
+lines written before 2.6.0 become the matching short line (an old grant stays a
+grant, the old notify-only default stays notify-only). An update line that is
+neither recognized grant becomes the notify-only line: updates are never inferred. `--auto-session-restart`
+opts into evidence-gated session rotation. A later run without those flags
+writes the default block again; add `--keep-options` to keep the update choice,
+session-restart and wiki-root settings already in the block (the guided setup
+always does). A grant counts
 only as the exact line the installer writes for it, so wording quoted in a
 `--preferences` value never becomes one, and a preference or wiki path must be
 one printable line. A grant line that was edited is not kept, and the run says so
-and names the flag that grants it again. Without the
-update opt-in, the first active `nobrainer-tech-flow` use each day checks and
+and names the flag that grants it again. With the
+notify-only line, the first active `nobrainer-tech-flow` use each day checks and
 notifies. Use a scheduler separately if updates must be checked on inactive days.
 
 A newer release must be obtained at a verified immutable ref before any
@@ -426,7 +438,7 @@ After restart, verify:
 
 #### Optional guards
 
-Two opt-in hooks in your Claude Code user `settings.json`, never in the plugin:
+Opt-in hooks in your Claude Code user `settings.json`, never in the plugin:
 
 - before a shell command, Claude Code asks you first (it never denies) for
   `rm -r` (also `/bin/rm`) outside the temporary folders (`$TMPDIR`, `/tmp`,
@@ -442,7 +454,14 @@ Two opt-in hooks in your Claude Code user `settings.json`, never in the plugin:
 - when a turn that edited files or ran commands ends without a line starting
   with `Proof:` or `Checked:` and without `UNVERIFIED`, the stop is blocked once
   so the agent adds one. A read-only turn, a second stop and an unreadable
-  transcript are let through.
+  transcript are let through;
+- after compaction, resume or clear, the agent is told to re-read up to three
+  active Flow goal files (a `GOAL_ID:` line and a `STATUS` other than `COMPLETE`,
+  in the project root, `tasks/`, `docs/` or `.nobrainer/`). It prints only each
+  path and a known `STATUS` word, never other goal-file text; it follows no
+  symlink, skips names with characters other than letters, digits, `.`, `-` and
+  `_`, stops after 5,000 folder entries or 200 files, and prints nothing on any
+  error.
 
 This is a seatbelt, not a security boundary. It reads the command text, so
 `sh -c`, a variable or an alias gets past it, and a risky phrase inside a quoted
@@ -459,7 +478,7 @@ python3 scripts/install.py --client claude --guards --undo --apply
 `~/.claude/settings.json` when the variable is unset. The preview lists only the
 hooks it would add or remove, never other settings; other hooks are kept, each
 change writes a new backup, readable only by you, without overwriting an older one, a second `--apply`
-changes nothing, and an invalid file is refused
+changes nothing, an install from an earlier version is shown as an update, and an invalid file is refused
 (exit 3) without being touched. The hooks run `flow_guard.py` through the
 skill link that `--client claude` created, so install the skills first. A
 plugin-only install, other clients, `scripts/install.sh` and Windows are not
@@ -472,7 +491,9 @@ PreToolUse reads `tool_name`, `tool_input.command` and `cwd` and answers
 `hookSpecificOutput.permissionDecision: "ask"` with `permissionDecisionReason`;
 Stop and SubagentStop read `stop_hook_active`, `last_assistant_message`,
 `transcript_path` and `agent_transcript_path` and answer
-`{"decision": "block", "reason": ...}`.
+`{"decision": "block", "reason": ...}`; SessionStart (matcher
+`compact|resume|clear`) reads `cwd` and answers
+`hookSpecificOutput.additionalContext`.
 
 ### Codex
 
@@ -585,10 +606,10 @@ actually exposes and passes that integration.
 
 The eighteen curated skills are the stable base. When a concrete work unit still
 has a capability gap, `nobrainer-team` first inventories installed/project
-capabilities, then may evaluate one external skill temporarily. Source/ref,
-scripts, permissions, credentials, network behavior, trigger overlap and
-rollback must be inspected before use. Persistent or global installation is an
-owner gate.
+capabilities, then writes a task-local specialist brief (role, method from
+project docs or verified primary sources, allowed actions, write scope and
+acceptance) for a native worker. Team never searches for, installs or runs
+third-party skills; installing anything is the owner's own separate decision.
 
 ## Readback and acceptance
 

package/docs/SKILL_CURATION.md

@@ -71,13 +71,13 @@ Team resolves a capability gap in this order:
 2. already installed and inspected specialist;
 3. maintained project/API/CLI/native capability;
 4. bounded current research;
-5. temporary external skill discovered for the exact missing capability.
+5. a task-local specialist brief for a native worker, written from project docs
+   or verified primary sources.
 
-External instructions are untrusted. Search rank does not authorize install,
-scripts, credentials, network access or writes. Review immutable source/ref,
-license, permissions, trigger overlap, persistence and rollback. Persistent or
-global installation requires an owner gate and evidence that repeated use earns
-the added trigger/context surface.
+Team never searches for, installs or runs third-party skills. Third-party text
+met during research is data, not instructions. A new permanent skill needs
+evidence that repeated use earns the added trigger/context surface and goes
+through the normal curation review.
 
 ## Retirement test