dsh-env-manager-plugin 0.1.0 → 0.1.2

package/docs/05-domain/prompt-template.md

@@ -1,90 +1,90 @@
-# Prompt Template
-
-Templates for presenting tool results to an Agent. Keep them compact; do not dump the whole registry.
-
-## Service Context
-
-```markdown
-# Service Context
-
-Environment: {environmentId} ({environmentName}, {environmentCategory})
-Service:     {serviceId} ({serviceName})
-Deployment:  {deploymentId} ({runtimeMode})
-Status:      {status}
-
-## Source
-
-- Git: {source.gitUrl} ({source.defaultBranch})
-- Module: {source.modulePath}
-- Artifact: {artifact.name} ({artifact.path})
-
-## Location
-
-{locationSummary}
-
-## Log source
-
-{logSourceSummary}
-
-## Resolved paths
-
-| Field | Value | Defined by | Inputs |
-|---|---|---|---|
-{pathRows}
-
-## Class location
-
-{classLocationSummary}
-
-## Credentials
-
-- {ref} — configured: {configured} (source: {source})
-
-## Diagnostics
-
-{diagnostics}
-```
-
-Rules:
-
-- Mark derived values as derived; do not imply they exist.
-- Show provenance for every path, because that is how users debug overrides.
-- Never include credential values.
-
-## Operation Resolution
-
-```markdown
-# Operation Resolution
-
-Operation: {operation}
-Context:   {environmentId} / {serviceId} / {deploymentId}
-Binding:   {matchedBindingId} (level: {matchLevel})
-Skill:     {skill.name} (available: {skill.available})
-Policy:    requiresApproval={policy.requiresApproval}, allowProduction={policy.allowProduction}
-
-## Parameters
-
-- {key}: {value}
-
-## Diagnostics
-
-{diagnostics}
-```
-
-Rules:
-
-- If the result is a conflict, list every candidate binding and its level.
-- If the Skill is unavailable, state why and do not suggest an alternative Skill.
-- Never present a routing result as permission to execute.
-
-## Environment Summary
-
-```markdown
-# Environments
-
-| Environment | Category | Hosts | Clusters | Services |
-|---|---|---|---|---|
-{rows}
-```
-
-Keep list output under 50 rows; point the reader at `env_get` for detail.
+# Prompt Template
+
+Templates for presenting tool results to an Agent. Keep them compact; do not dump the whole registry.
+
+## Service Context
+
+```markdown
+# Service Context
+
+Environment: {environmentId} ({environmentName}, {environmentCategory})
+Service:     {serviceId} ({serviceName})
+Deployment:  {deploymentId} ({runtimeMode})
+Status:      {status}
+
+## Source
+
+- Git: {source.gitUrl} ({source.defaultBranch})
+- Module: {source.modulePath}
+- Artifact: {artifact.name} ({artifact.path})
+
+## Location
+
+{locationSummary}
+
+## Log source
+
+{logSourceSummary}
+
+## Resolved paths
+
+| Field | Value | Defined by | Inputs |
+|---|---|---|---|
+{pathRows}
+
+## Class location
+
+{classLocationSummary}
+
+## Credentials
+
+- {ref} — configured: {configured} (source: {source})
+
+## Diagnostics
+
+{diagnostics}
+```
+
+Rules:
+
+- Mark derived values as derived; do not imply they exist.
+- Show provenance for every path, because that is how users debug overrides.
+- Never include credential values.
+
+## Operation Resolution
+
+```markdown
+# Operation Resolution
+
+Operation: {operation}
+Context:   {environmentId} / {serviceId} / {deploymentId}
+Binding:   {matchedBindingId} (level: {matchLevel})
+Skill:     {skill.name} (available: {skill.available})
+Policy:    requiresApproval={policy.requiresApproval}, allowProduction={policy.allowProduction}
+
+## Parameters
+
+- {key}: {value}
+
+## Diagnostics
+
+{diagnostics}
+```
+
+Rules:
+
+- If the result is a conflict, list every candidate binding and its level.
+- If the Skill is unavailable, state why and do not suggest an alternative Skill.
+- Never present a routing result as permission to execute.
+
+## Environment Summary
+
+```markdown
+# Environments
+
+| Environment | Category | Hosts | Clusters | Services |
+|---|---|---|---|---|
+{rows}
+```
+
+Keep list output under 50 rows; point the reader at `env_get` for detail.

package/docs/05-domain/rule-template.md

