@mfdaves/okf-mcp 0.3.3 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (40) hide show
  1. package/.agents/skills/okf-v02-migration/SKILL.md +37 -0
  2. package/.agents/skills/okf-v02-migration/agents/openai.yaml +6 -0
  3. package/.agents/skills/okf-v02-migration/references/field-mapping.md +26 -0
  4. package/README.md +192 -78
  5. package/okf/bundles/okf-mcp/distribution/reference-bundle.md +2 -2
  6. package/okf/bundles/okf-mcp/index.md +7 -0
  7. package/okf/bundles/okf-mcp/interfaces/http-authoring-api.md +2 -2
  8. package/okf/bundles/okf-mcp/interfaces/mcp-tools.md +8 -4
  9. package/okf/bundles/okf-mcp/overview/okf-mcp.md +2 -2
  10. package/okf/bundles/okf-mcp/policies/authoring-safety.md +5 -3
  11. package/okf/bundles/okf-mcp/runtime/file-concept-store.md +7 -5
  12. package/okf/bundles/okf-mcp/runtime/indexer.md +6 -4
  13. package/okf/bundles/okf-mcp/runtime/mcp-server.md +6 -6
  14. package/okf/bundles/okf-mcp/specs/attested-computation.md +24 -0
  15. package/okf/bundles/okf-mcp/specs/concept-format.md +5 -3
  16. package/okf/bundles/okf-mcp/specs/git-sources.md +23 -0
  17. package/okf/bundles/okf-mcp/workflows/v02-migration.md +24 -0
  18. package/package.json +9 -3
  19. package/server.json +5 -5
  20. package/src/assets.js +469 -0
  21. package/src/authoring.js +492 -20
  22. package/src/cli.js +467 -37
  23. package/src/computation.js +366 -0
  24. package/src/git-source.js +551 -0
  25. package/src/graph.js +71 -18
  26. package/src/http-server.js +8 -1
  27. package/src/index.js +5 -0
  28. package/src/indexer.js +428 -24
  29. package/src/markdown.js +129 -0
  30. package/src/mcp-server.js +447 -313
  31. package/src/migration.js +687 -0
  32. package/src/parser.js +135 -54
  33. package/src/plugins.js +30 -50
  34. package/src/project.js +74 -17
  35. package/src/remote.js +232 -17
  36. package/src/search.js +69 -6
  37. package/src/store.js +421 -25
  38. package/src/v02.js +545 -0
  39. package/src/validation.js +13 -2
  40. package/src/mcp-protocol.js +0 -283
@@ -23,16 +23,20 @@ relations:
23
23
 
24
24
  The MCP interface groups tools by intent.
25
25
 
26
- Discovery tools list bundles, concepts, types, tags, relation types, and loaded remote bundles. `get_concept` returns the complete frontmatter and Markdown body for one concept. `search_concepts` combines text ranking with structured filters.
26
+ Discovery tools list bundles, concepts, types, tags, custom relation types, standard edge kinds, and loaded remote bundles. `get_concept` accepts a portable Concept ID or compatibility locator and returns raw frontmatter and body plus normalized v0.2 signals, referenced-asset metadata, and declared Git-source availability. Search filters lifecycle, trust, freshness at a deterministic date, source presence, generator or verifier actors, runtime, and static attestation readiness.
27
27
 
28
- Graph tools return bounded graphs, neighbors, subgraphs, paths, summaries, and rendered exports. Canonical and path-derived concept URIs are accepted for direct graph traversal.
28
+ Graph tools return bounded graphs, neighbors, subgraphs, paths, summaries, provenance traces, and rendered exports. They can filter semantic edge kinds and optionally include inert asset nodes or unfetched external leaves. Extensionless canonical, `.md`, and custom-id aliases are accepted for lookup.
29
29
 
30
30
  Validation tools inspect bundles, projects, and candidate concepts without writing. They report OKF conformance separately from project validity. Remote loading fetches a public GitHub tree into the in-memory index.
31
31
 
