@engineeros/connector 1.11.0 → 1.12.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.
package/README.md CHANGED
@@ -186,6 +186,18 @@ npx --yes @engineeros/connector@latest start --workspace .
186
186
  Credentials are stored per workspace under `~/.engineeros/connectors` with owner-only permissions where supported.
187
187
  If a new pairing command is accidentally run from the same folder against the same EngineerOS server, the connector reuses this saved identity instead of creating another baseline assessment.
188
188
 
189
+ ## Self-check
190
+
191
+ Connector 1.12.0 checks itself and reports the result to EngineerOS, so a local problem is visible in **Project steering -> Connect workspace** instead of only in this terminal. The checks cover the Node runtime, the saved pairing, whether the EngineerOS backend answers from this machine, whether the coding agent starts, the tool registry, and stuck local Goal jobs.
192
+
193
+ The report is sent when the connector connects, every five minutes while it is idle, and once more when a startup problem is about to stop it, which is the case EngineerOS could not see before: the workspace simply appeared offline. Run the same checks locally at any time, paired or not:
194
+
195
+ ```sh
196
+ npx --yes @engineeros/connector@latest doctor --workspace .
197
+ ```
198
+
199
+ The command prints every check with its reason and remedy, sends the report when the workspace is paired, and exits non-zero when a check failed.
200
+
189
201
  ## Local Git history
190
202
 
191
203
  Pairing or starting connector 0.31.0 initializes a local Git repository when the project has none and creates its initial commit from source files and durable design/assessment artifacts. An empty project also gets a usable baseline. Existing repositories and their pending source changes are preserved. Git must be installed; no remote is created and nothing is pushed.