@foggy-projects/deepseek-harness-plugin 0.4.2-rc.5 → 0.4.4-rc.1

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 (52) hide show
  1. package/README.md +222 -185
  2. package/THIRD-PARTY-RUNTIME-NOTICES.md +16 -16
  3. package/cordis.patch.yml +6 -6
  4. package/docs/COMMUNITY-MARKETPLACES.md +64 -64
  5. package/docs/PUBLIC-BETA-READINESS.md +109 -109
  6. package/docs/RELEASE-CANDIDATE-0.4.0-RC.2.md +38 -38
  7. package/docs/RELEASE-CANDIDATE-0.4.0-RC.3.md +18 -18
  8. package/docs/RELEASE-CANDIDATE-0.4.1-DSH-0.1.5-RC.1.md +60 -60
  9. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.1.md +62 -62
  10. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.2.md +50 -50
  11. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.3.md +34 -34
  12. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.4.md +32 -32
  13. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.5.md +27 -27
  14. package/docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md +96 -0
  15. package/docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md +135 -0
  16. package/docs/WINDOWS-BETA-ACCEPTANCE.md +113 -113
  17. package/experience/linux/README.md +53 -53
  18. package/experience/linux/prepare.sh +2 -2
  19. package/lib/atomic-json.js +41 -41
  20. package/lib/client.js +1222 -1031
  21. package/lib/component-manager.js +164 -0
  22. package/lib/component-releases.js +363 -0
  23. package/lib/diagnostics.js +86 -86
  24. package/lib/index.js +764 -698
  25. package/lib/operation-lock.js +139 -0
  26. package/lib/python-runtime.js +339 -339
  27. package/lib/query-tool.js +134 -131
  28. package/lib/remote-descriptor.js +74 -59
  29. package/lib/remote.js +8 -8
  30. package/lib/runtime-settings.js +89 -89
  31. package/lib/skill-provider.js +116 -116
  32. package/lib/typert.js +9 -9
  33. package/lib/version.js +20 -20
  34. package/lib/viewer-preview.js +44 -27
  35. package/package.json +19 -16
  36. package/skills/foggy-deepseek-onboarding/SKILL.md +149 -143
  37. package/skills/foggy-deepseek-onboarding/assets/connection.schema.json +48 -48
  38. package/skills/foggy-deepseek-onboarding/assets/datasource.example.json +14 -14
  39. package/skills/foggy-deepseek-onboarding/assets/env.example +14 -14
  40. package/skills/foggy-deepseek-onboarding/assets/onboarding-state.schema.json +71 -71
  41. package/skills/foggy-deepseek-onboarding/assets/semantic-plan.example.json +8 -8
  42. package/skills/foggy-deepseek-onboarding/assets/semantic-plan.schema.json +21 -21
  43. package/skills/foggy-deepseek-onboarding/assets/versions.json +23 -23
  44. package/skills/foggy-deepseek-onboarding/references/onboarding-workflow.md +168 -168
  45. package/skills/foggy-deepseek-onboarding/scripts/doctor.ps1 +4 -4
  46. package/skills/foggy-deepseek-onboarding/scripts/install.ps1 +4 -4
  47. package/skills/foggy-deepseek-onboarding/scripts/invoke-onboarding.ps1 +32 -32
  48. package/skills/foggy-deepseek-onboarding/scripts/onboard.ps1 +4 -4
  49. package/skills/foggy-deepseek-onboarding/scripts/onboarding.py +3721 -3697
  50. package/skills/foggy-deepseek-onboarding/scripts/runtime-start.ps1 +4 -4
  51. package/skills/foggy-deepseek-onboarding/scripts/runtime-stop.ps1 +4 -4
  52. package/skills/foggy-deepseek-onboarding/scripts/uninstall.ps1 +4 -4
