@passioncode-ai/fabric-agent-adapter 0.78.0 → 0.79.1

package/CHANGELOG.md

@@ -1,5 +1,127 @@
 # Changelog
 
+## 0.79.1 (2026-11-12)
+
+0.79.0 was tagged and never published: its release run (43176165810) failed two jobs, so `release` and `publish` were
+skipped. 0.79.1 is 0.79.0 with these fixes, and is the release that ships it. Kit modules change: `fabric-peer-owner.mjs`,
+`fabric_supervisors` and `fabric-supervisors.mjs`, `fabric_board_session`, `fabric_board_slots` and their Node twins.
+
+### Fixed
+
+- **A checked connection to `localhost` reaches a listener on 127.0.0.1 under Node 18** (the `floors` job). Node 18
+  connects to the first address only, and `localhost` resolves to `::1` first on Linux, so `checkedSocket` (and every
+  loopback read made through it: `wellKnownOf`, the key set, the OpenRouter connector) found nothing where Python and
+  Node 20 and later try every address. It now passes `autoSelectFamily: true`. Reproduced on Node 22 with
+  `--no-network-family-autoselection`: the test fails without the change and passes with it.
+- **The Windows job runs what passes there** (the `windows` job). 0.79.0 ran the whole of
+  `test_fabric_session_dispatch.py` on Windows for the first time (FAA-236): the parsing, `gate-id` and damaged-folder
+  tests pass, and twelve `Hooks` tests fail (the dispatch record's holder and `/clear` across processes). The job runs
+  the whole file again: the twelve were ten tests of the POSIX `/clear` take-over, which `dispatch_holder` turns off on
+  Windows by design (now skipped there with the reason), one file read with the code page (now UTF-8), and one real
+  defect: when `os.fdopen` raised, the descriptor stayed open, Windows refused to remove the empty record, and the
+  run was told it was nested and never did its request. The descriptor is closed first (FAA-302).
+- **`foreign-user` no longer drops a lost call's record** (the 0.79.0 seam reading): 0.79.0's new board code
+  (FAA-252) reached two places that keep a lost call's state and read it as a refusal. The reply probe
+  (`_replied_before`, `repliedBefore`) and a lost enroll's asking record (`_replay`, `replay`) now stay, as for
+  `unreachable`, so a reply is never sent twice. Both twins, a test in each.
+- **A loopback origin with no port, or `:80`, is read on a checked connection** in both twins: Node's `new URL`
+  drops the default port and read `http://127.0.0.1:80` unchecked; Python read a portless origin unchecked.
+- `references/delegation.md` says what a restricted socket table does to a loopback key set and the way round.
+
+### Changed
+
+- 0.79.0's FAA-293 line is narrower than it read: the inode check closes the race between two copies starting at once.
+  A folder swapped under a copy already running is not caught yet (FAA-303).
+
+### Upgrading
+
+- `fabric_delegation` (and `fabric-delegation.mjs`) imports `fabric_peer_owner` since 0.79.0: update with
+  `fabric_kit.py install`, which brings it along, never a hand copy of the one file.
+
+## 0.79.0 (2026-11-12)
+
+The first release of the backlog sweep of 2026-11-12 (plan and inventory of the 134 open rows:
+`docs/evidence/specs/2026-11-12-backlog-waves-plan.md`). The contract pin stays `18f8d487`. Kit modules change:
+`fabric_lock`, `fabric_base`, `fabric_delegation`, `fabric_descriptor`, `fabric_supervisors`, `fabric_board_link`,
+`fabric_board_slots`, `fabric_board_session`, `fabric_openrouter`, the facade `fabric_service`, their Node twins, and
+`fabric-secrets.mjs`. The dashboard kit moves to 1.1.6.
+
+### Added
+
+- **creating and adapting: an organization's catalogue first** (the project board's request `2718ece8`). One neutral
+  line at step 0 of creating-fabric-agents and before scaffolding in adapting-projects-to-fabric: a private catalogue
+  of agent templates with an architect is asked first for the template, version, variant and known traps; the skill
+  runs after it. Scenario `ask-the-organization-catalogue-first` in both skills.
+
+### Changed
+
+- **working-with-fabric reads against Fabric v0.3.19.** The session-start preamble, the README and SKILL.md say both
+  cases: before Fabric 0.3.17 a dispatched run declines a request no session can take and the asker resends; from
+  0.3.17 the session's own Project is granted `board.respond` at `com.enroll` (CO-506) (FAA-221). The exit contract's
+  decline names the refusal's reason, takes over an `in_progress` request an earlier run left, and reads board ids
+  from the dispatch line first; the Observatory packet's board refs are the fallback (FAA-215, FAA-295).
+  `references/on-demand-session.md` and `board.md` name the Fabric releases as they are (FAA-246, FAA-216), and a
+  helper a run starts itself uses the runner's bypass flag with the task's limits set at launch (FAA-274).
+- **"When nobody answers"** runs only on a machine whose trust is `mine` (ADR-0176), and the asker cancels its own
+  request after adapting (FAA-220). One phrase for a never-held slot, and a gate question is moot once its request is
+  answered or taken (FAA-222, FAA-248).
+- **creating-fabric-agents: completion lines for an agent that answers people**, one per checklist item (a file and a
+  test, or `NOT_RUN`), the first reply measured from the person's message (FAA-180).
+- **One rule for a secret in a child's environment**: the agent's own process may hold its key from its supervisor or
+  a vault runner; a child it starts never gets it (FAA-281).
+- **Operator channel through the estate's gateway**: where the estate runs a messaging gateway the operator chose, the
+  channel sends through it; a polling token has one poller across machines (`poller-elsewhere`); the contract's
+  own-bot form (DEC-0034) is unchanged (FAA-282).
+- **README quick start picks a free port**; `where-agents-run.md` adds one computer with a personal and an
+  organization account and a member's virtual machine (DEC-0154) (FAA-283).
+- **The dashboard link gate is agent-side**, and a generated project pins a negative fixture in its own test (FAA-129).
+- **The shipped-file check follows npm** (`test/validate.py`): a `files` entry with a glob, one naming nothing, or no
+  `files` at all is a finding; README and LICENSE are read because npm ships them regardless; a line with no scheme
+  says so. Tests pin `__pycache__`, the wiring into `validate_repo`, and the kit's `older` and `modified` verdicts
+  without release tags (FAA-212).
+
+### Fixed
+
+- **The instance lock never holds a file that is no longer at its path** (FAA-293, a board finding of 2026-11-10).
+  After `flock` (Python) or the `O_EXLOCK` open (Node on macOS), and again after the pid is written, `acquire`
+  compares the locked inode with the file at the path; on a mismatch it re-opens up to
+  `InstanceLock.INODE_RETRIES` (3) times, then fails with an error naming the path. A data import that swapped the
+  data folder no longer lets two copies start.
+- **The dashboard kit's resize observers write in the next frame** (dashboard kit 1.1.6, a board finding of
+  2026-11-12): the nav's observer laid the bar out inside its callback and the chrome's wrote `--fd-chrome-h` and
+  `--fd-chrome-top` there, so WebKit raised "ResizeObserver loop completed with undelivered notifications" at 390 px.
+  Both schedule their work with `requestAnimationFrame` (cancelling the previous frame), the nav refits only when its
+  width changed, the chrome writes a property only when its value changed; a WebKit test pins that no callback writes.
+- **Another OS account's listener is never read as ours**: the delegation verifier reads a loopback key set only from
+  this account's listener (FAA-255); the OpenRouter connector stops at once on a loopback base URL another account
+  holds, without trying the fallback model (FAA-257); a board session maps a hub port another account holds to
+  `foreign-user`, never `unreachable` (FAA-252); Python's `well_known_of` and `job_well_known_of` tell down from
+  `foreign-user` as Node's `wellKnownOf` does, and an origin spelled `localhost`, another 127/8 address or `[::1]` is
+  read on a checked connection (FAA-259, FAA-257); a hub pid another account's process holds is "not verified",
+  never running (FAA-254).
+- **The reserved capability `project.work`** is refused by both kits in `surfaces.mcp.capabilities`, as an action's
+  tool and by the board responder (DEC-0140 PR-1) (FAA-244).
+- The provider entry's URI check uses the RFC 3986 class the descriptor check uses: a byte-order mark, a zero-width
+  space, a non-ASCII path and an IDN host are refused (FAA-127).
+- The dispatch record survives a hooks folder damaged by hand: `RecursionError` reads as unreadable, a `dispatch`
+  file is a folder that cannot be written, prune ages a record by its own `lstat` (FAA-208).
+- `test/validate.py` reads board rows cell by cell as the workspace aggregator does: code spans and escaped pipes
+  (FAA-214). The Node credential detector and the dashboard kit's button append values in place, linear like the
+  Python twin (FAA-245). The source check's linear-time tests measure a ratio, not the wall clock (FAA-209).
+- The board kit sends the operator to Fabric's Settings → Agent access (FAA-223); `vendor_vectors.mjs` names the
+  command that works, the contract's `tsx` at the pin (FAA-242).
+- Step 6's `fabric_task_create` example carries the required `origin` (FAA-154).
+- A dispatched Claude Code run that sees only `fabric_whoami` is named as Fabric's CO-563 (fixed in the Fabric release
+  after v0.3.19) and says so in its exit report instead of claiming the board was read (FAA-296).
+- `fabric_session.py --help` and the README list `gate-id`, and the Windows job runs the dispatch tests (FAA-236).
+- `provider-entry.md` and the provider writer's message name Fabric v0.3.16 for CO-479 (FAA-216).
+
+### Upgrading
+
+- A service that vendors the kit updates its copies with `fabric_kit.py install` (the changed modules are named
+  above); a dashboard that vendors the dashboard kit takes 1.1.6. `launchd_install` takes injected readers
+  (`fetch_well_known=`, `fetch_job_well_known=`) as Node's `launchdInstall` takes `fetchWellKnown`.
+
 ## 0.78.0 (2026-11-12)
 
 The contract pin stays `18f8d487`. Kit modules change: a new `fabric_tailnet` and `fabric-tailnet.mjs` (layer L0); `fabric_supervisors` and `fabric-supervisors.mjs`, and the facades