32
- Project mode exposes read-only candidate validation, path suggestion, and proposal inspection helpers. Proposal creation, acceptance, and rejection additionally require `--authoring`. Runtime calls to `load_remote_bundle` require `--allow-remote-tool`; configured remote bundles remain readable without that flag.
32
+ Static computation tools inspect contracts, read indexed assets, prepare parameter digests, and check receipt field names without execution, attestation, value echo, or persistence. Migration tools check or preview Stage A without writes.
33
+
34
+ `read_git_source` reads one pinned `sources[].git` entry from a checkout or bare repository explicitly mapped by the MCP host. It reads the Git object database rather than the working tree and never fetches.
35
+
36
+ An explicit local root or project workspace exposes candidate validation, path suggestion, and proposal inspection. Normal proposal mutations require `--authoring`; the coordinated computation proposal additionally requires `--allow-computation-authoring`. Runtime calls to `load_remote_bundle` require `--allow-remote-tool`.
33
37
 
34
38
  Every tool supplies a purpose-specific description, descriptions for all input parameters, and MCP annotations for read behavior, destructive behavior, idempotency, and external access. Tool discovery and direct invocation use the same capability checks, so a hidden tool also fails when called by name. Annotations remain hints to clients; server-side validation is authoritative.
35
39
 
36
- Tool arguments are validated against the advertised schema without coercion. Unknown or disabled tools and malformed call envelopes are protocol errors. Once a known enabled tool receives a structurally valid call, expected validation, storage, network, read-only, and proposal-conflict failures are returned as tool results with `isError: true`. A validation operation that successfully reports invalid OKF remains a successful tool result.
40
+ The official MCP SDK validates tool arguments against the advertised schema without coercion. Unknown or disabled tools are rejected by SDK dispatch. Argument-schema failures and expected validation, storage, network, read-only, and proposal-conflict failures from enabled tools are returned as tool results with `isError: true`. A validation operation that successfully reports invalid OKF remains a successful tool result.
37
41
 
38
42
  `list_concepts` applies its optional text query together with its structured filters. Relation-type filtering selects concepts with an outgoing relation of the requested type.
@@ -19,9 +19,9 @@ relations:
19
19
 
20
20
  # okf-mcp
21
21
 
22
- `okf-mcp` turns directories of OKF Markdown concepts into a searchable in-memory knowledge graph. It provides a command-line interface, a JSON-RPC stdio MCP server, generator plugins, remote GitHub bundles, and an optional HTTP authoring API.
22
+ `okf-mcp` turns one OKF v0.2 root and its explicitly referenced inert assets into a searchable in-memory knowledge graph. It provides a CLI, SDK-backed stdio MCP server, pinned Git-source reads, optional workspace federation, generator plugins, remote GitHub bundles, and an HTTP authoring API.
23
23
 
24
- The runtime uses `js-yaml` for standards-oriented YAML parsing and has no database, embedding service, or build step. Local bundle mode performs no network calls. Project mode adds configuration, typed relations, proposal storage, and guarded writes to local bundle directories.
24
+ The runtime uses `js-yaml` and CommonMark and has no database, embedding service, computation executor, attester runtime, or build step. `--root` is the normal single-catalog interface and performs no network calls. The optional project manifest federates multiple roots and generator configuration; it is an okf-mcp extension rather than part of OKF v0.2.
25
25
 
26
26
  The primary runtime entry is the [MCP stdio server](../runtime/mcp-server.md). Concept interpretation and graph construction belong to the [indexer](../runtime/indexer.md). Durable knowledge changes follow the [concept authoring workflow](../workflows/concept-authoring.md) and [authoring safety policy](../policies/authoring-safety.md).
27
27
 
@@ -23,16 +23,18 @@ relations:
23
23
 
24
24
  # Authoring Safety
25
25
 
26
- Authoring is allowed only for local bundles declared by `okf.project.yaml`. MCP proposal mutations additionally require the explicit `--authoring` capability. Remote bundles are read only.
26
+ Authoring is allowed for an explicit local `--root` or local roots declared by `okf.project.yaml`. MCP proposal mutations require `--authoring`; coordinated computation proposals also require `--allow-computation-authoring`. Remote roots are read only.
27
27
 
