wiki-graph 0.6.0 → 0.7.1

package/dist/data/help/commands/predicate.jinja

@@ -314,12 +314,42 @@ Notes:
 {% elif "/wikispine" in uri %}
 Schema:
   {
-    "provider": "fetch|cli"
+    "provider": "fetch|cli",
+    "endpoint": "<optional-service-base-url>"
   }
 
 Notes:
-  - `fetch` uses the built-in WikiSpine service endpoint.
+  - Allowed keys: provider, endpoint, token.
+  - `fetch` uses the hosted WikiSpine endpoint by default and requires its Bearer API key.
   - `cli` runs the local `wikispine` command from PATH.
+  - `token` is sensitive and cannot be set from JSON.
+  - To add or replace it, use `{{ commandName }} {{ uri }} put token --secret`.
+  - To remove it, use `{{ commandName }} {{ uri }} delete token`.
+{% elif "/wikimedia" in uri %}
+Schema:
+  {
+    "endpoint": "<optional-service-base-url>"
+  }
+
+Notes:
+  - Allowed keys: endpoint, token.
+  - An empty section uses direct local Wikimedia access. Setting `token` enables the hosted resolver; `endpoint` is optional.
+  - Remote access requires `token`; `endpoint` alone is incomplete.
+  - `pnpm dev` defaults to `https://pdf-craft-api.oomol.dev`; built CLI artifacts default to `https://api.pdfcraft.ai`.
+  - `token` is sensitive and cannot be set from JSON.
+  - To add or replace it, use `{{ commandName }} {{ uri }} put token --secret`.
+  - To remove it, use `{{ commandName }} {{ uri }} delete token`.
+{% elif "/job" in uri %}
+Schema:
+  {
+    "endpoint": "<service-base-url>"
+  }
+
+Notes:
+  - Allowed keys: endpoint, token.
+  - `token` is optional and sensitive; it cannot be set from JSON.
+  - To add or replace it, use `{{ commandName }} {{ uri }} put token --secret`.
+  - To remove it, use `{{ commandName }} {{ uri }} delete token`.
 {% elif "/concurrent" in uri %}
 Schema:
   {
@@ -344,6 +374,9 @@ Examples:
 {% elif "/wikispine" in uri %}
   {{ commandName }} {{ uri }} set '{"provider":"fetch"}'
   {{ commandName }} {{ uri }} set '{"provider":"cli"}'
+{% elif "/job" in uri or "/wikimedia" in uri %}
+  {{ commandName }} {{ uri }} set '{"endpoint":"https://service.example.com"}'
+  {{ commandName }} {{ uri }} put token --secret
 {% elif "/concurrent" in uri %}
   {{ commandName }} {{ uri }} set '{"job":3,"request":6}'
   {{ commandName }} {{ uri }} set --json-input '{"job":2,"request":4}'

package/dist/data/help/commands/uri.jinja

@@ -326,6 +326,7 @@ Sections:
   - `{{ commandName }} wikg://local/config/llm --help`
   - `{{ commandName }} wikg://local/config/embeddings --help`
   - `{{ commandName }} wikg://local/config/concurrent --help`
+  - `{{ commandName }} wikg://local/config/wikimedia --help`
   - `{{ commandName }} wikg://local/config/wikispine --help`
 {% elif target.name == "local-config-section" %}
 URI type:

package/dist/data/help/topics/config.jinja

@@ -22,10 +22,16 @@ Sections:
       - `job`: simultaneous generation jobs. Default: 3.
       - `request`: concurrent LLM requests. Default: 6.
 
+  `wikg://local/config/wikimedia`
+    Optional remote Wikimedia resolver:
+      - `endpoint`: optional service base URL; defaults to the current development or production gateway.
+      - `token`: required Bearer API key. A configured token enables remote resolution; an empty section keeps direct local Wikimedia access.
+
   `wikg://local/config/wikispine`
     WikiSpine runtime provider for Knowledge Graph builds:
       - `provider`: `cli` or `fetch`.
-      - `fetch` uses the built-in WikiSpine service endpoint.
+      - `endpoint`: optional service base URL for `fetch`; defaults to the current development or production gateway.
+      - `token`: required Bearer API key for `fetch`.
       - `cli` runs the local `wikispine` command from PATH.
 
 Operations:
@@ -33,13 +39,14 @@ Operations:
     {{ commandName }} wikg://local/config/llm
     {{ commandName }} wikg://local/config/embeddings
     {{ commandName }} wikg://local/config/concurrent
+    {{ commandName }} wikg://local/config/wikimedia
     {{ commandName }} wikg://local/config/wikispine
 
   Replace a section with a JSON object:
     {{ commandName }} wikg://local/config/llm set '{"provider":"openai","model":"gpt-4.1"}'
     {{ commandName }} wikg://local/config/embeddings set '{"provider":"openai","model":"text-embedding-3-small"}'
     {{ commandName }} wikg://local/config/concurrent set '{"job":3,"request":6}'
-    {{ commandName }} wikg://local/config/wikispine set '{"provider":"fetch"}'
+    Sensitive tokens cannot be supplied by `set`; configure remote Wikimedia and WikiSpine incrementally with `put`.
 
   Update one key:
     {{ commandName }} wikg://local/config/llm put provider openai
@@ -48,16 +55,23 @@ Operations:
     {{ commandName }} wikg://local/config/embeddings put model text-embedding-3-small
     {{ commandName }} wikg://local/config/concurrent put job 3
     {{ commandName }} wikg://local/config/concurrent put request 6
+    {{ commandName }} wikg://local/config/wikimedia put endpoint https://wikimedia.example.com
+    {{ commandName }} wikg://local/config/wikimedia put token --secret
     {{ commandName }} wikg://local/config/wikispine put provider cli
     {{ commandName }} wikg://local/config/wikispine put provider fetch
+    {{ commandName }} wikg://local/config/wikispine put token --secret
 
   Store the API key:
     {{ commandName }} wikg://local/config/llm put apiKey --secret
     {{ commandName }} wikg://local/config/embeddings put apiKey --secret
 
+  Store a service token:
+    {{ commandName }} wikg://local/config/wikimedia put token --secret
+    {{ commandName }} wikg://local/config/wikispine put token --secret
+
 Secret handling:
-  - `apiKey` is read through an interactive hidden prompt.
-  - `apiKey` is masked as `****` in command output.
+  - `apiKey` and `token` are read through an interactive hidden prompt.
+  - `apiKey` and `token` are masked as `****` in command output.
   - `set <json>` and `set --json-input <json>` cannot set a real `apiKey`.
   - Those JSON inputs may include `"apiKey":"****"` to preserve an existing secret.
   - Omitting `apiKey` from those JSON inputs removes it from the section.
@@ -96,16 +110,22 @@ Examples:
   {{ commandName }} wikg://local/config/embeddings put apiKey --secret
   {{ commandName }} wikg://local/config/embeddings test
   {{ commandName }} wikg://local/config/wikispine put provider fetch
+  {{ commandName }} wikg://local/config/wikispine put token --secret
   {{ commandName }} wikg://local/config/wikispine test
 
+Hosted provider environments:
+  - `pnpm dev` uses `https://pdf-craft-api.oomol.dev`.
+  - Built CLI artifacts use `https://api.pdfcraft.ai`.
+  - An explicit provider endpoint overrides these defaults.
+
 WikiSpine:
   Knowledge Graph builds require WikiSpine. If `wikispine` is missing,
   configure one provider and run the config test before starting Knowledge Graph work.
-  - `fetch` uses the built-in service endpoint and requires network access to that service.
+  - `fetch` uses the hosted service endpoint and requires network access plus a configured API key.
   - `cli` requires a `wikispine` executable on PATH and any local runtime/data it needs.
   - Test `cli` from the same shell that runs Wiki Graph; a different terminal or service environment may have a different PATH.
   - If `{{ commandName }} wikg://local/config/wikispine test` fails for `cli`, check PATH first or switch to `fetch`.
-  - If the test fails for `fetch`, check network access or switch to `cli` in environments with a prepared local runtime.
+  - If the test fails for `fetch`, check network access and the API key, or switch to `cli` in environments with a prepared local runtime.
   - CLI help does not install the local WikiSpine runtime; use `fetch` unless the local runtime is already prepared.
   - Knowledge Graph jobs should not be started until this test succeeds.
   Runtime setup and recovery guide:

package/dist/data/help/topics/readiness.jinja

@@ -125,18 +125,19 @@ WikiSpine readiness:
   WikiSpine provides entity candidate lookup for Knowledge Graph construction.
 
   Provider choices:
-  - `fetch`: use the built-in WikiSpine HTTP service. This is usually easier for Agents and hosted setups.
+  - `fetch`: use the hosted WikiSpine HTTP service with a WikiGraph API key. This is usually easier for Agents and hosted setups.
   - `cli`: run the local `wikispine` command from PATH. This is useful for offline or locally controlled environments, but requires local runtime setup and data.
 
   Configure one provider, then test it:
     {{ commandName }} wikg://local/config/wikispine put provider fetch
+    {{ commandName }} wikg://local/config/wikispine put token --secret
     {{ commandName }} wikg://local/config/wikispine test
 
     {{ commandName }} wikg://local/config/wikispine put provider cli
     {{ commandName }} wikg://local/config/wikispine test
 
   Recovery:
-    Use `fetch` when network access to the built-in service is available.
+    Use `fetch` when network access and an API key for the hosted service are available.
     Use `cli` only when a local `wikispine` executable and its runtime/data are prepared.
     Test `cli` from the same shell that runs Wiki Graph so PATH and runtime files match the job environment.
     CLI help does not install the local WikiSpine runtime; use the guide below when preparing a local setup.