- CONN-PULSELINK-MCP-CONNECTOR-CONTENT2
- Requirementsall slices in all specs2
- Requirements not donenot VERIFIED1
- Specs not donewhole specs only1
Each spec shows its requirement count. Panel J lists every record.
Requirements (2)
Specs (1)
Each bar shows one state against all records of the same kind.
Percentages count current rows. Done means VERIFIED.
| State | Definition |
|---|---|
| SPECIFIED | The requirement is written. No code for it is on the default branch. |
| LANDED | A commit that carries its ID in a Spec trailer is on the default branch. |
| VERIFIED | It is LANDED and a test bound to its ID exists. |
A spec state is the lowest state of its rows. Done means VERIFIED.
Invalid state: 0
| Spec / title | Req. | Landed | Done | Spec state | Code references |
|---|---|---|---|---|---|
| CONN-PULSELINK-MCP-CONNECTOR-CONTENTCONN-PULSELINK-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | 2 | 1/2 | 1 | SPECIFIED | pulselink_mcp/__init__.py:67 implementation: file exists; coverage not verified pulselink_mcp/mcp_server.py implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified tests/test_default_content_surfaces.py test: file exists; coverage not verified ../../pulselink_mcp/__init__.py implementation: file exists; coverage not verified |
Landed counts LANDED and VERIFIED requirements. Done counts VERIFIED requirements only.
The spec state comes from the spec status file only.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/pulselink-mcp / pulselink-mcp connector (1)
CONN-PULSELINK-MCP-CONNECTOR-CONTENT: no plan diagram declared.
Depends on means a declared prerequisite. Extends and references do not imply prerequisite order. Shared code never creates dependencies. External targets are source declarations, not verified delivery.
Knuckles-Team/pulselink-mcp / pulselink-mcp connector
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-PULSELINK-MCP-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
Issues
1 open at capture.
- #38 Nightly Connector failing updated 2026-11-16T15:27:16Z
Pull Requests
0 open at capture.
The build reads GitHub one time. This page makes no live API requests.
Each status file gives one spec row. Each requirement gives one more row. A record without a valid state shows INVALID. Expand a Definition to read the canonical requirement and verification text.
All documented records (3 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-PULSELINK-MCP-CONNECTOR-CONTENT CONN-PULSELINK-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-PULSELINK-MCP-CONNECTOR-CONTENT-R001 Default content Definition — CONN-PULSELINK-MCP-CONNECTOR-CONTENT / CONN-PULSELINK-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `pulselink-mcp` as the single `scion_sdk.connector` entry point. The server lists the packaged `skill://` and `ontology://` resources and the packaged prompts with no `content=` argument. Caller chain: `pulselink-mcp` in `pyproject.toml` runs `pulselink_mcp.mcp_server:mcp_server`, which builds the server from the `scion_sdk.connector` entry point `pulselink_mcp:connector` (`pulselink_mcp/__init__.py:67`); the SDK `Connector` then lists the packaged skills, ontology and prompts. Shape: `pyproject.toml` entry point `pulselink-mcp` plus the `connector = Connector(.)` object in `pulselink_mcp/__init__.py`; the packaged `skills/`, `ontology/` and `prompts/` directories of `pulselink_mcp` are reused as is, with no connector-local registration code. Proving test: `tests/test_default_content_surfaces.py::test_default_content_surfaces`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. | requirement | CONN-PULSELINK-MCP-CONNECTOR-CONTENT | VERIFIED | 68fba8789df6 944db9eb4da7 tests/test_default_content_surfaces.py:15 |
| CONN-PULSELINK-MCP-CONNECTOR-CONTENT-R002 Register the offline bookmark reader Definition — CONN-PULSELINK-MCP-CONNECTOR-CONTENT / CONN-PULSELINK-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Register the offline bookmark reader.** Subsystem: connector. Caller: process start → `pulselink_mcp/mcp_server.py` → `scion_sdk.adapters.bookmark_source.register_bookmark_tool(server, BookmarkReader(root=..))`. Config key `PULSELINK_BOOKMARK_ROOT` names the authorized directory; no default, and a missing key skips registration. Refusals: reuse SCION-SOURCE-INGEST-R005.10. Writes: none. Depends on: SCION-SOURCE-INGEST-R005.9. Caller chain: process start runs `pulselink_mcp/mcp_server.py`, which calls `register_bookmark_tool(server, BookmarkReader(root=..))` from `scion_sdk.adapters.bookmark_source` when `PULSELINK_BOOKMARK_ROOT` is set. Shape: one registration call in `pulselink_mcp/mcp_server.py` guarded by the `PULSELINK_BOOKMARK_ROOT` setting; reuses the SDK `BookmarkReader` and its refusal codes. Proving test (planned): `tests/test_bookmark_tool_served.py::test_tool_reads_authorized_root_only`. | Test: `tests/test_bookmark_tool_served.py::test_tool_reads_authorized_root_only` (L3) calls the tool for a file inside and a path outside the root. | requirement | CONN-PULSELINK-MCP-CONNECTOR-CONTENT | SPECIFIED | No recorded commit/test evidence |