@@ -1,73 +1,73 @@
-# Rule Profile Template
-
-Copy into `<dataDir>/rules/<id>.yaml`.
-
-```yaml
-id: java-common
-schemaVersion: 1
-description: Common Java service paths, log sources and class locations
-
-variables:
-  installRoot: /opt/company/services
-  timezone: Asia/Shanghai
-
-paths:
-  serviceHome: ${installRoot}/${service.id}
-  jar: ${paths.serviceHome}/lib/${service.artifact.name}
-  logDir: ${paths.serviceHome}/logs
-  applicationLog: ${paths.logDir}/${service.id}.log
-  configDir: ${paths.serviceHome}/config
-
-logSources:
-  native:
-    kind: file
-    path: ${paths.applicationLog}
-  docker:
-    kind: container-stdout
-    container: ${deployment.location.containerName}
-  kubernetes:
-    kind: pod-logs
-    namespace: ${deployment.location.namespace}
-    workload: ${deployment.location.workload.name}
-
-classLocations:
-  native:
-    kind: deployed-dir
-    path: ${paths.serviceHome}/classes
-  kubernetes:
-    kind: jar-entry
-    path: ${paths.jar}
-    entryPrefix: com/company/aico
-
-createdAt: 2026-11-01T03:00:00.000Z
-updatedAt: 2026-11-01T03:00:00.000Z
-```
-
-## Template syntax
-
-Allowed:
-
-```text
-${installRoot}
-${paths.serviceHome}
-${service.id}
-${deployment.location.namespace}
-```
-
-Forbidden:
-
-- function calls, arithmetic, conditionals
-- environment variable access
-- shell or command substitution
-- JavaScript
-
-## Notes
-
-- A path may reference another path; cycles are errors.
-- Undefined references are errors, not empty strings.
-- The only valid form is `${identifier(.identifier)*}`, capped at 2048 characters;
-  anything else (missing brace, operators, spaces) is `RULE_TEMPLATE_INVALID`.
-- Resolved paths containing `..` are rejected.
-- `classLocations` distinguishes build output, deployed directories and jar entries.
-- Only the deployment's `runtimeMode` entry is resolved by `env_resolve`.
-- Overrides: environment `ruleOverrides`, then deployment `variables` and `ruleOverrides`.
+# Rule Profile Template
+
+Copy into `<dataDir>/rules/<id>.yaml`.
+
+```yaml
+id: java-common
+schemaVersion: 1
+description: Common Java service paths, log sources and class locations
+
+variables:
+  installRoot: /opt/company/services
+  timezone: Asia/Shanghai
+
+paths:
+  serviceHome: ${installRoot}/${service.id}
+  jar: ${paths.serviceHome}/lib/${service.artifact.name}
+  logDir: ${paths.serviceHome}/logs
+  applicationLog: ${paths.logDir}/${service.id}.log
+  configDir: ${paths.serviceHome}/config
+
+logSources:
+  native:
+    kind: file
+    path: ${paths.applicationLog}
+  docker:
+    kind: container-stdout
+    container: ${deployment.location.containerName}
+  kubernetes:
+    kind: pod-logs
+    namespace: ${deployment.location.namespace}
+    workload: ${deployment.location.workload.name}
+
+classLocations:
+  native:
+    kind: deployed-dir
+    path: ${paths.serviceHome}/classes
+  kubernetes:
+    kind: jar-entry
+    path: ${paths.jar}
+    entryPrefix: com/company/aico
+
+createdAt: 2026-11-01T03:00:00.000Z
+updatedAt: 2026-11-01T03:00:00.000Z
+```
+
+## Template syntax
+
+Allowed:
+
+```text
+${installRoot}
+${paths.serviceHome}
+${service.id}
+${deployment.location.namespace}
+```
+
+Forbidden:
+
+- function calls, arithmetic, conditionals
+- environment variable access
+- shell or command substitution
+- JavaScript
+
+## Notes
+
+- A path may reference another path; cycles are errors.
+- Undefined references are errors, not empty strings.
+- The only valid form is `${identifier(.identifier)*}`, capped at 2048 characters;
+  anything else (missing brace, operators, spaces) is `RULE_TEMPLATE_INVALID`.
+- Resolved paths containing `..` are rejected.
+- `classLocations` distinguishes build output, deployed directories and jar entries.
+- Only the deployment's `runtimeMode` entry is resolved by `env_resolve`.
+- Overrides: environment `ruleOverrides`, then deployment `variables` and `ruleOverrides`.

package/docs/05-domain/service-template.md