28
28
  Concept paths must be safe relative `.md` paths inside the selected bundle. Absolute paths, parent traversal, reserved `index.md` and `log.md` targets, symbolic-link traversal, and non-directory parents are rejected.
29
29
 
30
- New concepts cannot reuse an existing path URI or stable id. Updates are bound to the existing bundle, path, path URI, and canonical identity. Updating a concept cannot rename its stable URI.
30
+ New concepts cannot reuse a canonical Concept ID or compatibility alias. Updates are bound to the existing bundle and path and cannot change the custom-id alias.
31
31
 
32
32
  Candidates must satisfy the concept format, configured relation vocabulary, and internal target integrity. External schemes such as `repo://` are allowed as opaque references.
33
33
 
34
34
  Proposal creation never writes a concept file. Acceptance repeats validation. Updates also compare the source revision immediately before replacement and return conflicts for detected concurrent changes. After acceptance, the MCP index is rebuilt without discarding configured or runtime-loaded remote bundle state.
35
35
 
36
+ Computation, executor, and attester artifacts are always inert. Inspection and preflight never execute them, fetch external contract URIs, echo parameter or receipt values, persist receipts, or claim attestation. Migration adds no unverifiable provenance or trust claims and never accepts its own proposals.
37
+
36
38
  HTTP mutations require bearer authorization. Filesystem safeguards still apply after authentication.
37
39
 
38
- The local file store is designed for one trusted project workspace. Multiple independent authoring workers require an external coordination or locking strategy.
40
+ The local file store is designed for one trusted root or project workspace. Multiple independent authoring workers require an external coordination or locking strategy.
@@ -2,7 +2,7 @@
2
2
  id: okf://okf-mcp/runtime/file-concept-store
3
3
  type: OKF Runtime Component
4
4
  title: File Concept Store
5
- description: Local proposal and concept persistence boundary used by project authoring.
5
+ description: Local proposal and concept persistence boundary used by root and project authoring.
6
6
  tags: [storage, proposals, authoring, filesystem]
7
7
  relations:
8
8
  - type: consumes
@@ -19,12 +19,14 @@ relations:
19
19
 
20
20
  # File Concept Store
21
21
 
22
- The file concept store is the persistence boundary for project-mode authoring. Proposal records are JSON files under `.okf-proposals` by default. Concept files remain ordinary Markdown inside configured local bundles.
22
+ The file concept store is the persistence boundary for root- and project-mode authoring. Proposal records are JSON files under `.okf-proposals` by default. Concept files remain ordinary Markdown inside the selected local root.
23
23
 
24
24
  Proposal states are `proposed`, `accepted`, and `rejected`. Creating or updating a proposal writes only the proposal record. Acceptance revalidates the candidate before changing a concept file.
25
25
 
26
- New concepts use exclusive creation. Updates retain a SHA256 revision of the source content and check it again immediately before atomic replacement. Detected concurrent changes return a conflict and preserve the current file.
26
+ New concepts use exclusive creation. Updates retain a SHA256 revision and check it immediately before atomic replacement. Gated Attested Computation proposals stage the concept plus an optional external computation file and conflict-check every target before acceptance.
27
27
 
28
- Write paths are normalized relative Markdown paths. Reserved files are rejected, bundle boundaries are enforced, and symbolic-link traversal is blocked. Update proposals are also bound to the original bundle, path, and stable concept identity.
28
+ The store rolls back published files when an ordinary acceptance call fails, but a multi-file acceptance is not crash-transactional across process or power loss. Operators must inspect and repair an interrupted acceptance before restarting authoring; the store does not claim database transaction semantics.
29
29
 
30
- This is a local file-backed store intended for a trusted project workspace. It is not a distributed transaction system or multi-writer database. Its invariants are defined by the [authoring safety policy](../policies/authoring-safety.md).
30
+ Write paths remain bundle-relative, bundle boundaries are enforced, and symbolic-link traversal is blocked. Generic tools cannot alter computation contracts. Migration manifests live under `.okf-proposals/migrations`; their child proposals are never auto-accepted, and the reserved version proposal depends on accepted Stage-A children.
31
+
32
+ This is a local file-backed store intended for a trusted root or project workspace. It is not a distributed transaction system or multi-writer database. Its invariants are defined by the [authoring safety policy](../policies/authoring-safety.md).
@@ -23,15 +23,17 @@ relations:
23
23
 
