dsh-env-manager-plugin 0.1.0 → 0.1.2

package/cordis.patch.yml

@@ -1,4 +1,4 @@
-- insert:
-    - id: dsh-env-manager
-      name: dsh-env-manager-plugin
-      config: {}
+- insert:
+    - id: dsh-env-manager
+      name: dsh-env-manager-plugin
+      config: {}

package/docs/00-project/current-state.md

@@ -11,7 +11,7 @@ surfaces.**
 
 The V1 Host is implemented in TypeScript under `src/` and compiled to `lib/`. Storage,
 registry, resolver, router, session store, application service, ten tools and the
-same-origin HTTP API are in place, with 50 Vitest tests passing. The Client panel is
+same-origin HTTP API are in place, with 51 Vitest tests passing. The Client panel is
 implemented in `client.js` and its sidebar/main slot registrations are live. The sidebar
 glyph follows the host `sidebar.panellist` contract: it honors the owner's
 `size`/`active` props and renders monochrome with `currentColor`; the contract is recorded
@@ -31,11 +31,37 @@ the tarball, publishes with npm Trusted Publisher/OIDC, and creates a GitHub Rel
 The first publish must be bootstrapped manually before Trusted Publisher can be bound;
 the exact steps are in [`release.md`](../06-operations/release.md).
 