@@ -1,39 +1,39 @@
-# Service Template
-
-Copy into `<dataDir>/services/<id>.yaml` and replace the example values.
-
-```yaml
-id: aicoservice
-schemaVersion: 1
-name: Aico Service
-aliases: [aicoservice]
-category: backend
-description: Core AI coordination service
-
-git:
-  url: https://git.example.internal/team/aicoservice.git
-  defaultBranch: main
-  modulePath: /            # monorepo subpath, omit when not needed
-
-build:
-  tool: maven              # maven | gradle | npm | custom
-  command: mvn -DskipTests package
-
-artifact:
-  name: aicoservice.jar
-  path: ${paths.serviceHome}/lib/${service.artifact.name}
-
-deployModes: [native, docker, kubernetes]
-ruleProfileRefs: [java-common, company-default]   # order matters; later wins
-
-createdAt: 2026-11-01T03:00:00.000Z
-updatedAt: 2026-11-01T03:00:00.000Z
-```
-
-## Notes
-
-- Services are environment-independent. Placement belongs in a deployment binding.
-- `ruleProfileRefs` are applied in order; when two profiles define the same field, the later one wins.
-- `deployModes` must include every runtime mode used by its deployment bindings.
-- `artifact.name` is commonly interpolated by rule profiles as `${service.artifact.name}`.
-- No credentials here. A service-level credential is not modelled in V1.
+# Service Template
+
+Copy into `<dataDir>/services/<id>.yaml` and replace the example values.
+
+```yaml
+id: aicoservice
+schemaVersion: 1
+name: Aico Service
+aliases: [aicoservice]
+category: backend
+description: Core AI coordination service
+
+git:
+  url: https://git.example.internal/team/aicoservice.git
+  defaultBranch: main
+  modulePath: /            # monorepo subpath, omit when not needed
+
+build:
+  tool: maven              # maven | gradle | npm | custom
+  command: mvn -DskipTests package
+
+artifact:
+  name: aicoservice.jar
+  path: ${paths.serviceHome}/lib/${service.artifact.name}
+
+deployModes: [native, docker, kubernetes]
+ruleProfileRefs: [java-common, company-default]   # order matters; later wins
+
+createdAt: 2026-11-01T03:00:00.000Z
+updatedAt: 2026-11-01T03:00:00.000Z
+```
+
+## Notes
+
+- Services are environment-independent. Placement belongs in a deployment binding.
+- `ruleProfileRefs` are applied in order; when two profiles define the same field, the later one wins.
+- `deployModes` must include every runtime mode used by its deployment bindings.
+- `artifact.name` is commonly interpolated by rule profiles as `${service.artifact.name}`.
+- No credentials here. A service-level credential is not modelled in V1.

package/docs/06-operations/deployment-guide.md

@@ -1,54 +1,54 @@
-# Deployment Guide
-
-## Install as a Local Bundle
-
-In a DSH session, call the `plugin_manager` tool:
-
-```text
-action: install_bundle
-target: <absolute path to this repository>
-```
-
-Restart DSH if needed.
-
-## Verify
-
-1. Ask `plugin_manager` for `action: list_bundles` and confirm the bundle appears.
-2. Confirm it is active, not `overridden` or `restart-required`.
-3. Call `env_list` from the Agent; a fresh install returns an empty list.
-4. Open the **Environment Manager** entry in the sidebar and confirm the Overview
-   counts render.
-5. Optional transport check:
-
-   ```bash
-   curl -s -X POST http://127.0.0.1:<port>/env-manager/api \
-     -H 'content-type: application/json' \
-     -H 'x-env-manager-request: 1' \
-     -d '{"op":"meta"}'
-   ```
-
-   Without the header the route returns 403; that is the expected control.
-
-## Upgrade
-
-1. Pull the latest changes.
-2. `npm install && npm run build`.
-3. Reinstall the bundle with `plugin_manager`.
-4. Restart DSH so the Host module generation is fresh.
-5. Run `env_validate` and review diagnostics.
-
-Registry data is untouched by an upgrade. A `schemaVersion` change requires a migration; V1 has none.
-
-## Remove
-
-Call `plugin_manager` with `action: remove_bundle` and `target: dsh-env-manager-plugin`.
-
-Registry data under `dataDir` is not deleted. Back it up if you may reinstall later.
-
-## Rollback
-
-1. Reinstall the previous checkout.
-2. Restart DSH.
-3. Restore `dataDir` from the backup if the previous version wrote incompatible records.
-
-V1 accepts only `schemaVersion: 1`; records written by an unknown version are skipped with a warning rather than corrupted.
+# Deployment Guide
+
+## Install as a Local Bundle
+
+In a DSH session, call the `plugin_manager` tool:
+
+```text
+action: install_bundle
+target: <absolute path to this repository>
+```
+
+Restart DSH if needed.
+
+## Verify
+
+1. Ask `plugin_manager` for `action: list_bundles` and confirm the bundle appears.
+2. Confirm it is active, not `overridden` or `restart-required`.
+3. Call `env_list` from the Agent; a fresh install returns an empty list.
+4. Open the **Environment Manager** entry in the sidebar and confirm the Overview
+   counts render.
+5. Optional transport check:
+
+   ```bash
+   curl -s -X POST http://127.0.0.1:<port>/env-manager/api \
+     -H 'content-type: application/json' \
+     -H 'x-env-manager-request: 1' \
+     -d '{"op":"meta"}'
+   ```
+
+   Without the header the route returns 403; that is the expected control.
+
+## Upgrade
+
+1. Pull the latest changes.
+2. `npm install && npm run build`.
+3. Reinstall the bundle with `plugin_manager`.
+4. Restart DSH so the Host module generation is fresh.
+5. Run `env_validate` and review diagnostics.
+
+Registry data is untouched by an upgrade. A `schemaVersion` change requires a migration; V1 has none.
+
+## Remove
+
+Call `plugin_manager` with `action: remove_bundle` and `target: dsh-env-manager-plugin`.
+
+Registry data under `dataDir` is not deleted. Back it up if you may reinstall later.
+
+## Rollback
+
+1. Reinstall the previous checkout.
+2. Restart DSH.
+3. Restore `dataDir` from the backup if the previous version wrote incompatible records.
+
+V1 accepts only `schemaVersion: 1`; records written by an unknown version are skipped with a warning rather than corrupted.