24
24
  # OKF Indexer
25
25
 
26
- The indexer loads configured bundle directories, applies include and exclude filters, parses Markdown documents with the safe YAML core schema, and builds a bounded in-memory graph. It keeps separate collections for all documents, valid concepts, reserved resources, edges, warnings, and errors.
26
+ The indexer normally loads one OKF root, validates UTF-8, parses YAML with the safe core schema, parses body structure with CommonMark, and builds an in-memory graph. Its optional workspace mode can load several roots with include and exclude filters. It keeps separate collections for documents, concepts, reserved resources, explicitly referenced assets, edges, warnings, and errors.
27
27
 
28
- Both canonical ids and path-derived URIs resolve through the URI map. Graph operations normalize path aliases to canonical ids before traversal.
28
+ Portable identities are extensionless path-derived Concept IDs. `.md`, custom-id, and workspace-scoped `okf://` locators resolve through compatibility maps; ambiguous bare IDs require a scoped locator.
29
29
 
30
- Markdown links become `markdown_link` edges. Frontmatter relations become typed `relation` edges. Internal targets are validated, while non-OKF schemes are recorded as external references.
30
+ Markdown links and extension relations remain `markdown_link` and `relation` edges. Standard v0.2 fields add `resource`, `source`, `computation`, `executor`, and `attester` edges. Safe bundle-local artifacts are registered only when explicitly referenced, with byte limits, symlink rejection, MIME classification, and SHA256; content is never executed.
31
31
 
32
32
  Markdown targets resolve to an exact document first. When no exact document exists, a directory link resolves to that directory's reserved `index.md`. This rule is shared by local indexing, remote indexing, and authoring candidate validation, so the resulting edge uses the nested index document's canonical URI.
33
33
 
34
- Validation is layered. OKF conformance checks parseable mapping frontmatter, a non-empty concept `type`, and the reserved structures of `index.md` and `log.md`. Unknown fields and unknown type values remain conformant. Project validity additionally covers missing roots, invalid paths, duplicate bundle ids, duplicate concept URIs, unsupported relation types, broken Markdown links, and broken internal targets.
34
+ Validation is layered. OKF conformance checks UTF-8, parseable mapping frontmatter, a non-empty string `type`, and reserved structures. Optional v0.2 family problems are advisories. Project validity covers path and identity integrity, relation vocabulary, and internal targets; broken Markdown links invalidate only under `strictLinks`.
35
+
36
+ Remote loading is two-pass: selected Markdown is parsed first, then only referenced local assets are fetched. Revision and blob metadata, digests, counts, and unresolved references remain attached to the read-only bundle.
35
37
 
36
38
  Results expose `conformant`, `validForProject`, and structured diagnostics. `valid` is a compatibility alias for `validForProject`. Valid concepts continue to be served even when other files produce diagnostics.
37
39
 
@@ -13,25 +13,25 @@ relations:
13
13
  target: okf://okf-mcp/workflows/concept-authoring
14
14
  - type: configured_by
15
15
  target: repo://src/mcp-server.js
16
- - type: configured_by
17
- target: repo://src/mcp-protocol.js
18
16
  - type: checked_by
19
17
  target: repo://test/okf-mcp.test.js
20
18
  - type: checked_by
21
19
  target: repo://test/mcp-hardening.test.js
20
+ - type: checked_by
21
+ target: repo://test/mcp-sdk.test.js
22
22
  ---
23
23
 
24
24
  # MCP Stdio Server
25
25
 
26
- The MCP server reads newline-delimited JSON-RPC messages from stdin and writes responses to stdout. It implements initialization, ping, resource listing and reading, tool listing, and tool calls without an SDK dependency.
26
+ The MCP server exposes OKF resources and tools over stdio through the official `@modelcontextprotocol/server` v2 SDK. The application adapter registers the existing schemas and handlers; the SDK owns framing, negotiation, validation, and dispatch.
27
27
 