-**Release status (2026-11-01):** the GitHub `Release` workflow is active
-(`release.yml`, workflow ID `403656649`), but the npm package
-`dsh-env-manager-plugin` is not published yet. Bootstrap is waiting for a valid npm OTP
-(`EOTP`); after the `0.0.0-stage` bootstrap and Trusted Publisher binding, tag `v0.1.0`
-will publish the real package.
+**Release status (2026-11-01):** `dsh-env-manager-plugin@0.1.0` is published and is the
+`latest` npm tag (`gitHead` `4d884e7`). The
+[GitHub Release v0.1.0](https://github.com/zhiwuli0228/dsh-env-manager/releases/tag/v0.1.0)
+contains `dsh-env-manager-plugin-0.1.0.tgz`; workflow run
+[`41323001406`](https://github.com/zhiwuli0228/dsh-env-manager/actions/runs/41323001406)
+completed successfully. The 0.1.0 publish itself was bootstrapped manually; the workflow
+detected the existing version, skipped npm publish, and created the Release. Later versions
+use npm Trusted Publisher/OIDC through the same workflow.
+
+**Plugin directory:** submitted to
+[`awesome-dsh-plugin/awesome-dsh-plugin`](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
+as PR [#11185](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/11185)
+(`data/plugins/zhiwuli0228__dsh-env-manager.yml`, category `dev`). The repository has the
+`dsh-plugin` topic; the listing is pending CI/review.
+
+**Installation smoke test (2026-11-02):** removed the old local bundle
+`dsh-env-manager` from the `desktop` profile, including its package dependency, bundle
+entry, lockfile reference and stale `node_modules/dsh-env-manager` symlink. Reinstalled
+the published package as `dsh-env-manager-plugin@0.1.0` from npm. The discovery Skill,
+ten tools, sidebar panel and `/env-manager/api` transport all came back; the API reported
+the preserved registry data (2 environments, 3 services, 3 deployments, 0 rule profiles,
+0 operation bindings) and no warnings. Registry data was intentionally not deleted during
+uninstall.
+
+**Install hardening (2026-11-03):** reproduced the reported failure from a clean clone:
+`lib/` was git-ignored, so a checkout installed without a build had no `lib/index.js`.
+The compiled `lib/` tree is now committed, `index.js` reports a specific missing-build
+error, and the install docs use `plugin_manager install_bundle` instead of the
+dependency-only `dsh plugin add` command. `scripts/repair-profile.mjs` detects duplicate
+or legacy bundle entries and offers an atomic `--fix` with a backup. The published
+`0.1.0` npm tarball already contained `lib/`; this fixes checkout and git installs.
 
 The panel uses a centered 1080 px column, 22 px title with a glyph mark, underline tabs,
 compact stat cards and a master/detail environment view. **Environments is the first and

package/docs/00-project/glossary.md

@@ -1,215 +1,215 @@
-# Glossary
-
-## Environment
-
-One complete network and one configuration page, such as `dev`, `test-a`, `staging` or
-`production`.
-
-Contains the role catalogue, hosts, clusters and access endpoints in one record. An
-environment must declare at least one logical role; the panel seeds management, business,
-database and expansion by default.
-
-## Plane
-
-A role view over an environment's nodes: management, business, database or expansion.
-
-A plane is **not** a separate environment and has no node copies. Opening a plane tab
-filters the environment's single `hosts[]` collection. A node that serves two planes is one
-host with two roles.
-
-## Node
-
-The user-facing name for a host inside an environment. See **Host**.
-
-## Host
-
-A single compute machine inside one environment: a VM, physical machine, Kubernetes node or
-Pod-hosting machine. A Pod is not a Host.
-
-Attributes: hostname, kind, OS, IP, SSH port, roles, command access and a `credentialRef`. A
-host must declare at least one role; it may carry several roles, which is how co-location is
-expressed. It may have zero accounts, or accounts that each carry their own `credentialRef`.
-
-## Node Kind
-
-The machine classification on `Host.kind`: `vm`, `physical`, `k8s-all-in-one`, `k8s-worker`
-or `pod-host`. It describes how the machine participates in the deployment, not which
-logical plane it serves. A missing kind reads as `vm`.
-
-## Command Surface
-
-The command entry points available on a host, recorded in `Host.access`: `ssh`, `kubectl`
-or `docker`. This is capability metadata, not an authorization grant and not a credential.
-
-## Pod Host
-
-A machine running Pods that operators reach with `docker exec`, recorded as
-`Host.kind: pod-host`. It is one Host even when it runs many Pods; individual Pods belong to
-the deployment model, not `hosts[]`.
-
-## Web Login
-
-A management or business console login recorded on `HostAccount`: `loginUrl` is the console
-entry URL, `username` is the login name and `credentialRef` points to the password in the
-DSH credential service. The URL is configuration, never a secret; the password is never
-stored in the environment YAML.
-
-## Cluster
-
-A Kubernetes or Docker cluster inside one environment.
-
-Attributes: kind, optional topology (`all-in-one`, `separate` or `external`), API endpoint,
-namespaces and a `credentialRef`. Kubernetes and Pod-host nodes reference it through
-`Host.clusterRef`.
-
-## Cluster Topology
-
-A descriptive label on `Cluster.topology`:
-
-- `all-in-one` — control plane and worker on the same machine;
-- `separate` — dedicated control plane and worker machines;
-- `external` — a cluster managed outside this environment.
-
-Per-host `Host.kind` is authoritative; topology does not replace it.
-
-## Logical Role
-
-A named function a host can serve, such as `management`, `business`, `database` or
-`extension`.
-
-Hosts and roles are many-to-many via `Host.roles`. Standard role ids are seeded on
-environment creation; custom ids are allowed but must be declared before use.
-
-## Service
-
-A deployable software component described independently of any environment.
-
-Attributes: id, name, aliases, category, Git URL and branch, build tool, artifact name, supported deploy modes and ordered rule profile references.
-
-## Deployment Binding
-
-The relationship "this service runs here, in this runtime mode".
-
-One service may have several bindings in one environment, so `(environmentId, serviceId)` is not unique.
-
-## Runtime Mode
-
-`native`, `docker` or `kubernetes`. Determines which location fields and which log source apply.
-
-## Rule Profile
-
-A reusable set of variables, paths, log sources and class locations.
-
-Referenced by services in order; later profiles win on field conflicts.
-
-## Rule Override
-
-A field-level override carried by an environment or a deployment.
-
-Overriding one field leaves the other fields of the profile intact.
-
-## Rule Layer
-
-One of `global`, `service`, `environment`, `deployment`, in ascending priority.
-
-## Template
-
-A string containing `${...}` references, resolved by interpolation only.
-
-No functions, operators, conditionals or shell execution.
-
-## Provenance
-
-The explanation attached to a resolved value:
-
-- `definedBy` — the layer and profile that supplied the winning template;
-- `inputs` — referenced fields and the layer that supplied each;
-- `shadowed` — lower-priority definitions that lost.
-
-## Derived Value
-
-A value produced by rule resolution. It is not evidence that a file or endpoint exists.
-
-## Verified Value
-
-A value confirmed by an online check. V1 does not produce verified values.
-
-## Service Context
-
-The structured result of resolving an environment, service, deployment, rules and credential status.
-
-Returned by `env_resolve`.
-
-## Operation Binding
-
-A predicate mapping an operation in a given context to a specific Skill, with parameter templates and policy.
-
-## Match Level
-
-How specific a binding is: `deployment`, `environment-service`, `service`, `category-mode`, `global`.
-
-Higher levels win; same-level ties are conflicts.
-
-## Skill Reference
-
-A pointer to a DSH Skill: name, optional expected source and provider.
-
-It is discovery information, not execution authorization.
-
-## Approval Policy
-
-The `requiresApproval` and `allowProduction` fields on a binding.
-
-Write operations default to requiring approval; production defaults to denied.
-
-## Credential Reference
-
-A `credentialRef` string stored in a registry record.
-
-The value behind it lives in the DSH credential service or an external vault and is never returned by this plugin.
-
-## Credential Status
-
-`configured`, `missing` or `unavailable`, obtained from the credential service without reading the value.
-
-## Session Context
-
-The per-session default environment.
-
-Advisory only; it never changes registry records or another session's state.
-
-## Operation Record
-
-A structured, redacted description of a performed operation: scope, operation, Skill reference, timing, outcome, evidence references and summary.
-
-Owned by the memory plugin from P1 onward.
-
-## Evidence Reference
-
-An opaque, sanitized pointer to evidence produced during an operation.
-
-Not the evidence itself.
-
-## Memory Scope
-
-The environment/service/deployment scope attached to a memory query or record.
-
-Prevents a single-environment conclusion from becoming a global rule.
-
-## Memory Bridge
-
-The optional adapter between this plugin and the memory plugin.
-
-Introduces no second store of environment facts and applies nothing automatically.
-
-## Review Queue
-
-The place where candidate rule or Skill changes wait for a human decision.
-
-## Source of Truth
-
-The durable data representation. Here: YAML registry files under the plugin data directory.
-
-## Harness
-
-The project-level control system for AI-assisted development: context rules, constraints, execution and verification policies, and continuity practices.
+# Glossary
+
+## Environment
+
+One complete network and one configuration page, such as `dev`, `test-a`, `staging` or
+`production`.
+
+Contains the role catalogue, hosts, clusters and access endpoints in one record. An
+environment must declare at least one logical role; the panel seeds management, business,
+database and expansion by default.
+
+## Plane
+
+A role view over an environment's nodes: management, business, database or expansion.
+
+A plane is **not** a separate environment and has no node copies. Opening a plane tab
+filters the environment's single `hosts[]` collection. A node that serves two planes is one
+host with two roles.
+
+## Node
+
+The user-facing name for a host inside an environment. See **Host**.
+
+## Host
+
+A single compute machine inside one environment: a VM, physical machine, Kubernetes node or
+Pod-hosting machine. A Pod is not a Host.
+
+Attributes: hostname, kind, OS, IP, SSH port, roles, command access and a `credentialRef`. A
+host must declare at least one role; it may carry several roles, which is how co-location is
+expressed. It may have zero accounts, or accounts that each carry their own `credentialRef`.
+
+## Node Kind
+
+The machine classification on `Host.kind`: `vm`, `physical`, `k8s-all-in-one`, `k8s-worker`
+or `pod-host`. It describes how the machine participates in the deployment, not which
+logical plane it serves. A missing kind reads as `vm`.
+
+## Command Surface
+
+The command entry points available on a host, recorded in `Host.access`: `ssh`, `kubectl`
+or `docker`. This is capability metadata, not an authorization grant and not a credential.
+
+## Pod Host
+
+A machine running Pods that operators reach with `docker exec`, recorded as
+`Host.kind: pod-host`. It is one Host even when it runs many Pods; individual Pods belong to
+the deployment model, not `hosts[]`.
+
+## Web Login
+
+A management or business console login recorded on `HostAccount`: `loginUrl` is the console
+entry URL, `username` is the login name and `credentialRef` points to the password in the
+DSH credential service. The URL is configuration, never a secret; the password is never
+stored in the environment YAML.
+
+## Cluster
+
+A Kubernetes or Docker cluster inside one environment.
+
+Attributes: kind, optional topology (`all-in-one`, `separate` or `external`), API endpoint,
+namespaces and a `credentialRef`. Kubernetes and Pod-host nodes reference it through
+`Host.clusterRef`.
+
+## Cluster Topology
+
+A descriptive label on `Cluster.topology`:
+
+- `all-in-one` — control plane and worker on the same machine;
+- `separate` — dedicated control plane and worker machines;
+- `external` — a cluster managed outside this environment.
+
+Per-host `Host.kind` is authoritative; topology does not replace it.
+
+## Logical Role
+
+A named function a host can serve, such as `management`, `business`, `database` or
+`extension`.
+
+Hosts and roles are many-to-many via `Host.roles`. Standard role ids are seeded on
+environment creation; custom ids are allowed but must be declared before use.
+
+## Service
+
+A deployable software component described independently of any environment.
+
+Attributes: id, name, aliases, category, Git URL and branch, build tool, artifact name, supported deploy modes and ordered rule profile references.
+
+## Deployment Binding
+
+The relationship "this service runs here, in this runtime mode".
+
+One service may have several bindings in one environment, so `(environmentId, serviceId)` is not unique.
+
+## Runtime Mode
+
+`native`, `docker` or `kubernetes`. Determines which location fields and which log source apply.
+
+## Rule Profile
+
+A reusable set of variables, paths, log sources and class locations.
+
+Referenced by services in order; later profiles win on field conflicts.
+
+## Rule Override
+
+A field-level override carried by an environment or a deployment.
+
+Overriding one field leaves the other fields of the profile intact.
+
+## Rule Layer
+
+One of `global`, `service`, `environment`, `deployment`, in ascending priority.
+
+## Template
+
+A string containing `${...}` references, resolved by interpolation only.
+
+No functions, operators, conditionals or shell execution.
+
+## Provenance
+
+The explanation attached to a resolved value:
+
+- `definedBy` — the layer and profile that supplied the winning template;
+- `inputs` — referenced fields and the layer that supplied each;
+- `shadowed` — lower-priority definitions that lost.
+
+## Derived Value
+
+A value produced by rule resolution. It is not evidence that a file or endpoint exists.
+
+## Verified Value
+
+A value confirmed by an online check. V1 does not produce verified values.
+
+## Service Context
+
+The structured result of resolving an environment, service, deployment, rules and credential status.
+
+Returned by `env_resolve`.
+
+## Operation Binding
+
+A predicate mapping an operation in a given context to a specific Skill, with parameter templates and policy.
+
+## Match Level
+
+How specific a binding is: `deployment`, `environment-service`, `service`, `category-mode`, `global`.
+
+Higher levels win; same-level ties are conflicts.
+
+## Skill Reference
+
+A pointer to a DSH Skill: name, optional expected source and provider.
+
+It is discovery information, not execution authorization.
+
+## Approval Policy
+
+The `requiresApproval` and `allowProduction` fields on a binding.
+
+Write operations default to requiring approval; production defaults to denied.
+
+## Credential Reference
+
+A `credentialRef` string stored in a registry record.
+
+The value behind it lives in the DSH credential service or an external vault and is never returned by this plugin.
+
+## Credential Status
+
+`configured`, `missing` or `unavailable`, obtained from the credential service without reading the value.
+
+## Session Context
+
+The per-session default environment.
+
+Advisory only; it never changes registry records or another session's state.
+
+## Operation Record
+
+A structured, redacted description of a performed operation: scope, operation, Skill reference, timing, outcome, evidence references and summary.
+
+Owned by the memory plugin from P1 onward.
+
+## Evidence Reference
+
+An opaque, sanitized pointer to evidence produced during an operation.
+
+Not the evidence itself.
+
+## Memory Scope
+
+The environment/service/deployment scope attached to a memory query or record.
+
+Prevents a single-environment conclusion from becoming a global rule.
+
+## Memory Bridge
+
+The optional adapter between this plugin and the memory plugin.
+
+Introduces no second store of environment facts and applies nothing automatically.
+
+## Review Queue
+
+The place where candidate rule or Skill changes wait for a human decision.
+
+## Source of Truth
+
+The durable data representation. Here: YAML registry files under the plugin data directory.
+
+## Harness
+
+The project-level control system for AI-assisted development: context rules, constraints, execution and verification policies, and continuity practices.