package/README.md

@@ -24,7 +24,9 @@ The skills are `adapting-projects-to-fabric`, `creating-fabric-agents`,
 a terminal that works in a project through Fabric. It finds Fabric (`hub.json`, its `pid`), has the machine's
 lifecycle broker start it when it is down, registers `fabric-mcp` once with no secret, calls `fabric_whoami`
 first, reads the project board (`com.status`, `com.list`, `com.read_ack` only what was read), answers what waits on its
-Project in the same turn with its state (the result later; a request a responder should take stays queued), and asks other
+Project in the same turn with its state (the result later; a request its Project's service should take stays queued; before Fabric 0.3.17 a run Fabric starts
+declines a request no session can take and the asker resends, and from 0.3.17 the session's own Project is granted
+`board.respond` at `com.enroll`, CO-506), and asks other
 Projects only through `com.submit`, asks who is working on what and claims its task before it starts
 (`fabric_work_list`, `fabric_work_claim`, Fabric v0.3.5 and later), links tasks to backlog rows instead of copying them, and
 releases at the end (`fabric_work_release`). `scripts/fabric_session.py status` prints where Fabric stands and one
@@ -40,7 +42,7 @@ uses Fabric (one line pointing at `fabric_whoami` in a folder with no sign of it
 is down it adds one line (skip `fabric_whoami`, start Fabric through the broker if the task needs it), and only in a
 project that uses Fabric; in a session Fabric started on a board request (`FABRIC_DISPATCH_WORKFLOW` set) it prints the
 exit contract instead, on the condition that the session's own prompt starts with the dispatch line naming the same
-three, and UserPromptSubmit, which sees that line, confirms the run or says it is none (FAA-201); Stop records each turn's facts (HEAD, files changed, lines added and removed, never content)
+three (a `/clear` while another session holds the dispatch is told it is nested, FAA-208), and UserPromptSubmit, which sees that line, confirms the run or says it is none (FAA-201); Stop records each turn's facts (HEAD, files changed, lines added and removed, never content)
 and the board's unread count, and, once the running Fabric takes them (unless `FABRIC_SESSION_NO_REPOSITORIES=1`), the other repositories the turn touched (it then
 reads the last 512 KB of the session transcript (message text and tool output included, which can hold a secret the session displayed; read in memory only), uses only tool names and path arguments, and sends host/owner/name, never a
 local path or text); UserPromptSubmit adds one line only when that count rose, and each reminder Fabric gave on a turn once (a turn `watch-mail` delivered prints there instead); SessionEnd releases what the