28
- The server supports protocol versions `2025-11-25`, `2025-06-18`, `2025-03-26`, and `2024-11-05`. Initialization returns a requested supported version. A well-formed unsupported version negotiates to the preferred supported version, `2025-11-25`, so the client can decide whether to continue. Missing or malformed initialization parameters remain invalid.
28
+ The SDK serves the modern `2026-07-28` revision and its compatibility path for 2025-era clients, including `2025-11-25`. Both paths expose the same OKF resources, enabled tools, schemas, and application behavior.
29
29
 
30
- The transport validates the JSON-RPC envelope before dispatch. Parse errors, invalid requests, unknown methods, invalid method parameters, missing resources, and internal failures use their corresponding protocol error classes. Valid notifications never receive responses, including notifications with unknown methods or failing handlers. Stdout is reserved for protocol messages.
30
+ The SDK validates protocol messages and tool arguments before application dispatch. Expected application failures return tool results with `isError: true`; unexpected implementation failures are masked. Stdout remains reserved for protocol messages.
31
31
 
32
32
  Each indexed Markdown document is exposed as a `text/markdown` resource. The [MCP tool catalog](../interfaces/mcp-tools.md) exposes discovery, search, graph navigation, validation, remote loading, and proposal-based authoring.
33
33
 
34
- Bundle mode is read oriented. Project mode loads `okf.project.yaml`, enables configured relation types, and supplies the store required by the [authoring workflow](../workflows/concept-authoring.md). Proposal mutation tools remain disabled unless the server starts with `--authoring`. Runtime remote loading remains disabled unless it starts with `--allow-remote-tool`.
34
+ Root mode is the normal single-catalog interface and can supply the local store used by the [authoring workflow](../workflows/concept-authoring.md). Project mode remains an optional federation/configuration extension. Proposal mutation tools remain disabled unless the server starts with `--authoring`; runtime remote loading remains disabled unless it starts with `--allow-remote-tool`.
35
35
 
36
36
  Remote GitHub bundles are fetched as Markdown and added to the in-memory index. They remain read only and never execute remote code. After an accepted local proposal, one reconstruction path rebuilds the index from configured local bundles, configured remote bundles, and runtime-loaded remote bundles, preserving remote concepts and relationships.
37
37
 
@@ -0,0 +1,24 @@
1
+ ---
2
+ id: okf://okf-mcp/specs/attested-computation
3
+ type: OKF Data Contract
4
+ title: Attested Computation Support
5
+ description: Static OKF v0.2 computation contract interpretation and non-execution boundary.
6
+ tags: [okf, computation, attestation, safety]
7
+ relations:
8
+ - type: depends_on
9
+ target: okf://okf-mcp/specs/concept-format
10
+ - type: configured_by
11
+ target: repo://src/v02.js
12
+ - type: configured_by
13
+ target: repo://src/computation.js
14
+ - type: checked_by
15
+ target: repo://test/v02-integration.test.js
16
+ ---
17
+
18
+ # Attested Computation Support
19
+
20
+ An Attested Computation declares a runtime, typed parameters, exactly one inline or file computation, an executor resource with expected receipt fields, and an attester resource. Structural readiness is separate from resolution of bundle-local artifacts, lifecycle freshness, and verification trust.
21
+
22
+ The runtime can inspect this contract, hash the sanctioned computation, check declared parameter names, and compare receipt field names. Parameter and receipt values are not returned or persisted.
23
+
24
+ No tool executes the computation, executor, or attester. External resources are not fetched on demand. Execution and actual attestation remain unsupported until a separately allowlisted adapter, sandbox, ABI, cost, credential, and receipt policy exists.
@@ -19,14 +19,16 @@ relations:
19
19
 
20
20
  # OKF Concept Format
21
21
 
