@passioncode-ai/fabric-agent-adapter 0.49.3 → 0.51.1

package/CHANGELOG.md

@@ -1,5 +1,113 @@
 # Changelog
 
+## 0.51.1 (2026-10-26)
+
+The tag `v0.51.0` was never published: its release run stopped at the Node 18 floor, so 0.51.1 is the first npm
+release carrying everything listed under 0.51.0 below.
+
+### Fixed
+
+- The tests of one instance per context (`test/fabric-context.test.mjs`, FAA-125) skip on Linux under a Node that
+  cannot bind an abstract socket name exactly (Node 18 and 20), as every other lock test does since FAA-72. The kit
+  itself already refused there with a sentence; only the tests lacked the guard.
+- `references/package.md` no longer says the passkey countersignature waits for `org-authority/1`: DEC-0129 decided
+  that protocol only as the organization's member list for relay admission, and the countersignature waits for the
+  decision that defines the `org-countersign/1` verifier (contract finding on board thread `6c50c84f`).
+
+## 0.51.0 (2026-10-26)
+
+### Changed
+
+- **Pinned to the contract release `v0.1.0+2026-10-26.2` (`e6c4fc16`)** (FAA-128). It carries DEC-0122 to DEC-0125;
+  `a3a66eb0` and `52c7d798` stay supported. Brief: `docs/evidence/specs/2026-10-26-faa-128-125-repin-a3a66eb-brief.md`.
+- **Narrowings (DEC-0123, FAA-132).** `url_request` / `urlRequest` now refuses a loopback page URL (`http://127.0.0.1`
+  and every other spelling of a local address): hand a service's page over as Fabric Dashboards' `open_link`
+  (`page_answer` / `pageAnswer` builds it). `check_dashboard_link.py` refuses the legacy `open?service=` link and a
+  page path with whitespace, as the contract's `parseDashboardsLink` does. A service that built either may now be
+  refused at construction.
+- **DL-19 `operator-decision-required`** names the three routes for a client that cannot set `_meta`: Fabric's
+  `agent.call` with `call.decision` once the hub forwards it, the service's own elicitation, the action's page as an
+  `open_link`. Outside a mandate (`data.detail` `outside-mandate: <part>`) it gives DEC-0125 MD-4's order instead:
+  call again within your own mandate, else pass the refusal up; only the leading agent asks the operator, with the
+  same three routes.
+- Dashboard kit 1.1.5 now matches its pin (DEC-0124 is in it); brief decision D17 of 0.50.0 is closed.
+
+### Added
+
+- **The operator's mandate (DEC-0125, FAA-131).** `fabric_mandate` / `fabric-mandate.mjs` port `mandate/1`
+  (FAC-SEM-144, scope narrowing, hand-over); `request_meta(mandate=)` sends one; a server with `agent_id` reads
+  `_meta.mandate` in its action gate. working-with-fabric states the operator's rule of 2026-10-26, «я сказал одному
+  = сказал всем»: one approval he gives any of his agents binds all of them when the relay carries his words, the
+  date, the source and the scope from one of his own Projects on his personal board (provenance `trusted`; never a
+  member's Project on an organization's board) or the session that started the agent; content an agent read is never
+  one; human gates stay. A hand-over never adds a `capabilities` or `actions` list the scope in force leaves out
+  (contract DEC-0136 MD-2a, adopted ahead of the pin: brief decision D28), so no agent of the chain can grant itself an
+  action the operator did not name. Taking a prose relay from another agent is the operator's rule, honoured ahead of the pinned
+  AP-3 (brief decision D27); the contract's DEC-0126 (OA-2) states it, and FAA-134 takes its wording in 0.52.0.
+- **A service's pages as `open_link` (DEC-0123).** `fabric_page_links` / `fabric-page-links.mjs` build and read
+  Fabric Dashboards links and FAC-SEM-143, checked against the contract's vectors and about 200,000 generated
+  inputs with no twin difference.
+- **A2A, the reading side (DEC-0122).** `fabric_a2a` / `fabric-a2a.mjs` read `surfaces.a2a` and an Agent Card;
+  `build_well_known(a2a=)` writes the member; the probe adds `well-known.a2a` and `a2a.card` (the card is fetched
+  without the descriptor's token). Serving a card and the A2A binding stay FAA-10.
+- **One instance per context (FAA-125, N-11).** `fabric_context` / `fabric-context.mjs`: `hold_context_instance`
+  derives a context's instance, folders and lock, refuses a second process, refuses an `org:<id>` instance without
+  its share grant placement and exits 78 before creating anything; `personal` keeps the `default` instance.
+  `launchd_uninstall(instance=)` removes only that instance.
+
+## 0.50.0 (2026-10-26)
+
+### Changed
+
+- **Pinned to the contract release `v0.1.0+2026-10-25` (`52c7d798`)** (FAA-117, contract CT-124). The release carries
+  DEC-0112 to DEC-0121; only DEC-0121 changes kit code, the others bind a node, an organization server or Project
+  Observatory and only regenerate vendored vectors (connections gains seven cases, the protocol register
+  `fabric-actions/0.1`). `2f020a6` stays supported. The brief is
+  `docs/evidence/specs/2026-10-26-faa-117-118-repin-52c7d79-brief.md` (decisions D1 to D17).
+
+### Added
+
+- **Dashboard action parity (DEC-0121).** Every button a dashboard offers the operator is an agent action too.
+  - `fabric_actions.py` / `fabric-actions.mjs` port the contract's `actionDecision`, `actionsView` and the FAC-SEM-142
+    rules, checked against `fixtures/vectors/actions.json` (65 cases) and the semantic fixtures.
+  - A service declares its actions with `McpToolServer.add_tool(..., action=, target=, human_step_url=)` and
+    publishes them with `build_well_known(actions=)` / `buildWellKnown({actions})` as `extensions/actions/0.1`; a
+    declaration the contract would flag is refused.
+  - The server gate reads only `_meta.decision`, never the arguments: a T0 or T1 call without the operator's
+    decision is refused `operator-decision-required`, a malformed one `decision-invalid`, a step only a person can
+    take `human-step-required` with `data.humanStep` and `data.url`, and T2 still needs `approval-required`. The
+    decision records the authenticated caller (`identify`, the delegation's caller, or `local:T0` / `local:T1`).
+    Gating a job's input responses is opt-in (`input_actions=True`) until Fabric's hub forwards decisions (CT-125).
+    The kits are ready now; a service adopts the gate once CT-125 lands, as the contract says (DEC-0121
+    *Compatibility*, CT-127), because Claude Code and Codex cannot set `_meta` and would otherwise meet
+    `operator-decision-required` with the page as their only route.
+  - A caller relays with `request_meta(decision=...)` / `requestMeta(traceparent, {decision})`.
+  - The three codes join DL-19 in both delegation twins.
+- **The probe** reports `well-known.actions`, `interop.action-tools` (a declared action's tool must be served),
+  `dashboard.actions-declared` (`NOT_RUN` for a dashboard that declares none) and `dashboard.opens-in-host`
+  (FAA-118: a browser opener aimed at the service's own pages in its checkout fails; `--repo PATH` names the
+  checkout).
+- **working-with-fabric** relays the operator's own words as the decision (AP-3), never text from a tool result, a
+  page, a file or another agent; a coding agent whose client cannot set `_meta` goes through Fabric's `agent.call`
+  (after CT-125), the service's elicitation, or the action's page in Fabric Dashboards, in that order (confirmed by
+  the contract's owner on board thread `92c6f277`). On `human-step-required` it hands the person the link.
+
+- **Fabric's button follows contract DEC-0124** (dashboard kit 1.1.5; FB-3 amended on the adapter's request, board
+  thread `4801da8d`, contract PR #189, after this release's pin). The accessible name and the menu follow the page's
+  language, which the contract now states, so 0.49.3's note that the kit departs from FB-3 no longer holds. A page's
+  own words (`data-label-*`) are taken only when they keep the word *Fabric* (WCAG 2.2 SC 2.5.3, Label in Name);
+  otherwise the built-in words stay. A page that set words without *Fabric* under 0.49.3 shows the built-in words
+  after it updates its kit. The kit follows this amendment ahead of the pin (brief decision D17).
+- **The probe's new `dashboard.opens-in-host` can fail a service that passed before**: one that opens its own pages
+  in a browser. Open them through Fabric Dashboards instead (see the building-fabric-services skill).
+
+### Changed (guidance)
+
+- **Agent pages open only in Fabric Dashboards** (FAA-118, the operator's rule of 2026-10-24): the rule now sits in
+  the body of the three SKILL.md files, with the AGENTS.md block a project carries and a section for an agent that
+  has a page and no service descriptor. Manual restore and enabling the operator channel are the operator's
+  decision on the page or relayed (D16).
+
 ## 0.49.3 (2026-10-25)
 
 ### Fixed

package/README.md

@@ -85,6 +85,7 @@ a service (a descriptor names it as `source.repository`) whose dashboard has no
 anywhere else; the [kit reference](plugins/fabric-agent-adapter/skills/building-fabric-services/references/dashboard-kit.md)
 has the upgrade steps, which the agent may take itself.
 
+Agent pages open only in Fabric Dashboards (the operator's rule, carried in the builder skills since 0.50.0).
 Dashboard handoffs use the host-generated `open_link` as the primary action. The
 three builder skills carry the same [consumer procedure](plugins/fabric-agent-adapter/skills/building-fabric-services/references/dashboard-links.md)
 and a portable `scripts/check_dashboard_link.py` gate for generated renderers.
@@ -98,7 +99,11 @@ is the MCP tool of its name, long work is a job with a stable id (`fabric.job.ge
 `fabric.job.cancel`), a question for a person is an elicitation, and every call carries
 one W3C trace. The kits ship the helpers (`scripts/fabric_interop.py`,
 `scripts/fabric-interop.mjs`), the sample service serves a job end to end, and the probe
-checks the interop rules. A job a provider limit paused or stopped, and an effect nobody saw, carry their own codes
+checks the interop rules. Every dashboard button has a tool (`fabric-actions/0.1`, contract DEC-0121): the
+operator's agent relays their decision in `_meta.decision` (a service adopts the gate once Fabric's hub forwards
+decisions, CT-125; Claude Code and Codex, which cannot set `_meta`, relay through Fabric's `agent.call`, the service's
+own elicitation or the action's page), and the refusals `operator-decision-required`,
+`decision-invalid` and `human-step-required` say what is missing. A job a provider limit paused or stopped, and an effect nobody saw, carry their own codes
 (`quota-exhausted`, `outcome-unknown`) and keys per caller (contract DEC-0087). The estate kits check share grants into
 an organization (`scripts/fabric_share.py`, DEC-0086) and the estate ceremonies: a revision's record rules, a headless
 machine's enroll token, the nearby pairing by a comparison code and the hub's single use of a token
@@ -275,7 +280,7 @@ Scaffolding is non-destructive by default. It writes only the paths declared in
 The default pin for new bundles is [`fabric-contract.lock.json`](fabric-contract.lock.json):
 
 - version: `0.1.0`
-- commit: `2f020a696453ae299b123517f14957f6a1354379`
+- commit: `e6c4fc16b415eec3190dd34d924d269405359dc9`
 
 Every other mention of the default contract revision (this section, the skills' metadata, the
 skill card, `adapt_project.py`) must equal it; `python3 test/validate.py` fails a tree

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@passioncode-ai/fabric-agent-adapter",
-  "version": "0.49.3",
+  "version": "0.51.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.",
-  "version": "0.49.3",
+  "version": "0.51.1",
   "author": {
     "name": "PassionCode.ai",
     "url": "https://passioncode.ai/"

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

@@ -5,9 +5,9 @@ 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.49.3"
+  version: "0.51.1"
   contract-version: "0.1.0"
-  contract-commit: "2f020a696453ae299b123517f14957f6a1354379"
+  contract-commit: "e6c4fc16b415eec3190dd34d924d269405359dc9"
 ---
 
 # Adapting projects to Fabric
@@ -76,7 +76,7 @@ Use exactly:
 
 - contract version `0.1.0`;
 - repository `https://github.com/passioncode-ai/fabric-agent-contract`;
-- commit `2f020a696453ae299b123517f14957f6a1354379`.
+- commit `e6c4fc16b415eec3190dd34d924d269405359dc9`.
 
 This is the default for new bundles. When checking an issued legacy bundle, preserve its
 explicit supported lock and use that exact clean checkout. Never silently upgrade or
@@ -218,9 +218,9 @@ not a connected provider.
 If the agent has a human stop (a choice, an approval, a confirmation) or emits `notify: true`
 events, propose its operator channel (`fabric-operator-channel/0.1`, OC-11) to the operator once,
 now, as [the operator channel and the repository standard](references/operator-channel-and-repository.md)
-describes: the operator's four steps, the answer recorded and never asked again, and the bot, the
-token and enabling the channel left to the operator. An agent with neither stops nor notify events
-skips this step.
+describes: the operator's four steps, the answer recorded and never asked again, the bot and the
+token left to the person, and enabling the channel to the operator's decision (on the page or
+relayed, DEC-0121). An agent with neither stops nor notify events skips this step.
 
 ## The repository around the provider
 
@@ -245,8 +245,26 @@ Report:
 Never summarize the outcome as “Fabric-compatible” unless all required admission gates
 passed against a real provider and the project binding is valid.
 
-## Dashboard handoff: also for consumers
-
-When handing a registered service dashboard to a person, or writing the generated agent's
-completion or notification instructions, read and apply [dashboard links](references/dashboard-links.md)
-and run its output gate before delivery, in any host. Headless agents need no dashboard.
+## Agent pages open only in Fabric Dashboards
+
+The operator's rule (2026-10-24) for every page of an agent or a local Fabric service, in any host: a
+link in an answer or a notification, `<tool> dashboard`, a completion message, a page the agent opens
+itself. Hand over the `open_link` the `fabric-dashboards` MCP's `link` tool returns for the exact
+registered service key (`list_services`, never guessed) and the page's path; open it only with the
+host's `open` and `fallback=never`. Never `open <url>`, `open -a Safari`, `xdg-open`,
+`webbrowser.open` or `shell.openExternal` aimed at the agent's pages. A browser only on a confirmed
+`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:
+[dashboard links](references/dashboard-links.md) has the block, the gate's input and the remote case.
+Headless agents need no dashboard.
+
+## An agent with a page and no service descriptor
+
+A local page no service descriptor names cannot open in Fabric Dashboards. Never open it in a browser
+instead: make the agent a `fabric-service/0.1` service with `building-fabric-services` (the descriptor,
+the well-known document, the login-code routes and a declared dashboard), and until that lands file a
+board row for it and say the page waits on it.

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

@@ -5,6 +5,19 @@ an existing Fabric service dashboard to a person. This also applies to generated
 agent instructions and completion messages. Headless agents need no dashboard;
 API origins, external docs and OAuth links are not dashboard actions.
 
+The rule (the operator's, 2026-10-24): every page of an agent or a local Fabric
+service opens only in Fabric Dashboards, never in Safari, Dia, Chrome or any
+other browser, unless Fabric Dashboards is confirmed not installed.
+
+## Contents
+
+- Resolve, then hand over
+- The block a generated AGENTS.md carries
+- An agent with a page and no service descriptor
+- Device and channel
+- Portable output gate
+- Degradation
+
 ## Resolve, then hand over
 
 1. Discover the target computer and exact registered `service.id.instance`.
@@ -20,9 +33,12 @@ API origins, external docs and OAuth links are not dashboard actions.
    compatible host resolver or report the limitation, not presumed absence.
 4. A request for a link opens nothing. A request to open uses the host `open`
    tool/approved opener, which starts or focuses the existing Fabric Dashboards
-   and reuses the service view. `fallback=never` forbids a browser; `if_absent`
-   permits one only for confirmed absence. Discover schema support first: older
-   `open` implementations may silently fall back on failure and are not strict.
+   and reuses the service view, with `fallback=never`: it forbids a browser.
+   `if_absent` permits one only for confirmed absence. Discover schema support
+   first: older `open` implementations may silently fall back on failure and are
+   not strict. Never
+   `open <url>`, `open -a Safari`, `xdg-open`, `start <url>`, `webbrowser.open`
+   or `shell.openExternal` aimed at the service's pages.
 5. An installed host that failed to open is **not absent**. Report the failure;
    do not silently launch HTTP in a browser, a second server, `npm run dev`, or
    another standalone dashboard. A stopped backend stays on its host status/Start
@@ -31,6 +47,40 @@ API origins, external docs and OAuth links are not dashboard actions.
    not page readiness, a successful login, or a completed job. Links carry no
    bearer tokens or login codes. The host handles dashboard authentication.
 
+## The block a generated AGENTS.md carries
+
+An agent with a page carries this block in its `AGENTS.md` (its `CLAUDE.md` reads
+it through `@AGENTS.md`), beside its browser rule, and its completion and
+notification renderers follow it:
+
+```markdown
+## Pages open only in Fabric Dashboards
+
+Every page of this agent (its dashboard, a job, an approval, a report) opens in
+Fabric Dashboards, never in a browser. Resolve the registered service key with
+the fabric-dashboards MCP (`list_services`, never guessed) and hand over the
+`open_link` its `link` tool returns for the page's path; to open it, call the
+host's `open` with `fallback=never`. Never `open <url>`, `open -a Safari`,
+`xdg-open`, `start <url>`, `webbrowser.open` or `shell.openExternal` on this
+agent's pages. A browser only when `host_status` confirms `not_installed`; an
+installed host that failed to open is reported, not replaced by HTTP. Links
+carry no token or login code. Every completion and notification action passes
+the Fabric Agent Adapter's link gate before delivery: `check_dashboard_link.py`
+in its `building-fabric-services/scripts`, run from that skill's directory;
+where it cannot run, the action is compared by hand and the check is NOT_RUN.
+```
+
+The project's checks run the gate below on each renderer's action, and a test
+holds a raw-HTTP primary action beside an available host refused.
+
+## An agent with a page and no service descriptor
+
+Fabric Dashboards opens only a page a service descriptor names. An agent that
+serves a local page without one cannot be opened there, and a browser is not the
+workaround. Make it a `fabric-service/0.1` service (`building-fabric-services`:
+the descriptor, the well-known document, the login-code routes and a declared
+dashboard); until that lands, file a board row for it and say the page waits on it.
+
 ## Device and channel
 
 A custom scheme opens on the device receiving it. A phone's localhost is not the
@@ -90,5 +140,8 @@ or instructions alone do not prove all final answers from every agent are filter
 
 Syntax is owned by Fabric Dashboards and `@passioncode-ai/fabric-service-host`:
 [ADR-0005](https://github.com/passioncode-ai/fabric-dashboards/blob/51a7a80acf42781d7bec304cc87c655d48cc309b/docs/adr/0005-service-links.md).
-The gate accepts canonical links and the legacy `open?service=` form returned by
-older hosts; it does not generate either dialect or redefine the Fabric wire contract.
+The gate accepts only the service form, `fabric-dashboards://service/SERVICE_ID.INSTANCE`
+with at most one `path`; since 0.51.0 it refuses the legacy `open?service=` form, as contract
+DEC-0123 (PL-1, checker rule `FAC-SEM-143`) and its vectors do. A host that still returns the
+legacy form fails the gate: report it as an installed host that did not open the page. The gate
+does not generate links or redefine the Fabric wire contract.

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

@@ -26,9 +26,12 @@ bare `/command` in a group is not addressed), and a channel nobody receives on i
 
 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, storing the token and enabling the channel
-are the operator's action: never create the bot, ask for or store the token's value, or enable the
-channel yourself. The default pin carries DEC-0034 and DEC-0035: a served status document is
+`proposal` in its status document. Creating the bot and putting its token into the secret store
+stay the person's (a `secret` step, contract DEC-0121 AP-4): never create the bot, or ask for or
+store the token's value. Enabling the channel, and removing a webhook found on its token, are the
+operator's decision, taken by them on the agent's page or relayed to its agent in their own words
+with `_meta.decision` (OC-1, OC-2, DEC-0121 AP-2); never enable it on your own account. The default
+pin carries DEC-0034 and DEC-0035: a served status document is
 checked against the pinned `schemas/operator-channel-status.schema.json`; the channel's runtime
 rules have no probe rule here yet, so report them `NOT_RUN`. An agent with neither stops nor notify
 events skips this.
@@ -49,6 +52,11 @@ For a PassionCode.ai repository, the agent's repository follows the organization
 - an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
   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).
+
 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
 choice, nothing about it is published or listed by the organization, and none of these files is

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

@@ -22,10 +22,10 @@ import fabric_secrets as _secrets  # noqa: E402 - the contract's credential dete
 
 CONTRACT_VERSION = "0.1.0"
 CONTRACT_REPOSITORY = "https://github.com/passioncode-ai/fabric-agent-contract"
-CONTRACT_COMMIT = "2f020a696453ae299b123517f14957f6a1354379"
+CONTRACT_COMMIT = "e6c4fc16b415eec3190dd34d924d269405359dc9"
 # #region supported-contract-revisions — docs: README.md#contract-pin
 # Only this declaration may name a legacy revision in live files.
-SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "87d384ffce2757081b7ab227e5dad3dddd08328f", "0a4ce773c4b9e6bec40c6387eb3f988af7152c0e", "e742016dc396aa31e5a13a893489e43f15786c69", "bfa9a67aa3c6cb808c093e7d83cd59799f1ee7d0", "c55f2d5a11c9a0197e958e87212fca7ae1154769", "07042181bfae2a481aa0da1a5651f24c76669c48", "d8146cfb0a1c74fc6432284c4356bb0c864b37b5", "82e163665e156a08aa3b92e4711015582c06162c", "1636fa97262f4a26e2086572d540c2ee701e0010", "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
+SUPPORTED_CONTRACT_COMMITS = (CONTRACT_COMMIT, "a3a66eb0052043847f6556348e37d34ca873a629", "52c7d798b9f4eb784eb4e29e717038a8912c759d", "2f020a696453ae299b123517f14957f6a1354379", "87d384ffce2757081b7ab227e5dad3dddd08328f", "0a4ce773c4b9e6bec40c6387eb3f988af7152c0e", "e742016dc396aa31e5a13a893489e43f15786c69", "bfa9a67aa3c6cb808c093e7d83cd59799f1ee7d0", "c55f2d5a11c9a0197e958e87212fca7ae1154769", "07042181bfae2a481aa0da1a5651f24c76669c48", "d8146cfb0a1c74fc6432284c4356bb0c864b37b5", "82e163665e156a08aa3b92e4711015582c06162c", "1636fa97262f4a26e2086572d540c2ee701e0010", "f00a7685e3861c27f7899c033fb850a145a1708f", "a046f57cf46ea9e3da57ff8ce6a3ed4d26d8774b", "fe55fc67cba1a9e34a736da7d148d4fe2a8fbfa0", "b291bf09e0a9f9fd3c16cf540832cd021203b7d1", "0cacd08b0e95b6abf131eae1206b60792138bc3c", "2eb91c00e852d9c31d804310d38fad91589fcbac", "8e49fbd5fbbf230e32c1969cd24ac3c22422f0a5", "a83bec6b47776af688402c18efec507143061f68", "52da526d7cc1e063d74c5b520dbc03d0ace15246", "78b2da018d2c4bd9ac1bde1dc3b7f1a110a175f5", "623bf61358c339cb10297807b3f024b5d9f1f327", "23f9fda4c05f8a3852246ee98d4f2adf74ed0875", "9091d3d6606b0c4b5591a38c3674356a01fd7f55", "df55c8c54a23251342a7ee57ba95642b7eb39e61", "2ce392291c6668598d12cd38327e24696b5ca15c")
 # #endregion supported-contract-revisions
 INTEROP_KEY = "https://fabric.passioncode.ai/agent-contract/extensions/interop/0.1"
 MCP_REVISION = "2026-07-28"

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

@@ -74,7 +74,9 @@ def login_path(path):
 
 def safe_path(path):
     return (isinstance(path, str) and path.startswith('/') and not path.startswith('//')
-            and len(path) <= 2048 and not re.search(r'[\\\x00-\x1f\x7f]', path))
+            and len(path) <= 2048 and not re.search(r'[\\\x00-\x1f\x7f]', path)
+            # JavaScript's whitespace (\s), which the contract's parseDashboardsLink refuses in a page (DEC-0123)
+            and not re.search('[ \u00a0\u1680\u2000-\u200a\u2028\u2029\u202f\u205f\u3000\ufeff]', path))
 
 
 def check(data):
@@ -87,11 +89,11 @@ def check(data):
     require(not re.search(r'[\\\x00-\x20\x7f]', native + http), 'unsafe_url')
     deep, plain = urlsplit(native), urlsplit(http)
     require(deep.scheme == 'fabric-dashboards' and not deep.username and not deep.password and not deep.port and not deep.fragment, 'invalid_deep_link')
-    query = parse_qs(deep.query, keep_blank_values=True, strict_parsing=True)
-    if deep.netloc == 'service':
-        require(deep.path in ('/' + service, '/' + service + '/') and set(query) <= {'path'}, 'wrong_service_or_parameter')
-    else:
-        require(deep.netloc == 'open' and deep.path in ('', '/') and query.get('service') == [service] and set(query) <= {'service', 'path'}, 'invalid_legacy_link')
+    # An empty query is no fields: Python 3.9's strict parse_qs raises on '' where 3.11 and later answer {}.
+    query = parse_qs(deep.query, keep_blank_values=True, strict_parsing=True) if deep.query else {}
+    # DEC-0123 PL-1: only the service form; the legacy open?service= link is refused (FAC-SEM-143, since 0.51.0).
+    require(deep.netloc == 'service', 'not_service_link')
+    require(deep.path in ('/' + service, '/' + service + '/') and set(query) <= {'path'}, 'wrong_service_or_parameter')
     require('path' not in query or len(query['path']) == 1, 'duplicate_path')
     page = query.get('path', [None])[0]
     require(page is None or safe_path(page), 'unsafe_path')

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

@@ -14,10 +14,10 @@ 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.49.3"
+  version: "0.51.1"
   contract-version: "0.1.0"
   extension: "fabric-service/0.1"
-  extension-commit: "2f020a696453ae299b123517f14957f6a1354379"
+  extension-commit: "e6c4fc16b415eec3190dd34d924d269405359dc9"
 ---
 
 # Building Fabric services
@@ -70,9 +70,10 @@ Answer before writing code, and record the answers in the project README:
 | Caller | Surface | Why |
 |---|---|---|
 | Another agent on this machine | MCP `2026-07-28`, `streamable-http`, at `/mcp` on the service origin, token in a header | one process serves every session; stdio-per-session once left twenty stray servers on this machine |
-| The operator or a script | a CLI: `<tool> service status\|start\|stop\|restart`, `<tool> dashboard`, `<tool> doctor --json` | every verb delegates to launchd and the well-known document, never to its own process table |
+| The operator or a script | a CLI: `<tool> service status\|start\|stop\|restart`, `<tool> dashboard` (opens only in Fabric Dashboards, below), `<tool> doctor --json` | every verb delegates to launchd and the well-known document, never to its own process table |
 | A remote agent | A2A `1.0` over HTTPS, or MCP behind an authenticated gateway | loopback reachability is not authorization |
-| The dashboard page | same-origin REST under `/api`, session cookie plus a custom request header | the CSRF defence all four existing dashboards use |
+| An A2A peer on this computer | `surfaces.a2a` names a public Agent Card, served without the token; its interface URLs are loopback (DEC-0122); the kits read it, serving one is FAA-10 | the card carries no credential, process member or required Fabric extension |
+| The dashboard page | same-origin REST under `/api`, session cookie plus a custom request header; every button on it also a tool on the MCP surface (Step 5) | the CSRF defence all four existing dashboards use |
 
 Read [the surfaces and auth reference](references/surfaces-and-auth.md) when wiring
 MCP registration into a client config, the login flow or the CSRF header.
@@ -248,6 +249,16 @@ and declare it with `extensions=fs.dashboard_extension()`. Read
 declaration and how to upgrade a dashboard built before the kit: an upgrade you may make yourself,
 which the plugin's session-start notice offers in a repository that owns the service.
 
+**Every button has a tool** (`fabric-actions/0.1`, contract DEC-0121 AP-1). Each action the page lets a
+person take is a tool on the MCP surface with the same effect, checks, audit record and an idempotency key,
+registered with `server.add_tool(tool, handler, action={id, title, tool, gate})` (`gate` is `none`, `relayed`
+or `human` with its `humanStep`) and declared with `build_well_known(actions=server.action_table())` under
+`extensions/actions/0.1`. A `relayed` action called by the operator's own agent with their decision in
+`_meta.decision` is the operator's act: never answer it "operator session required" or send them to the page.
+A service adopts the relayed gate once Fabric's hub forwards decisions (CT-125), as the contract says; until then its tools
+answer as today. Read the interop reference's *Actions* section for when to adopt, the gate, its hooks and its
+refusals.
+
 **Say what the agent uses** (`fabric-connections/0.1`, DEC-0096) so Fabric Dashboards draws its chain: the other
 agents, models, connectors, stores and channels, each with its state, from
 `connections_extension()` / `connectionsExtension()` in `fabric_connections`. Never a credential in it, never a call
@@ -283,10 +294,15 @@ python3 <skill-dir>/scripts/check_service.py <id>[.<instance>]
 It reports `PASS`, `FAIL` or `NOT_RUN` per rule (descriptor, port claim, well-known
 shape, identity, latency, Host/Origin/cross-site guards, loopback bind, token file,
 events auth and shape, single-use login, state outside code, instance lock, plist,
-launchd pid equals answering pid, `dashboard.declared` (ED-9), and the `interop.*` rules:
+launchd pid equals answering pid, `dashboard.declared` (ED-9), `well-known.actions` (DEC-0121),
+`dashboard.actions-declared` (`NOT_RUN` when a dashboard declares no actions), `dashboard.opens-in-host` (no browser
+opener aimed at the service's pages in its checkout; `--repo PATH` names the checkout, and a service installed
+from a release folder needs it), and the `interop.*` rules:
 manifest link, capability list, tools equal to the manifest, job tools, unknown job, trace
-propagation, event trace pairs, and `board.responder` for a service that declares the project board) and exits 1 on
-any `FAIL`. A `NOT_RUN` is not a pass;
+propagation, event trace pairs, `interop.action-tools` (every declared action's tool is served), `well-known.a2a` and
+`a2a.card` (DEC-0122: the card is fetched without the token and its interfaces are never called; the surfaces
+reference's *A2A for remote agents* section), and
+`board.responder` for a service that declares the project board) and exits 1 on any `FAIL`. A `NOT_RUN` is not a pass;
 name it in the report. A service with a dashboard also runs the layout probe,
 `node <skill-dir>/scripts/check_dashboard_layout.mjs --service <id>` (WebKit at 360, 480, 768
 and 1280 px; needs Playwright, else `NOT_RUN` and exit 3: nothing was measured).
@@ -328,7 +344,8 @@ first commit:
 - an `AGENTS.md` that opens with the template's *Read first* block and closes with *After work*,
   and a `CLAUDE.md` whose first line is `@AGENTS.md`.
 
-org-index `scripts/check_format.py` reports 0 findings for it before it is called done. **An agent
+Whoever owns the repository, an agent with a page gets the dashboard rule block in its `AGENTS.md`
+(below). 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
 choice, nothing about it is published or listed by the organization, and none of these files is
 required of it, though the verified MCP quick start is still how anyone learns to drive it.
@@ -418,8 +435,29 @@ the probe table verbatim with every `NOT_RUN` explained; the lock and kill-9 res
 with pids; and the one next command. Never call a service conformant while the probe
 reports a `FAIL`.
 
-## Dashboard handoff: also for consumers
+## Agent pages open only in Fabric Dashboards
+
+The operator's rule (2026-10-24) for every page of an agent or a local Fabric service, in any host: a link in an
+answer or a notification, `<tool> dashboard`, a completion message, a page the agent opens itself.
+
+1. Resolve the exact registered service key (`id.instance`) with the `fabric-dashboards` MCP (`list_services`);
+   never guess it from a project name or a port.
+2. Hand over the `open_link` its `link` tool returns for the service and the page's path, as the primary action.
+3. To open it, use the host's `open` with `fallback=never`. Never `open <url>`, `open -a Safari`, `xdg-open`,
+   `start <url>`, `webbrowser.open` or `shell.openExternal` aimed at the service's pages.
+4. A browser only on a confirmed `not_installed` host (`host_status`); an installed host that failed to open is
+   reported, never replaced by HTTP.
+5. Links carry no token or login code: the host signs in.
+
+Run `scripts/check_dashboard_link.py` (from this skill's own directory; it is not copied into the project) on an
+action before it is printed or opened, and have the project's checks run it for every completion and notification
+renderer. The generated `AGENTS.md` carries the rule as its dashboard
+rule block; [dashboard links](references/dashboard-links.md) has the block, the gate's input and the remote case. The
+probe's `dashboard.opens-in-host` fails a tracked file that opens the dashboard with a browser opener. Headless agents
+need no dashboard.
+
+## An agent with a page and no service descriptor
 
-When handing a registered service dashboard to a person, or writing the generated agent's
-completion or notification instructions, read and apply [dashboard links](references/dashboard-links.md)
-and run its output gate before delivery, in any host. Headless agents need no dashboard.
+A local page no service descriptor names cannot open in Fabric Dashboards. Never open it in a browser instead:
+make the agent a `fabric-service/0.1` service (this skill: the descriptor, the well-known document, the login-code
+routes and a declared dashboard), and until that lands file a board row for it and say the page waits on it.

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

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.4 · Fabric's button (Fabric Agent Contract DEC-0040, FB-1…FB-8, FL-1…FL-6)
+/* fabric-dashboard-kit@1.1.5 · 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.4';
+  var VERSION = '1.1.5';
   var COOKIE = 'fabric_button';
   var GET_FABRIC = 'https://passioncode.ai/fabric';
   var ABSENT_AFTER_MS = 1500;
@@ -165,13 +165,14 @@
       absent: 'Fabric \u043d\u0435 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d. \u0421\u043a\u0430\u0447\u0430\u0439\u0442\u0435 \u0435\u0433\u043e \u043d\u0430' }
   };
 
-  /** The labels for a page language, each one replaced by a non-blank string the page gives (data-label-*). */
+  /** The labels for a page language, each one replaced by a non-blank string the page gives (data-label-*) that keeps
+      the word Fabric: the visible label stays inside the name and each item (DEC-0124, WCAG 2.2 SC 2.5.3). */
   function labelsFor(lang, overrides) {
     var base = LABELS[/^ru(-|$)/i.test(String(lang || '')) ? 'ru' : 'en'];
     var out = {};
     Object.keys(base).forEach(function (k) {
       var own = overrides ? overrides[k] : undefined;
-      out[k] = typeof own === 'string' && own.trim() ? own.trim() : base[k];
+      out[k] = typeof own === 'string' && own.trim() && own.indexOf('Fabric') >= 0 ? own.trim() : base[k];
     });
     return out;
   }

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

@@ -1,4 +1,4 @@
-/* fabric-dashboard-kit@1.1.4 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.5 · 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.4 · fabric-dashboard/0.1 (Fabric Agent Contract DEC-0036)
+/* fabric-dashboard-kit@1.1.5 · 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.4';
+  var VERSION = '1.1.5';
   /* fabric-dashboard-kit:theme-ids:begin */
   var THEMES = ['graphite', 'fabric', 'paper', 'forest', 'ocean', 'ember', 'contrast'];
 /* fabric-dashboard-kit:theme-ids:end */

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.4",
+  "version": "1.1.5",
   "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": "c9367aad04c662547aec61e67e10b99d80ec1d1c4618b4473bc2db882d80db94",
-    "fabric-dashboard.js": "5f157d185d9b04e9a11e680399503bbae924520ed0c112b734bf59fc8ee6bb49",
-    "fabric-button.js": "2906d3533635df2ed1f2f071abe00238d30ea81666ff34c3456b376526b66859",
+    "fabric-dashboard.css": "cc7a96fa2c5eeb03d113e7a543ed88d43ce78c2808c411de199ea0fc6d55b957",
+    "fabric-dashboard.js": "5df01193c590a1d8aa82a521954902fecf2d7f655df482165f90d7291b00087f",
+    "fabric-button.js": "e945b3252f9a246826d06dbe7bd4be66e82d539a33728c3d3043fd61d4cbd681",
     "themes.json": "511839f1a1a83eb37fadfd132791474497d5c28c5091700b9aa31ad076e359b5"
   },
   "history": {
@@ -49,6 +49,11 @@
       "fabric-dashboard.css": "c9367aad04c662547aec61e67e10b99d80ec1d1c4618b4473bc2db882d80db94",
       "fabric-dashboard.js": "5f157d185d9b04e9a11e680399503bbae924520ed0c112b734bf59fc8ee6bb49",
       "fabric-button.js": "2906d3533635df2ed1f2f071abe00238d30ea81666ff34c3456b376526b66859"
+    },
+    "1.1.5": {
+      "fabric-dashboard.css": "cc7a96fa2c5eeb03d113e7a543ed88d43ce78c2808c411de199ea0fc6d55b957",
+      "fabric-dashboard.js": "5df01193c590a1d8aa82a521954902fecf2d7f655df482165f90d7291b00087f",
+      "fabric-button.js": "e945b3252f9a246826d06dbe7bd4be66e82d539a33728c3d3043fd61d4cbd681"
     }
   }
 }

package/plugins/fabric-agent-adapter/skills/building-fabric-services/recipes/support-agent/README.md

@@ -101,7 +101,9 @@ version is still read and never written; delete it once its messages are past th
 - Replace the example knowledge with the product's own, and run real past questions through it ([practices](../../../creating-fabric-agents/references/practices.md#judges-and-evals), *Judges
   and evals*): count handoffs and read a sample of replies.
 - Show spend: `fabric_usage.usage_report` over the ledger, or `fabric_openrouter.totals`.
-- One decision per message id holds in one process; a service runs one instance per context under its instance lock.
-  Each process reads `decisions.jsonl` once and keeps the index in memory, so a second process writing the same
-  state folder is not seen.
+- One decision per message id holds in one process. Each process reads `decisions.jsonl` once and keeps the index in
+  memory, so a second process writing the same state folder is not seen: a service runs one instance per context with
+  `fabric_context.hold_context_instance` (Node: `holdContextInstance`) and points `stateDir` at that instance's data
+  folder, so a second copy for the same context exits 75 and an organization's copy keeps its own folder
+  ([one instance per context](../../references/estate-record.md#one-instance-per-context-the-helper)).
 - Set the outbox's retention and schedule `prune`.