@@ -49,7 +51,8 @@ line naming the retro (FAA-206; Fabric's `retro-after-work`, since Fabric 0.3.16
 advertises `session-hooks/1`; Stop and SessionEnd always prune their own stale spool folders. All are silent in a session Fabric launched (except the retro line after a release of finished work and, in one started on a board request, the exit contract and the prompt hook's verdict on its dispatch line, but no unread line or reminder), never block the session, read no Fabric token (an `origin` URL's embedded credential is dropped in memory, never
 kept or sent) and always
 exit 0 once `python3` starts (on Windows, Claude Code runs hooks in Git Bash, or PowerShell without it, where `python3`
-must name Python 3.9 or later; FAA-183). `fabric_session.py watch-mail` waits for board mail under a background watcher, and `install-host-hooks
+must name Python 3.9 or later; FAA-183). `fabric_session.py watch-mail` waits for board mail under a background watcher, `gate-id <request>` prints the
+`commandId` of a request's gate question (the one a dispatched run uses), and `install-host-hooks
 --host codex|kimi|hermes|opencode|openclaw|pi` installs each host's native context bridge (dry run unless `--apply`).
 Codex receives structured SessionStart JSON; Hermes, OpenCode, OpenClaw and Pi use native plugin APIs.
 See the [native host matrix](plugins/fabric-agent-adapter/skills/working-with-fabric/references/native-host-hooks.md)
@@ -204,18 +207,20 @@ With Python 3.9+ and the Claude Code CLI, in a throwaway directory and a tempora
 ```bash
 KIT=plugins/fabric-agent-adapter/skills/building-fabric-services/scripts   # or ~/.agents/skills/building-fabric-services/scripts
 DATA=$(mktemp -d); SERVICES=$(mktemp -d); WORK=$(mktemp -d)
-python3 "$KIT/sample_service.py" serve --port 47190 --data-dir "$DATA" &
-python3 "$KIT/sample_service.py" register --port 47190 --data-dir "$DATA" --services-dir "$SERVICES"
+# A free loopback port, so the sample never collides with a service already running here.
+PORT=$(python3 -c 'import socket;s=socket.socket();s.bind(("127.0.0.1",0));print(s.getsockname()[1])')
+python3 "$KIT/sample_service.py" serve --port "$PORT" --data-dir "$DATA" &
+python3 "$KIT/sample_service.py" register --port "$PORT" --data-dir "$DATA" --services-dir "$SERVICES"
 # The probe exits 0 (no FAIL); only then is the service registered for one client run (listener.owner proves the port
 # is this account's, and the client cannot check it). The token goes in a header, never in argv.
 # On macOS 27.2 run these with Apple's /usr/bin/python3: an ad-hoc-signed Python, such as Homebrew's, sees no other
 # process's sockets (FAA-272).
 python3 "$KIT/check_service.py" sample --services-dir "$SERVICES" && \
-python3 - "$DATA/service.token" "$WORK/mcp.json" <<'EOF'
+python3 - "$DATA/service.token" "$WORK/mcp.json" "$PORT" <<'EOF'
 import json, os, sys
 token = open(sys.argv[1]).read().strip()
 with os.fdopen(os.open(sys.argv[2], os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600), "w") as f:
-    json.dump({"mcpServers": {"sample": {"type": "http", "url": "http://127.0.0.1:47190/mcp",
+    json.dump({"mcpServers": {"sample": {"type": "http", "url": "http://127.0.0.1:%s/mcp" % sys.argv[3],
                "headers": {"Authorization": "Bearer " + token}}}}, f)
 EOF
 (cd "$WORK" && claude -p "Call the tool mcp__sample__sample_echo with text 'ping' and reply with only the text it returns." \
@@ -230,6 +235,8 @@ the CLI connected to the sample over streamable HTTP, called `sample.echo` and p
 ([record](docs/evidence/runs/2026-11-08-0.77.0-quick-start.md)). The probe prints one line per rule
 (`PASS`, `FAIL` or `NOT_RUN` with its evidence) and exits 1 on any `FAIL`; run it against your
 own service by its id once its installer has written the descriptor.
+The free-port line (FAA-283) was run again on 2026-11-12 from this repository's kit with Claude Code 2.1.299 and
+Apple's `/usr/bin/python3`: a port the system chose, 44 rules, 0 FAIL, `listener.owner` PASS, and `ping`.
 `FABRIC_REAL_CLIENT=1 python3 -m unittest discover -s test -p test_real_client.py` repeats the connection check
 (every sample tool listed, no model call) in the test suite.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.78.0",
+  "version": "0.79.1",
   "description": "Create Fabric-compatible agents, run them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract. This package is the installer CLI.",
   "scripts": {
     "test": "python3 test/validate.py && python3 -m unittest discover -s test -q && node --test 'test/*.test.mjs'"

package/plugins/fabric-agent-adapter/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "fabric-agent-adapter",
   "displayName": "Fabric Agent Adapter",
   "description": "Create new Fabric-compatible agents, build them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract through evidence-backed MCP, A2A, or local-runner provider bundles; and teach a coding agent to work in a project through Fabric (fabric-mcp, fabric_whoami, claim and release), with Claude Code session hooks; and put an agent on a standing watch over a product (observer mode).",
-  "version": "0.78.0",
+  "version": "0.79.1",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

package/plugins/fabric-agent-adapter/hooks/hooks.json

@@ -1,5 +1,5 @@
 {
-  "description": "Two silent-unless-relevant hook sets. The dashboard-kit notice: one line at session start or /clear in a repository that owns a Fabric service whose dashboard has no kit or an older one (fabric-dashboard/0.1, DEC-0036), phrased as an upgrade the agent may make itself. The Fabric session hooks (working-with-fabric, COM-04, FAA-12a): at session start or /clear, the preamble when Claude Code has the MCP server `fabric` and Fabric runs (fabric_whoami, then the project board through com.status and com.list, claim and release); when Fabric is down, one line, only in a project that uses Fabric (a Fabric contract file, a project-bound registration or a service descriptor naming the repository); nothing on compact or resume; each turn's facts (HEAD, files changed, lines added and removed, never content), the board's unread count, and, once the running Fabric's fabric_session_observe takes them (unless FABRIC_SESSION_NO_REPOSITORIES=1), the other repositories the turn touched (the last 512 KB of the session transcript, message text and tool output included (a secret the session displayed can be there; read in memory only), is then read and only the current turn's tool names and path arguments are used; host/owner/name leave the machine, never a local path or text) and the session's end through Fabric, only when the running Fabric advertises session-hooks/1; at each prompt one line only when the unread count rose, then each nudge a turn's answer carried, once (watch-mail prints those of turns it delivered). The session hooks are all silent in a session Fabric launched but the exit contract and the prompt hook's verdict on it and the retro line below; the dashboard-kit notice is silent only in a session started on a board request. Every hook reads no Fabric token (a credential embedded in an origin URL is read by git config and dropped in memory, never spooled or sent), prints at most one block, always exits 0 once python3 starts (on Windows it must name Python in Git Bash, FAA-183), and hands any Fabric call to a detached worker with a 10 s deadline. In a session Fabric started on a board request (FABRIC_DISPATCH_WORKFLOW), session start prints the exit contract instead of the preamble on the condition that the session's own prompt starts with the dispatch line naming the same three, launched or not, and the prompt hook, which sees that line, confirms the run or says it is none, launched or not, with no unread line or nudge, and the dashboard-kit notice says nothing (FAA-201). After a call to Fabric's fabric_work_release or fabric_task_release that releases a claim as done, PostToolUse adds one line naming the retro (FAA-206); after any other call, or a release Fabric's answer refuses (released: false, already-released) or that released nothing, nothing.",
+  "description": "Two silent-unless-relevant hook sets. The dashboard-kit notice: one line at session start or /clear in a repository that owns a Fabric service whose dashboard has no kit or an older one (fabric-dashboard/0.1, DEC-0036), phrased as an upgrade the agent may make itself. The Fabric session hooks (working-with-fabric, COM-04, FAA-12a): at session start or /clear, the preamble when Claude Code has the MCP server `fabric` and Fabric runs (fabric_whoami, then the project board through com.status and com.list, claim and release); when Fabric is down, one line, only in a project that uses Fabric (a Fabric contract file, a project-bound registration or a service descriptor naming the repository); nothing on compact or resume; each turn's facts (HEAD, files changed, lines added and removed, never content), the board's unread count, and, once the running Fabric's fabric_session_observe takes them (unless FABRIC_SESSION_NO_REPOSITORIES=1), the other repositories the turn touched (the last 512 KB of the session transcript, message text and tool output included (a secret the session displayed can be there; read in memory only), is then read and only the current turn's tool names and path arguments are used; host/owner/name leave the machine, never a local path or text) and the session's end through Fabric, only when the running Fabric advertises session-hooks/1; at each prompt one line only when the unread count rose, then each nudge a turn's answer carried, once (watch-mail prints those of turns it delivered). The session hooks are all silent in a session Fabric launched but the exit contract and the prompt hook's verdict on it and the retro line below; the dashboard-kit notice is silent only in a session started on a board request. Every hook reads no Fabric token (a credential embedded in an origin URL is read by git config and dropped in memory, never spooled or sent), prints at most one block, always exits 0 once python3 starts (on Windows it must name Python in Git Bash, FAA-183), and hands any Fabric call to a detached worker with a 10 s deadline. In a session Fabric started on a board request (FABRIC_DISPATCH_WORKFLOW), session start prints the exit contract instead of the preamble on the condition that the session's own prompt starts with the dispatch line naming the same three, launched or not (a /clear while another session holds the dispatch is told it is nested, FAA-208), and the prompt hook, which sees that line, confirms the run or says it is none, launched or not, with no unread line or nudge, and the dashboard-kit notice says nothing (FAA-201). After a call to Fabric's fabric_work_release or fabric_task_release that releases a claim as done, PostToolUse adds one line naming the retro (FAA-206); after any other call, or a release Fabric's answer refuses (released: false, already-released) or that released nothing, nothing.",
   "hooks": {
     "SessionStart": [
       {

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/SKILL.md

@@ -9,7 +9,7 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Requires filesystem access and Python 3.9+. Exact schema checks additionally need git, Node.js, pnpm, and the pinned fabric-agent-contract checkout (a public repository). Works without those tools in an explicitly degraded structural-check mode.
 metadata:
   author: PassionCode.ai
-  version: "0.78.0"
+  version: "0.79.1"
   contract-version: "0.1.0"
   contract-commit: "18f8d48762edc5bfb1433657cbfe1c16196df1a6"
 ---
@@ -100,6 +100,7 @@ is unavailable, continue only through local structure and mark exact schema vali
 
 ### 3. Scaffold the provider bundle
 
+If your organization keeps a private catalogue of agent templates with an architect, ask it first: it names the template, version, variant and known traps; this skill runs after it.
 Before scaffolding, ask the [agents database](references/agents-database.md) for an audit of the project
 (`agents-db.audit`) and carry its `optimize` proposals into the completion report.
 Load [provider bundle](references/provider-bundle.md) before creating or mapping files.
@@ -290,9 +291,10 @@ host's `open` and `fallback=never`. Never `open <url>`, `open -a Safari`, `xdg-o
 `not_installed` host; an installed host that failed to open is reported, never replaced by HTTP.
 Links carry no token or login code.
 
-The agent's `AGENTS.md` carries this as its dashboard rule block, and its checks run the adapter's link gate
-(`scripts/check_dashboard_link.py` from this skill's own directory; it is not copied into the project) on every
-completion and notification action before delivery:
+The agent's `AGENTS.md` carries this as its dashboard rule block; the agent runs the adapter's link gate
+(`scripts/check_dashboard_link.py` from this skill's own directory, an agent-side gate never copied into the project or
+run by its CI) on every completion and notification action before delivery, and the project's own test pins the
+negative fixture:
 [dashboard links](references/dashboard-links.md) has the block, the gate's input and the remote case.
 Headless agents need no dashboard.
 

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/dashboard-links.md

@@ -125,11 +125,43 @@ its acceptance does not authorize or deliver it. Enforce grants/dedup/expiry in
 the transport. Unknown or failed host status produces no executable local action.
 A separately labelled copyable link for diagnosis is not an open action.
 
-Add this check to the generated project's dashboard completion/notification
-renderer before delivery. A raw-HTTP primary action with an available host is the
-negative fixture; a valid native action is the positive one. Keep diagnostics
-separate. This gate checks structured actions, not arbitrary prose: a CLI invocation
-or instructions alone do not prove all final answers from every agent are filtered.
+The gate is **agent-side**: the agent runs it from this skill's directory before it
+delivers an action. It is never copied into the generated project and never run by
+that project's CI: the adapter's versioned plugin folder has no stable path there, so
+its result in a project's pipeline would always be NOT_RUN. A raw-HTTP primary action
+with an available host is the gate's negative fixture; a valid native action is the
+positive one. Keep diagnostics separate. This gate checks structured actions, not
+arbitrary prose: a CLI invocation or instructions alone do not prove all final answers
+from every agent are filtered.
+
+The generated project pins the same negative fixture in its own test suite, without
+calling the gate: a test that renders its completion and notification output with an
+available host and fails when a raw loopback `http_url` or a legacy `open?service=`
+link appears in it. The snippet is self-contained; `render` stands for the project's
+own renderer:
+
+```python
+import re
+import unittest
+
+RAW_LOOPBACK = re.compile(r"https?://(?:127\.0\.0\.1|localhost|\[::1\])")
+LEGACY = "fabric-dashboards://open?service="
+RESOLVED = {"service": "example-agent.default",
+            "open_link": "fabric-dashboards://service/example-agent.default?path=%2Fdashboard",
+            "http_url": "http://127.0.0.1:47195/dashboard"}
+
+
+def render(resolved, host_state):  # replace with the project's completion/notification renderer
+    raise NotImplementedError
+
+
+class RenderedDashboardLinks(unittest.TestCase):
+    def test_rendered_output_has_no_raw_loopback_or_legacy_link(self):
+        out = render(RESOLVED, host_state="available")
+        self.assertIn(RESOLVED["open_link"], out)
+        self.assertIsNone(RAW_LOOPBACK.search(out), out)
+        self.assertNotIn(LEGACY, out)
+```
 
 ## Degradation
 

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/operator-channel-and-repository.md

@@ -25,6 +25,16 @@ unless addressed (`/command@ThisBot`, a reply to its own message or a press of i
 bare `/command` in a group is not addressed), and a channel nobody receives on is `degraded`
 (`receiver-missing`). Say so in the proposal when the operator means to bind a shared group.
 
+Where the estate runs a messaging gateway service the operator chose for sending (one service every
+agent sends through, holding its own grants and allowlist), the channel sends through that gateway
+and does not call the messenger itself; the agent's own bot above is the contract's form (DEC-0034,
+OC-11) and the form used where no such gateway runs. A bot token read by polling (Telegram
+`getUpdates`) has exactly one poller across every machine: a second poller on the same token gets
+`409 Conflict` and the two take each other's updates. Check placement before polling: the instance
+on the machine the estate's placement record names for the agent polls, an instance on any other
+machine does not poll and reports `degraded` with the reason (`poller-elsewhere`), and a test starts a
+second instance placed elsewhere and sees it stay off the token.
+
 Record the answer (`accepted`, `declined` or `later`) in the agent's state and in its conformance
 report, and do not ask again; an agent that serves `surfaces.operatorChannel` also shows it as
 `proposal` in its status document. Creating the bot and putting its token into the secret store
@@ -57,9 +67,9 @@ For a PassionCode.ai repository, the agent's repository follows the organization
   and a `CLAUDE.md` whose first line is `@AGENTS.md`.
 
 Whoever owns the repository, an agent with a page gets the dashboard rule block in its `AGENTS.md`
-(pages open only in Fabric Dashboards; the block is in `references/dashboard-links.md`), and its
-checks run the adapter's link gate (`scripts/check_dashboard_link.py` from the skill's own directory, not a copy in
-the project).
+(pages open only in Fabric Dashboards; the block is in `references/dashboard-links.md`); the agent runs the
+adapter's link gate (`scripts/check_dashboard_link.py` from the skill's own directory, agent-side, never a copy in the
+project or a step of its CI), and the project's own test pins the gate's negative fixture (the same reference).
 
 org-index `scripts/check_format.py` reports 0 findings for it before it is called done. An agent
 someone builds for themselves is not a PassionCode.ai repository: its licence is its owner's

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/references/provider-entry.md

@@ -64,9 +64,9 @@ It refuses, with one sentence that never quotes a value:
 - a manifest whose name follows a backslash (`C:\Agents\example\fabric-agent.json`). The reader,
   `validate_provider_entry`, accepts it since DEC-0145 (`MANIFEST_PATTERN`, the schema's), but a reader that has not
   re-pinned to DEC-0145 refuses the entry, Fabric's registry among them (CT-192), so the writer does not emit it until
-  the oldest Fabric release in use reads it (the release after v0.3.15, CO-479). Write the path with `/` before the name. A manifest under the home folder
+  the oldest Fabric release in use reads it (Fabric v0.3.16, which shipped CO-479). Write the path with `/` before the name. A manifest under the home folder
   (`~/Agents/example/fabric-agent.json`) is read by every Fabric release; one with a drive letter
-  (`C:/Agents/example/fabric-agent.json`) only by Fabric after v0.3.15, whose registry took the repin (CO-479): v0.3.15
+  (`C:/Agents/example/fabric-agent.json`) only by Fabric v0.3.16 and later, whose registry took the repin (CO-479): v0.3.15
   and earlier read only a manifest under `~/` or `/`, so not `~\` either.
 
 `validate` also checks that the file is named `<id>.json` (FAC-SEM-014, slug half): the stem is what follows the last

package/plugins/fabric-agent-adapter/skills/adapting-projects-to-fabric/scripts/fabric_provider.py

@@ -61,8 +61,12 @@ _URL = re.compile(URL_PATTERN)
 _MANIFEST = re.compile(MANIFEST_PATTERN[:-1] + r"\Z")
 # The manifest's name after a backslash: valid since DEC-0145, but no writer emits it until every reader accepts it.
 _MANIFEST_AFTER_BACKSLASH = re.compile(r"\\fabric-agent\.json\Z")
-# format: uri (RFC 3986 absolute URI): a scheme, a colon, then no whitespace or control character.
-_URI = re.compile(r"^[A-Za-z][A-Za-z0-9+.-]*:[^\s\x00-\x1f\x7f]+\Z")
+# format: uri (RFC 3986 absolute URI) as ajv-formats reads it: RFC 3986 characters only (unreserved, reserved and %HH),
+# the class the service kit's descriptor check uses (fabric_descriptor `_SOURCE_URI`, 0.49.3); a byte-order mark, a
+# zero-width space, a non-ASCII path or an IDN host is refused (FAA-127).
+_URI = re.compile(r"^[A-Za-z][A-Za-z0-9+.-]*:(?:[A-Za-z0-9._~:/?#@!$&'()*+,;=-]|%[0-9A-Fa-f]{2})+\Z")
+# Brackets belong to an IP-literal host only (RFC 3986 3.2.2); the literal is set aside before the character check.
+_IP_LITERAL = re.compile(r"^([A-Za-z][A-Za-z0-9+.-]*://(?:[^/?#@\[\]]*@)?)\[[0-9A-Fa-f:.vV]+\]")
 # format: date-time (RFC 3339).
 _TIMESTAMP = re.compile(r"^[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]+)?([Zz]|[+-][0-9]{2}:[0-9]{2})\Z")
 FIELDS = {"protocol", "id", "providerId", "name", "summary", "manifest", "run", "source", "installedAt", "installedBy", "extensions"}
@@ -145,11 +149,14 @@ def validate_provider_entry(entry: Any) -> List[str]:
         source = entry["source"]
         if not isinstance(source, dict) or not set(source) <= {"repository"}:
             problems.append("source is {repository?}")
+        elif "repository" in source and isinstance(source["repository"], str) and (
+                _URI_PASSWORD.match(source["repository"]) or _secrets.repository_credential(source["repository"])):
+            # FAA-120, as the service kit: a repository is named, never reached with a credential in its URI. Said
+            # before the character check, so a password beside a character the URI class refuses (a backslash, as
+            # git reads one) is still named a credential (FAA-127).
+            problems.append("source.repository carries no password or credential: it names the repository")
         elif "repository" in source and not _is_uri(source["repository"]):
             problems.append("source.repository is an absolute URI")
-        elif "repository" in source and (_URI_PASSWORD.match(source["repository"]) or _secrets.repository_credential(source["repository"])):
-            # FAA-120, as the service kit: a repository is named, never reached with a credential in its URI.
-            problems.append("source.repository carries no password or credential: it names the repository")
     if not isinstance(entry["installedAt"], str) or not _TIMESTAMP.fullmatch(entry["installedAt"]):
         problems.append("installedAt is an RFC 3339 date-time")
     if not isinstance(entry["installedBy"], str) or not 1 <= len(entry["installedBy"]) <= 200:
@@ -161,7 +168,7 @@ def validate_provider_entry(entry: Any) -> List[str]:
 
 
 def _is_uri(value: Any) -> bool:
-    return isinstance(value, str) and bool(_URI.fullmatch(value))
+    return isinstance(value, str) and bool(_URI.fullmatch(_IP_LITERAL.sub(r"\1h", value, count=1)))
 
 
 def _run_problems(run: Any) -> List[str]:
@@ -255,7 +262,7 @@ def write_provider_entry(entry: Dict[str, Any], directory: Optional[Path] = None
         # re-pins (CT-192), so the writer does not emit it yet.
         raise ProviderError("The manifest's name follows a backslash, which a reader that has not re-pinned to DEC-0145 refuses (CT-192). "
                             "Write the path with / before the name: ~/.../fabric-agent.json, which every Fabric release reads, or "
-                            "C:/.../fabric-agent.json, which Fabric reads only after v0.3.15 (its repin, CO-479).")
+                            "C:/.../fabric-agent.json, which Fabric reads only from v0.3.16 (its repin, CO-479).")
     problems = manifest_problems(entry)
     if problems:
         raise ProviderError("Provider entry is invalid: %s." % "; ".join(problems))

package/plugins/fabric-agent-adapter/skills/building-fabric-services/SKILL.md

@@ -9,7 +9,7 @@ license: AGPL-3.0-only OR LicenseRef-PassionCode-Commercial
 compatibility: Python 3.9+ or Node.js 20+ for the kits (Node.js 22+ for a Linux service's instance lock); the probe needs Python 3.9+. launchd steps are macOS-only; Linux services install a systemd user unit and Windows ones a per-user Scheduled Task with the kits' writers. Dashboard handoff optionally uses Fabric Dashboards MCP link/host_status/open; without it, report unresolved host capability. The contract checkout is optional.
 metadata:
   author: PassionCode.ai
-  version: "0.78.0"
+  version: "0.79.1"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
   extension-commit: "18f8d48762edc5bfb1433657cbfe1c16196df1a6"

package/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-button.js

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.5 · Fabric's button (Fabric Agent Contract DEC-0040, FB-1…FB-8, FL-1…FL-6)
+/* fabric-dashboard-kit@1.1.6 · Fabric's button (Fabric Agent Contract DEC-0040, FB-1…FB-8, FL-1…FL-6)
    Load it same-origin, after fabric-dashboard.css, with the service it opens Fabric on:
      <script src="fabric-button.js" defer data-service="example-agent.default" data-service-name="Example Agent"
              data-project="project-a" data-project-name="Project A"></script>
@@ -11,7 +11,7 @@
 (function (root) {
   'use strict';
 
-  var VERSION = '1.1.5';
+  var VERSION = '1.1.6';
   var COOKIE = 'fabric_button';
   var GET_FABRIC = 'https://passioncode.ai/fabric';
   var ABSENT_AFTER_MS = 1500;
@@ -69,7 +69,10 @@
       if (piece === '') return;
       var at = piece.indexOf('=');
       var name = firstKey(at < 0 ? piece : piece.slice(0, at));
-      values.set(name, (values.get(name) || []).concat(at < 0 ? '' : decodeKeepingPlus(piece.slice(at + 1))));
+      var value = at < 0 ? '' : decodeKeepingPlus(piece.slice(at + 1));
+      var list = values.get(name);
+      if (list) list.push(value); // appended in place, as the contract's secret-shape.ts does (FAA-245)
+      else values.set(name, [value]);
     });
     return values;
   }

package/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-dashboard.css

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.5 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.6 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
    A Fabric service dashboard shown inside a host pane: usable from 360 CSS px up, navigation always
    reachable, wide content in its own scroll box, one vertical scroller, appearance from the host.
    Copy this file next to fabric-dashboard.js; do not edit it in place. Put the page's own rules in

package/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/fabric-dashboard.js

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.5 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.6 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
    Load it same-origin with <script src="fabric-dashboard.js" defer></script>: no inline script, no
    eval, nothing from a CDN. It applies the host's appearance (ED-6, ED-8), folds navigation that
    does not fit into a More menu (ED-3), makes wide boxes keyboard-reachable (ED-4) and keeps
@@ -8,7 +8,7 @@
   'use strict';
 
   var KIT = 'fabric-dashboard-kit';
-  var VERSION = '1.1.5';
+  var VERSION = '1.1.6';
   /* fabric-dashboard-kit:theme-ids:begin */
   var THEMES = ['graphite', 'fabric', 'paper', 'forest', 'ocean', 'ember', 'contrast'];
 /* fabric-dashboard-kit:theme-ids:end */
@@ -148,6 +148,20 @@
     root.addEventListener('focus', applyAppearance);
   }
 
+  /* ---- resize observers write in the next frame (since 1.1.6) ----
+     A ResizeObserver callback that changes the size of what it watches, or of an ancestor, makes WebKit raise
+     "ResizeObserver loop completed with undelivered notifications". So a callback only schedules the work for the next
+     animation frame, cancelling one already scheduled, and the work itself skips a size it has already laid out. */
+  function nextFrame(work) {
+    var pending = null;
+    var raf = root.requestAnimationFrame;
+    return function () {
+      if (typeof raf !== 'function') { work(); return; }
+      if (pending !== null) root.cancelAnimationFrame(pending);
+      pending = raf.call(root, function () { pending = null; work(); });
+    };
+  }
+
   /* ---- navigation: fold what does not fit into More (ED-3) ---- */
   function foldNav(nav) {
     if (typeof nav.fdRefresh === 'function') { nav.fdRefresh(); return; } // folded already: refit, no second observers
@@ -212,8 +226,16 @@
       }
     }
     layout();
-    if (typeof root.ResizeObserver === 'function') new root.ResizeObserver(function () { layout(); }).observe(nav);
-    else root.addEventListener('resize', layout);
+    // The fit depends on the nav's width only: a callback for a height the fold itself changed lays nothing out.
+    var laidOutWidth = null;
+    var refit = nextFrame(function () {
+      var width = nav.clientWidth;
+      if (width === laidOutWidth) return;
+      laidOutWidth = width;
+      layout();
+    });
+    if (typeof root.ResizeObserver === 'function') new root.ResizeObserver(refit).observe(nav);
+    else root.addEventListener('resize', refit);
     // A page that moves aria-current (its route changed) gets a fresh summary and fit, without telling the kit.
     if (typeof root.MutationObserver === 'function') {
       new root.MutationObserver(layout).observe(nav, { subtree: true, attributes: true, attributeFilter: ['aria-current'] });
@@ -255,12 +277,16 @@
       var header = chrome.querySelector('.fd-header');
       var lift = 0;
       if (height > limit && header) lift = Math.min(Math.ceil(header.getBoundingClientRect().height), height);
-      html.style.setProperty('--fd-chrome-top', lift ? -lift + 'px' : '0px');
-      html.style.setProperty('--fd-chrome-h', Math.max(0, height - lift) + 'px');
+      var top = lift ? -lift + 'px' : '0px';
+      var pinned = Math.max(0, height - lift) + 'px';
+      // An unchanged value is not written again: a write restyles the page and can wake the observer once more.
+      if (html.style.getPropertyValue('--fd-chrome-top') !== top) html.style.setProperty('--fd-chrome-top', top);
+      if (html.style.getPropertyValue('--fd-chrome-h') !== pinned) html.style.setProperty('--fd-chrome-h', pinned);
     }
     set();
-    if (typeof root.ResizeObserver === 'function') new root.ResizeObserver(set).observe(chrome);
-    root.addEventListener('resize', set);
+    var reset = nextFrame(set);
+    if (typeof root.ResizeObserver === 'function') new root.ResizeObserver(reset).observe(chrome);
+    root.addEventListener('resize', reset);
   }
 
   function init() {

package/plugins/fabric-agent-adapter/skills/building-fabric-services/assets/dashboard-kit/kit.json

@@ -1,6 +1,6 @@
 {
   "name": "fabric-dashboard-kit",
-  "version": "1.1.5",
+  "version": "1.1.6",
   "profile": "fabric-dashboard/0.1",
   "decision": "DEC-0036",
   "declarationKey": "https://fabric.passioncode.ai/agent-contract/extensions/dashboard/0.1",
@@ -15,9 +15,9 @@
     "contrast"
   ],
   "files": {
-    "fabric-dashboard.css": "cc7a96fa2c5eeb03d113e7a543ed88d43ce78c2808c411de199ea0fc6d55b957",
-    "fabric-dashboard.js": "5df01193c590a1d8aa82a521954902fecf2d7f655df482165f90d7291b00087f",
-    "fabric-button.js": "e945b3252f9a246826d06dbe7bd4be66e82d539a33728c3d3043fd61d4cbd681",
+    "fabric-dashboard.css": "7a90bbe1f1a2170df5dac0f596a3f302167bef9a7243457bb21dd0eb34f4d359",
+    "fabric-dashboard.js": "146ec9a0fd50af2df3245c02ec7dfba75b7d4e8cb5476fedb5ef727869fef1cc",
+    "fabric-button.js": "60c2b6d44571213e0237c29a94a4cf220f9de3efcfa697ac6a33777d1ad25fd6",
     "themes.json": "511839f1a1a83eb37fadfd132791474497d5c28c5091700b9aa31ad076e359b5"
   },
   "history": {
@@ -54,6 +54,11 @@
       "fabric-dashboard.css": "cc7a96fa2c5eeb03d113e7a543ed88d43ce78c2808c411de199ea0fc6d55b957",
       "fabric-dashboard.js": "5df01193c590a1d8aa82a521954902fecf2d7f655df482165f90d7291b00087f",
       "fabric-button.js": "e945b3252f9a246826d06dbe7bd4be66e82d539a33728c3d3043fd61d4cbd681"
+    },
+    "1.1.6": {
+      "fabric-dashboard.css": "7a90bbe1f1a2170df5dac0f596a3f302167bef9a7243457bb21dd0eb34f4d359",
+      "fabric-dashboard.js": "146ec9a0fd50af2df3245c02ec7dfba75b7d4e8cb5476fedb5ef727869fef1cc",
+      "fabric-button.js": "60c2b6d44571213e0237c29a94a4cf220f9de3efcfa697ac6a33777d1ad25fd6"
     }
   }
 }

package/plugins/fabric-agent-adapter/skills/building-fabric-services/references/board.md

@@ -26,8 +26,10 @@ skill's business (working-with-fabric, `references/project-board.md`).
 
 A **request** is addressed to a Project and one of its capabilities (`video.render`), never to a service. One
 **responder slot** exists per Project and capability; a service holds it under a **`board.respond` grant** the
-operator gives in Fabric (Agents & access): callee `fabric`, capability `board.respond`, resource
-`board:<project id>/<capability>`. A pid, a descriptor or a localhost origin authorizes nothing.
+operator gives in Fabric (Settings → Agent access): callee `fabric`, capability `board.respond`, resource
+`board:<project id>/<capability>`. A pid, a descriptor or a localhost origin authorizes nothing. The capability is
+never `project.work`: DEC-0140 PR-1 reserves it for a Project's primary responder, a coding session, and `Responder`
+refuses it with `invalid_arguments` (FAA-244).
 
 1. Ask once, through the hub's door: `HubClient().request_board_access(agent_id, project_id, [capability], reason)`
    (`requestBoardAccess`). Keep the answer's `pollSecret` in memory or a 0600 file.
@@ -37,8 +39,9 @@ operator gives in Fabric (Agents & access): callee `fabric`, capability `board.r
 3. Each connection joins with `fabric.board.join {projectId}` (`join_board` / `joinBoard`). It re-reads `hub.json`,
    checks the pid it names is alive, tells the owner of the door's listener from the socket table (DEC-0154 HA-2:
    another OS account's process, or one whose owner cannot be told, is `HubError` code `foreign-user`, retryable, with
-   nothing sent; a retry never clears a restricted macOS table, `table-restricted` in protocol.md, FAA-272), and only then sends the credential (a session already running maps that refusal, as any transport
-   failure, to `board.down` with reason `unreachable` until FAA-252). A missing grant is `HubError` code
+   nothing sent; a retry never clears a restricted macOS table, `table-restricted` in protocol.md, FAA-272), and only then sends the credential (a session already running carries that refusal as `BoardError` code
+   `foreign-user`, one of `SESSION_CODES`, to `board.down` with reason `foreign-user` and a sentence that says nothing
+   was sent, never `unreachable`'s "a write may have been stored", FAA-252). A missing grant is `HubError` code
    `not_authorized` whose `data.ask` holds the arguments to ask with.
 
 ## Wiring it into the service
@@ -302,7 +305,7 @@ held and not transferred). The responder keeps that move instead of undoing it:
   after the slot had moved past the record, reads as a move: the safe side; a slot such a replay took is left to lapse
   unused. A generation written `2.0` is `2`.
 - The operator may move the slot back to this session in Fabric (DEC-0140 PR-2), which this client cannot hear. No
-  Fabric release offers the operator's move yet (Fabric 0.3.15 has none: the control is CT-174's in Fabric, its agent twin CT-181 in the contract, then CT-125),
+  Fabric release through v0.3.19 (2026-11-11) offers the operator's move (the control is CT-174's in Fabric, its agent twin CT-181 in the contract, then CT-125),
   so today every move is another session taking the slot and take-back is the route back; the check below is ready
   for the move. While
   a slot is moved the responder reads `com.status` once a renewal (20 s) and, when the slot's generation is past the