22
- An OKF concept is a Markdown file with YAML frontmatter. A non-empty `type` is required. `title`, `description`, `tags`, `aliases`, and typed `relations` provide structured metadata, while the Markdown body carries the durable explanation.
22
+ An OKF concept is a UTF-8 Markdown file with YAML frontmatter. A non-empty string `type` is required. Standard v0.2 metadata families include `resource`, `sources`, `usage_window`, `generated`, `verified`, `status`, `stale_after`, and the Attested Computation contract. The Markdown body carries the durable explanation.
23
23
 
24
- The optional `id` field defines a stable `okf://` URI. Without it, the URI is derived from the bundle id and relative file path. A stable id is preferred for public concepts because it survives file moves. The path-derived URI remains an alias in the index.
24
+ The standard Concept ID is the bundle-relative path with `.md` removed. okf-mcp also creates the workspace-scoped locator `okf://<bundle>/<concept-id>` for MCP resources and federated lookup; it is not the portable OKF identity. The former `.md` URI remains a compatibility alias. The optional `id`, `aliases`, and typed `relations` fields are `okf-mcp` extensions; a valid custom `id` is an additional alias rather than a replacement for the standard identity.
25
25
 
26
26
  Frontmatter is parsed as a YAML mapping with the safe core schema. Nested mappings, arrays, block scalars, and unknown extension keys are preserved. Duplicate mapping keys and unsupported custom tags are rejected. Unknown concept type values do not fail OKF conformance.
27
27
 
28
28
  Files named `index.md` and `log.md` are reserved resources and are not concepts. Reserved indexes group local Markdown links under headings. A link to a bundle directory resolves to that directory's nested `index.md` when no exact document target exists. Reserved logs use an H1 title followed by newest-first ISO-dated H2 sections containing list entries.
29
29
 
30
- Internal `okf://` relation targets and Markdown links are checked as project rules rather than redefining minimum document conformance. Other schemes such as `repo://` are retained as opaque external references.
30
+ Consumers normalize bare `verified` mappings into one event and derive exactly `unverified`, `machine-confirmed`, or `human-reviewed`. Missing status defaults to `stable`; freshness is evaluated deterministically against `stale_after`. Malformed optional families produce advisories and fail trust closed without invalidating minimum conformance.
31
+
32
+ Internal paths, compatibility `okf://` targets, and Markdown links are checked as project rules rather than redefining minimum document conformance. Broken Markdown links are advisory unless `strictLinks` is enabled. CommonMark parsing excludes images and code fences from relationship extraction.
31
33
 
32
34
  The [indexer](../runtime/indexer.md) validates this contract. Accepted proposals are rendered back into this format by the [file concept store](../runtime/file-concept-store.md).