@@ -1,143 +1,149 @@
1
- ---
2
- name: foggy-deepseek-onboarding
3
- description: Set up and use Foggy Runtime for data-source exploration and semantic-model development inside DeepSeek Harness. Use for local experience, datasource onboarding, TM/QM authoring, validation, and development publication; route production deployment or updates to a separate release workflow.
4
- ---
5
-
6
- # Foggy DeepSeek onboarding
7
-
8
- Use this Skill for the normal DeepSeek Harness experience: connect a development datasource, inspect
9
- it, create TM/QM files in the current workspace, and iterate until queries pass. Use the managed
10
- `foggy-runtime` CLI and this Skill's wrappers; do not configure Foggy MCP for this local workflow.
11
-
12
- ## Product boundary
13
-
14
- - Treat the plugin and bundled Launcher as local experience and development tooling.
15
- - Datasources, namespace bindings, model Bundles, refreshes, and query checks are online Runtime
16
- operations. They do not require a Runtime restart.
17
- - Start Runtime only when it is absent. Reuse a healthy running Runtime. Restart only when the user
18
- asks, a Launcher/JAR upgrade requires it, Runtime is unhealthy, or an actual startup setting such as
19
- port, JVM options, Runtime authentication, or an opt-in module changes.
20
- - Do not turn production publication into a continuation of local onboarding. When the user wants to
21
- deploy or update a formal environment, recommend a manual release or a dedicated production
22
- deployment workflow with separately supplied target access, credentials, version, verification, and
23
- rollback information.
24
- - Do not modify Foggy engine or CLI source. If progress genuinely requires either change, stop and ask
25
- for explicit authorization.
26
-
27
- ## Managed installation
28
-
29
- This Skill is registered through DeepSeek Harness's native Skill registry. Its scripts and references
30
- are authoritative; do not copy the Skill into the current workspace.
31
-
32
- - Linux install state: `${XDG_DATA_HOME:-$HOME/.local/share}/foggy/deepseek-harness/install-state.json`.
33
- - Windows install state: `%LOCALAPPDATA%\Foggy\DeepSeekHarness\install-state.json`.
34
- - Run this Skill's `doctor` wrapper with the current DSH workspace as `--project-root`. The managed CLI
35
- is intentionally isolated, so absence from `PATH` does not mean it is missing.
36
- - Use plugin settings to initialize or repair private Python, CLI, Launcher, or the managed analysis
37
- Skill. Do not independently reinstall them during a normal analysis session.
38
- - Treat the current DSH workspace as `projectRoot`. Keep model drafts and final model files there rather
39
- than redirecting them to an example repository.
40
-
41
- ## Development workflow
42
-
43
- 1. Run `doctor`. Runtime health is established by the managed CLI's read-only `wait-ready` check;
44
- process visibility alone does not prove HTTP readiness. Start Runtime only if it is not already
45
- healthy; require `wait-ready` and `capabilities` after a new start.
46
- 2. Accept datasource connection details from the user's message, a user-supplied local JSON file, an
47
- environment variable, or Runtime Console. Direct `password` is supported for local development.
48
- The wrapper submits it to the public Runtime API without copying it into onboarding state or
49
- evidence. Do not echo it in the response.
50
- 3. Create or select the namespace, add/test the datasource online, and bind it to the namespace. Do
51
- not stop or restart Runtime to make a password available. A running Runtime can accept a direct
52
- development password through its datasource API.
53
- 4. Inspect tables, columns, keys, and relationships. Small, bounded, read-only SQL samples are allowed
54
- when they help infer captions, enums, units, or date semantics. Do not run mutations unless the user
55
- explicitly requests them.
56
- 5. Load `foggy-ai-analysis` from the native registry only for TM/QM authoring and query tuning; its
57
- generic installation, datasource-secret, and production-deployment guidance does not override this
58
- development workflow. Default to a project-local `models/` directory unless the user specifies
59
- another directory.
60
- 6. Iterate through model validation, Bundle registration/update, model refresh/describe, query
61
- validation, and bounded query execution. Development publication means making the local model
62
- directory effective in this local Runtime; it is not a production release.
63
- For the final user-facing standard DSL query in Harness, use the native `foggy_query` tool when
64
- available (explicit namespace, published QM, `columns`, and `limit` of 1–100). It validates and
65
- executes, then displays a query card. The card creates a DataViewer preview link only if the user
66
- clicks its button; never pre-create links for every query. This first version does not support
67
- `DSL_CTE` or `executable_plan` in the native tool. Continue using the documented CLI route for
68
- CTE queries and do not claim they have a DataViewer preview.
69
- A successful response may still contain Runtime `warnings`. Preserve and report their stable facts
70
- (`code`, `path`, `message`, `suggestedNextAction`, `safeToAutoRepair`, `normalizedFragment`,
71
- `docsRef`, and `details.allowedProperties`)
72
- instead of treating success as proof that every requested option took effect. Free-text advice is
73
- optional. When a warning indicates possible semantic drift, use `models describe` to prepare a
74
- corrected payload if the user's intent can be preserved; otherwise disclose the limitation.
75
- Runtime 0.1.21 defaults unknown ordinary Query DSL properties to `WARN`; `IGNORE` continues without
76
- `queryInputWarnings`, while `STRICT` rejects the request with the complete structured violations.
77
- Never reinterpret a protected or governance-field failure as an ignorable warning.
78
- 7. When the model works, recommend committing the model directory to the user's own Git repository.
79
- Do not initialize a repository, commit, push, or create a remote unless the user requests it.
80
-
81
- For a normal end-to-end request, take the documented composite-command path first. Do not inspect
82
- `onboarding.py`, enumerate CLI help, search installation directories, load the sales-drop example, or
83
- fetch online syntax documentation before trying that path. Use those troubleshooting or reference
84
- sources only when a concrete error or unsupported modeling requirement makes them relevant.
85
-
86
- Use the user's business terms to narrow schema discovery with `--pattern` or repeated `--table` when
87
- there are clear candidates. Otherwise keep the bounded default, then inspect only the few tables and
88
- columns needed for the requested model. Full results belong in the evidence files; retain concise
89
- summaries and paths in the conversation instead of repeatedly reading complete JSON artifacts.
90
-
91
- Read [references/onboarding-workflow.md](references/onboarding-workflow.md) for the wrapper commands and
92
- credential shapes. Use `foggy-ai-analysis` references for detailed TM/QM modeling and query tuning.
93
-
94
- ## Credential choices for local development
95
-
96
- Choose the simplest source the user provides:
97
-
98
- - `password` in a connection file: simplest for an experience session; the source file remains under
99
- the user's control and should normally stay outside Git.
100
- - `passwordEnv`: the wrapper reads the variable from the Agent process and submits the value online;
101
- Runtime does not need to inherit it at startup.
102
- - Opaque profile: optional for users who already have one; never require it for ordinary onboarding.
103
- - Runtime Console: when a Launcher exposing Runtime Console is installed, the user may enter the
104
- connection there using the management token shown by the host/plugin.
105
-
106
- Keep only a minimal development safety baseline: do not echo passwords, put them in TM/QM files,
107
- include them in evidence/diagnostics, or commit them to Git. Do not impose production IAM, audit,
108
- approval, secret-store, or network-governance requirements on this local flow.
109
-
110
- ## Command behavior
111
-
112
- All scripts emit one JSON object. Treat `success=false` or a nonzero exit code as failure. Prefer the
113
- two resumable composite commands for a complete requested experience:
114
-
115
- ```text
116
- onboard-datasource-run --project-root <workspace> --connection-file <json> \
117
- --approve-configure --approve-bind --include-indexes
118
-
119
- onboard-semantic-run --project-root <workspace> --semantic-plan <json> \
120
- --query-payload <json> --approve-validate --approve-publish --approve-execute
121
- ```
122
-
123
- When the user has already asked to connect, build, and test a new local model, those flags implement
124
- that request and do not require separate question-by-question confirmation. Replacement, pruning, broad
125
- queries, destructive SQL, Git push, and production deployment still require their own clear scope.
126
-
127
- The normal analysis order is:
128
-
129
- ```text
130
- datasource add/test -> namespace bind -> table/schema inspection
131
- TM/QM authoring -> models validate -> bundle add/update -> refresh/describe
132
- query validate -> bounded query execute -> tune -> optional Git handoff
133
- ```
134
-
135
- Stop only the PID recorded by this package and preserve the Runtime work directory unless the user
136
- explicitly requests removal.
137
-
138
- ## Result
139
-
140
- Report the Runtime URL, namespace, datasource name, model directory, Bundle and QueryModel names,
141
- validation/query status, and useful evidence paths. Never include the password or business row values
142
- unless the user specifically asks for those values. Include Runtime warning count/codes and the
143
- warning evidence path when validation or execution completed with warnings.
1
+ ---
2
+ name: foggy-deepseek-onboarding
3
+ description: Set up and use Foggy Runtime for data-source exploration and semantic-model development inside DeepSeek Harness. Use for local experience, datasource onboarding, TM/QM authoring, validation, and development publication; route production deployment or updates to a separate release workflow.
4
+ ---
5
+
6
+ # Foggy DeepSeek onboarding
7
+
8
+ Use this Skill for the normal DeepSeek Harness experience: connect a development datasource, inspect
9
+ it, create TM/QM files in the current workspace, and iterate until queries pass. Use the managed
10
+ `foggy-runtime` CLI and this Skill's wrappers; do not configure Foggy MCP for this local workflow.
11
+
12
+ ## Product boundary
13
+
14
+ - Treat the plugin and bundled Launcher as local experience and development tooling.
15
+ - Datasources, namespace bindings, model Bundles, refreshes, and query checks are online Runtime
16
+ operations. They do not require a Runtime restart.
17
+ - Start Runtime only when it is absent. Reuse a healthy running Runtime. Restart only when the user
18
+ asks, a Launcher/JAR upgrade requires it, Runtime is unhealthy, or an actual startup setting such as
19
+ port, JVM options, Runtime authentication, or an opt-in module changes.
20
+ - Do not turn production publication into a continuation of local onboarding. When the user wants to
21
+ deploy or update a formal environment, recommend a manual release or a dedicated production
22
+ deployment workflow with separately supplied target access, credentials, version, verification, and
23
+ rollback information.
24
+ - Do not modify Foggy engine or CLI source. If progress genuinely requires either change, stop and ask
25
+ for explicit authorization.
26
+
27
+ ## Managed installation
28
+
29
+ This Skill is registered through DeepSeek Harness's native Skill registry. Its scripts and references
30
+ are authoritative; do not copy the Skill into the current workspace.
31
+
32
+ - Linux install state: `${XDG_DATA_HOME:-$HOME/.local/share}/foggy/deepseek-harness/install-state.json`.
33
+ - Windows install state: `%LOCALAPPDATA%\Foggy\DeepSeekHarness\install-state.json`.
34
+ - Run this Skill's `doctor` wrapper with the current DSH workspace as `--project-root`. The managed CLI
35
+ is intentionally isolated, so absence from `PATH` does not mean it is missing.
36
+ - Use plugin settings to initialize or repair private Python, CLI, Launcher, or the managed analysis
37
+ Skill. Do not independently reinstall them during a normal analysis session.
38
+ - Settings automatically checks official Launcher/CLI releases and lets the user select a version to
39
+ download and use. Checks never change installed components. Stop Runtime before switching versions;
40
+ saved choices persist across plugin upgrades and previously downloaded versions support rollback.
41
+ - Treat the current DSH workspace as `projectRoot`. Keep model drafts and final model files there rather
42
+ than redirecting them to an example repository.
43
+
44
+ ## Development workflow
45
+
46
+ 1. Run `doctor`. Runtime health is established by the managed CLI's read-only `wait-ready` check;
47
+ process visibility alone does not prove HTTP readiness. Start Runtime only if it is not already
48
+ healthy; require `wait-ready` and `capabilities` after a new start.
49
+ 2. Accept datasource connection details from the user's message, a user-supplied local JSON file, an
50
+ environment variable, or Runtime Console. Direct `password` is supported for local development.
51
+ The wrapper submits it to the public Runtime API without copying it into onboarding state or
52
+ evidence. Do not echo it in the response.
53
+ 3. Create or select the namespace, add/test the datasource online, and bind it to the namespace. Do
54
+ not stop or restart Runtime to make a password available. A running Runtime can accept a direct
55
+ development password through its datasource API.
56
+ Bind the namespace explicitly even when using the built-in `default` datasource. Launcher 0.1.46
57
+ detached model validation requires that binding. When using the optional legacy sales-drop replay,
58
+ first run `foggy-runtime --base-url <url> datasources bind --namespace salesdrop --data-source default`.
59
+ 4. Inspect tables, columns, keys, and relationships. Small, bounded, read-only SQL samples are allowed
60
+ when they help infer captions, enums, units, or date semantics. Do not run mutations unless the user
61
+ explicitly requests them.
62
+ 5. Load `foggy-ai-analysis` from the native registry only for TM/QM authoring and query tuning; its
63
+ generic installation, datasource-secret, and production-deployment guidance does not override this
64
+ development workflow. Default to a project-local `models/` directory unless the user specifies
65
+ another directory.
66
+ 6. Iterate through model validation, Bundle registration/update, model refresh/describe, query
67
+ validation, and bounded query execution. Development publication means making the local model
68
+ directory effective in this local Runtime; it is not a production release.
69
+ For the final user-facing standard DSL query in Harness, use the native `foggy_query` tool when
70
+ available (explicit namespace, published QM, `columns`, and `limit` of 1–100). It validates and
71
+ executes, then displays a query card. The card creates a DataViewer preview link only if the user
72
+ clicks its button; never pre-create links for every query. This first version does not support
73
+ `DSL_CTE` or `executable_plan` in the native tool. Continue using the documented CLI route for
74
+ CTE queries and do not claim they have a DataViewer preview.
75
+ A successful response may still contain Runtime `warnings`. Preserve and report their stable facts
76
+ (`code`, `path`, `message`, `suggestedNextAction`, `safeToAutoRepair`, `normalizedFragment`,
77
+ `docsRef`, and `details.allowedProperties`)
78
+ instead of treating success as proof that every requested option took effect. Free-text advice is
79
+ optional. When a warning indicates possible semantic drift, use `models describe` to prepare a
80
+ corrected payload if the user's intent can be preserved; otherwise disclose the limitation.
81
+ Unknown ordinary Query DSL properties in `WARN` mode produce structured warnings; `IGNORE` continues without
82
+ `queryInputWarnings`, while `STRICT` rejects the request with the complete structured violations.
83
+ Never reinterpret a protected or governance-field failure as an ignorable warning.
84
+ 7. When the model works, recommend committing the model directory to the user's own Git repository.
85
+ Do not initialize a repository, commit, push, or create a remote unless the user requests it.
86
+
87
+ For a normal end-to-end request, take the documented composite-command path first. Do not inspect
88
+ `onboarding.py`, enumerate CLI help, search installation directories, load the sales-drop example, or
89
+ fetch online syntax documentation before trying that path. Use those troubleshooting or reference
90
+ sources only when a concrete error or unsupported modeling requirement makes them relevant.
91
+
92
+ Use the user's business terms to narrow schema discovery with `--pattern` or repeated `--table` when
93
+ there are clear candidates. Otherwise keep the bounded default, then inspect only the few tables and
94
+ columns needed for the requested model. Full results belong in the evidence files; retain concise
95
+ summaries and paths in the conversation instead of repeatedly reading complete JSON artifacts.
96
+
97
+ Read [references/onboarding-workflow.md](references/onboarding-workflow.md) for the wrapper commands and
98
+ credential shapes. Use `foggy-ai-analysis` references for detailed TM/QM modeling and query tuning.
99
+
100
+ ## Credential choices for local development
101
+
102
+ Choose the simplest source the user provides:
103
+
104
+ - `password` in a connection file: simplest for an experience session; the source file remains under
105
+ the user's control and should normally stay outside Git.
106
+ - `passwordEnv`: the wrapper reads the variable from the Agent process and submits the value online;
107
+ Runtime does not need to inherit it at startup.
108
+ - Opaque profile: optional for users who already have one; never require it for ordinary onboarding.
109
+ - Runtime Console: when a Launcher exposing Runtime Console is installed, the user may enter the
110
+ connection there using the management token shown by the host/plugin.
111
+
112
+ Keep only a minimal development safety baseline: do not echo passwords, put them in TM/QM files,
113
+ include them in evidence/diagnostics, or commit them to Git. Do not impose production IAM, audit,
114
+ approval, secret-store, or network-governance requirements on this local flow.
115
+
116
+ ## Command behavior
117
+
118
+ All scripts emit one JSON object. Treat `success=false` or a nonzero exit code as failure. Prefer the
119
+ two resumable composite commands for a complete requested experience:
120
+
121
+ ```text
122
+ onboard-datasource-run --project-root <workspace> --connection-file <json> \
123
+ --approve-configure --approve-bind --include-indexes
124
+
125
+ onboard-semantic-run --project-root <workspace> --semantic-plan <json> \
126
+ --query-payload <json> --approve-validate --approve-publish --approve-execute
127
+ ```
128
+
129
+ When the user has already asked to connect, build, and test a new local model, those flags implement
130
+ that request and do not require separate question-by-question confirmation. Replacement, pruning, broad
131
+ queries, destructive SQL, Git push, and production deployment still require their own clear scope.
132
+
133
+ The normal analysis order is:
134
+
135
+ ```text
136
+ datasource add/test -> namespace bind -> table/schema inspection
137
+ TM/QM authoring -> models validate -> bundle add/update -> refresh/describe
138
+ query validate -> bounded query execute -> tune -> optional Git handoff
139
+ ```
140
+
141
+ Stop only the PID recorded by this package and preserve the Runtime work directory unless the user
142
+ explicitly requests removal.
143
+
144
+ ## Result
145
+
146
+ Report the Runtime URL, namespace, datasource name, model directory, Bundle and QueryModel names,
147
+ validation/query status, and useful evidence paths. Never include the password or business row values
148
+ unless the user specifically asks for those values. Include Runtime warning count/codes and the
149
+ warning evidence path when validation or execution completed with warnings.
@@ -1,48 +1,48 @@
1
- {
2
- "$schema": "https://json-schema.org/draft/2020-12/schema",
3
- "$id": "https://foggy-projects.dev/schemas/deepseek-harness/connection.schema.json",
4
- "title": "Foggy DeepSeek Harness connection plan",
5
- "type": "object",
6
- "additionalProperties": false,
7
- "required": ["schemaVersion", "name", "type", "namespace"],
8
- "properties": {
9
- "schemaVersion": {"const": "foggy-deepseek-connection/v1"},
10
- "profile": {"type": "string", "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]*$"},
11
- "name": {"type": "string", "minLength": 1},
12
- "type": {"enum": ["sqlite", "mysql", "postgres", "postgresql"]},
13
- "jdbcUrl": {"type": "string", "minLength": 1},
14
- "username": {"type": "string"},
15
- "password": {"type": "string", "description": "Optional local development password. It is submitted once and is not copied into onboarding state or evidence."},
16
- "passwordEnv": {"type": "string", "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"},
17
- "opaqueProfileId": {"type": "string", "pattern": "^fop_[a-f0-9]{32}$"},
18
- "opaqueRevision": {"type": "string", "pattern": "^sha256:[a-f0-9]{64}$"},
19
- "namespace": {"type": "string", "minLength": 1},
20
- "schemas": {"type": "array", "items": {"type": "string", "minLength": 1}, "uniqueItems": true},
21
- "modelsDir": {"type": "string", "minLength": 1, "default": "models"},
22
- "evidenceDir": {"type": "string", "minLength": 1},
23
- "readOnlyRecommended": {"type": "boolean", "default": true}
24
- },
25
- "oneOf": [
26
- {
27
- "required": ["opaqueProfileId", "opaqueRevision"],
28
- "not": {"anyOf": [
29
- {"required": ["jdbcUrl"]},
30
- {"required": ["username"]},
31
- {"required": ["password"]},
32
- {"required": ["passwordEnv"]}
33
- ]}
34
- },
35
- {
36
- "required": ["jdbcUrl"],
37
- "not": {"anyOf": [
38
- {"required": ["opaqueProfileId"]},
39
- {"required": ["opaqueRevision"]}
40
- ]}
41
- }
42
- ],
43
- "allOf": [{
44
- "not": {
45
- "required": ["password", "passwordEnv"]
46
- }
47
- }]
48
- }
1
+ {
2
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
3
+ "$id": "https://foggy-projects.dev/schemas/deepseek-harness/connection.schema.json",
4
+ "title": "Foggy DeepSeek Harness connection plan",
5
+ "type": "object",
6
+ "additionalProperties": false,
7
+ "required": ["schemaVersion", "name", "type", "namespace"],
8
+ "properties": {
9
+ "schemaVersion": {"const": "foggy-deepseek-connection/v1"},
10
+ "profile": {"type": "string", "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]*$"},
11
+ "name": {"type": "string", "minLength": 1},
12
+ "type": {"enum": ["sqlite", "mysql", "postgres", "postgresql"]},
13
+ "jdbcUrl": {"type": "string", "minLength": 1},
14
+ "username": {"type": "string"},
15
+ "password": {"type": "string", "description": "Optional local development password. It is submitted once and is not copied into onboarding state or evidence."},
16
+ "passwordEnv": {"type": "string", "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"},
17
+ "opaqueProfileId": {"type": "string", "pattern": "^fop_[a-f0-9]{32}$"},
18
+ "opaqueRevision": {"type": "string", "pattern": "^sha256:[a-f0-9]{64}$"},
19
+ "namespace": {"type": "string", "minLength": 1},
20
+ "schemas": {"type": "array", "items": {"type": "string", "minLength": 1}, "uniqueItems": true},
21
+ "modelsDir": {"type": "string", "minLength": 1, "default": "models"},
22
+ "evidenceDir": {"type": "string", "minLength": 1},
23
+ "readOnlyRecommended": {"type": "boolean", "default": true}
24
+ },
25
+ "oneOf": [
26
+ {
27
+ "required": ["opaqueProfileId", "opaqueRevision"],
28
+ "not": {"anyOf": [
29
+ {"required": ["jdbcUrl"]},
30
+ {"required": ["username"]},
31
+ {"required": ["password"]},
32
+ {"required": ["passwordEnv"]}
33
+ ]}
34
+ },
35
+ {
36
+ "required": ["jdbcUrl"],
37
+ "not": {"anyOf": [
38
+ {"required": ["opaqueProfileId"]},
39
+ {"required": ["opaqueRevision"]}
40
+ ]}
41
+ }
42
+ ],
43
+ "allOf": [{
44
+ "not": {
45
+ "required": ["password", "passwordEnv"]
46
+ }
47
+ }]
48
+ }
@@ -1,14 +1,14 @@
1
- {
2
- "schemaVersion": "foggy-deepseek-connection/v1",
3
- "profile": "business",
4
- "name": "business-db",
5
- "type": "mysql",
6
- "jdbcUrl": "jdbc:mysql://127.0.0.1:3306/business",
7
- "username": "business_dev",
8
- "password": "replace-for-local-development",
9
- "namespace": "business",
10
- "schemas": ["public"],
11
- "modelsDir": "models",
12
- "evidenceDir": ".foggy/onboarding-command-evidence/business",
13
- "readOnlyRecommended": true
14
- }
1
+ {
2
+ "schemaVersion": "foggy-deepseek-connection/v1",
3
+ "profile": "business",
4
+ "name": "business-db",
5
+ "type": "mysql",
6
+ "jdbcUrl": "jdbc:mysql://127.0.0.1:3306/business",
7
+ "username": "business_dev",
8
+ "password": "replace-for-local-development",
9
+ "namespace": "business",
10
+ "schemas": ["public"],
11
+ "modelsDir": "models",
12
+ "evidenceDir": ".foggy/onboarding-command-evidence/business",
13
+ "readOnlyRecommended": true
14
+ }
@@ -1,14 +1,14 @@
1
- # Optional development configuration. Direct passwords in a user-supplied connection file are also
2
- # supported; the onboarding wrapper does not copy them into state or evidence.
3
-
4
- FOGGY_RUNTIME_API_URL=http://127.0.0.1:18166
5
- FOGGY_NAMESPACE=default
6
-
7
- # Optional when Runtime reports securityMode=auth-code.
8
- # FOGGY_RUNTIME_API_AUTH_CODE=
9
-
10
- # Optional data-plane authorization value.
11
- # FOGGY_RUNTIME_AUTHORIZATION=
12
-
13
- # Optional alternative to a direct development password.
14
- # FOGGY_DATASOURCE_PASSWORD=
1
+ # Optional development configuration. Direct passwords in a user-supplied connection file are also
2
+ # supported; the onboarding wrapper does not copy them into state or evidence.
3
+
4
+ FOGGY_RUNTIME_API_URL=http://127.0.0.1:18166
5
+ FOGGY_NAMESPACE=default
6
+
7
+ # Optional when Runtime reports securityMode=auth-code.
8
+ # FOGGY_RUNTIME_API_AUTH_CODE=
9
+
10
+ # Optional data-plane authorization value.
11
+ # FOGGY_RUNTIME_AUTHORIZATION=
12
+
13
+ # Optional alternative to a direct development password.
14
+ # FOGGY_DATASOURCE_PASSWORD=