@@ -0,0 +1,23 @@
1
+ ---
2
+ type: OKF Extension Contract
3
+ title: Pinned Git Sources
4
+ description: Host-agnostic source metadata and bounded local Git-object reads for code knowledge stored outside its source repository.
5
+ tags: [okf, git, provenance, source, security]
6
+ relations:
7
+ - type: related_to
8
+ target: /specs/concept-format.md
9
+ - type: configured_by
10
+ target: repo://src/git-source.js
11
+ - type: checked_by
12
+ target: repo://test/git-source.test.js
13
+ ---
14
+
15
+ # Pinned Git Sources
16
+
17
+ A standard `sources` entry may point at a bundle-local concept of type `Git Repository` and carry a `git` extension with a full commit revision, repository-relative POSIX path, and optional inclusive `lines: { from, to }` range.
18
+
19
+ The OKF content contains the repository's transport URL but never a machine-local checkout path or credential. The MCP host maps the repository Concept ID to an explicit checkout, bare repository, or mounted object store with `--repo <concept-id>=<path>`.
20
+
21
+ `read_git_source` resolves only declared source entries. It reads a regular blob from the pinned commit, verifies its Git object ID and SHA-256, enforces UTF-8 and byte limits, and rejects traversal, symbolic links, and submodules. It disables lazy fetches and never consults dirty working-tree bytes.
22
+
23
+ An unpinned source or missing host mapping remains discoverable but unavailable. No indexing, search, graph, or provenance operation triggers Git network access.
@@ -0,0 +1,24 @@
1
+ ---
2
+ id: okf://okf-mcp/workflows/v02-migration
3
+ type: OKF Workflow
4
+ title: OKF v0.2 Migration
5
+ description: Review-only compatibility migration for existing v0.1 and mixed knowledge catalogs.
6
+ tags: [okf, migration, proposals, compatibility]
7
+ relations:
8
+ - type: depends_on
9
+ target: okf://okf-mcp/runtime/file-concept-store
10
+ - type: checked_by
11
+ target: okf://okf-mcp/policies/authoring-safety
12
+ - type: configured_by
13
+ target: repo://src/migration.js
14
+ - type: checked_by
15
+ target: repo://test/migration.test.js
16
+ ---
17
+
18
+ # OKF v0.2 Migration
19
+
20
+ The read-only checker classifies a bundle as v0.1, mixed, v0.2, undeclared, or blocked. It inventories legacy timestamps and citations, truthful actor-mapping needs, generated files, identity collisions, referenced assets, and version-declaration readiness.
21
+
22
+ The migration adds native fields without removing legacy content. A timestamp becomes `generated.at` only with a confirmed truthful `generated.by`; unambiguous citations become minimal `sources`. Native fields win and generated files are changed at their generator. A manifest and per-file proposals require review and explicit acceptance.
23
+
24
+ The root version proposal depends on accepted child proposals and complete catalog validation.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mfdaves/okf-mcp",
3
- "version": "0.3.3",
3
+ "version": "0.5.0",
4
4
  "description": "Local-first Open Knowledge Format validator, graph index, CLI, and MCP stdio server.",
5
5
  "homepage": "https://github.com/mfdaves/okf-mcp#readme",
6
6
  "repository": {
@@ -20,7 +20,7 @@
20
20
  "scripts": {
21
21
  "test": "node --test",
22
22
  "check": "node --test",
23
- "self:validate": "node bin/okf-mcp.js --project okf.project.yaml validate",
23
+ "self:validate": "node bin/okf-mcp.js --root okf/bundles/okf-mcp validate",
24
24
  "pack:check": "npm pack --dry-run",
25
25
  "package:smoke": "node scripts/package-smoke.js",
26
26
  "prepublishOnly": "npm run check && npm run self:validate",
@@ -39,6 +39,7 @@
39
39
  "files": [
40
40
  "bin",
41
41
  "src",
42
+ ".agents",
42
43
  "okf",
43
44
  "okf.project.yaml",
44
45
  "server.json",
@@ -52,6 +53,11 @@
52
53
  "access": "public"
53
54
  },
54
55
  "dependencies": {
55
- "js-yaml": "^5.2.1"
56
+ "@modelcontextprotocol/server": "2.0.0",
57
+ "commonmark": "^0.31.2",
58
+ "js-yaml": "^5.2.3"
59
+ },
60
+ "devDependencies": {
61
+ "@modelcontextprotocol/client": "2.0.0"
56
62
  }
57
63
  }
package/server.json CHANGED
@@ -8,23 +8,23 @@
8
8
  "source": "github"
9
9
  },
10
10
  "websiteUrl": "https://github.com/mfdaves/okf-mcp#readme",
11
- "version": "0.3.3",
11
+ "version": "0.5.0",
12
12
  "packages": [
13
13
  {
14
14
  "registryType": "npm",
15
15
  "identifier": "@mfdaves/okf-mcp",
16
- "version": "0.3.3",
16
+ "version": "0.5.0",
17
17
  "transport": {
18
18
  "type": "stdio"
19
19
  },
20
20
  "packageArguments": [
21
21
  {
22
22
  "type": "named",
23
- "name": "--project",
24
- "description": "Absolute path to the OKF project configuration.",
23
+ "name": "--root",
24
+ "description": "Absolute path to one OKF bundle root.",
25
25
  "isRequired": true,
26
26
  "format": "filepath",
27
- "placeholder": "/absolute/path/to/okf.project.yaml"
27
+ "placeholder": "/absolute/path/to/okf-root"
28
28
  },
29
29
  {
30
30
  "type": "positional",