@engineeros/connector 1.28.0 → 1.29.1

package/README.md

@@ -31,6 +31,8 @@ The runner stops and records a resumable failure after ten minutes without agent
 
 There is no wall-clock execution cutoff. Runs stop after at most two repair-and-review cycles following the initial review. The inactivity safeguard above still stops a silent agent; waiting for your answer does not consume a repair cycle. Successful results awaiting upload are not executed again.
 
+Before the independent checks, the connector runs each frozen `command` Proof itself in the Goal worktree and sends the measured exit code, duration, best-effort pass/fail/skip counts and a 4000-character log tail as `test_run` evidence (`measured_by: "connector"`). A non-zero exit, or an exit 0 whose recognised summary counted no tests, fails that Proof and starts a repair cycle; the result is saved per revision so a resumed run does not run it again. Commands that need a shell (`&&`, pipes, redirects, globs), and commands whose executable is not installed, are not run and stay with the independent verifier. Each command and everything it started stops after 15 minutes unless `ENGINEEROS_TEST_COMMAND_TIMEOUT_MS` says otherwise, and a command that exits is measured even when a leftover process still holds its output. The implementation agent is told to add or update automated tests with its code, and the verifier and reviewer fail a change whose behavior has no tests.
+
 ### Delete a Goal and its sandboxes
 
 Choose **Delete Goal** in the Goal detail header and confirm. This deletes all revisions, runs, receipts, proof results, attachments and run questions for that Goal. Connected runners first stop every run in the revision family, then remove owned isolated Git worktrees (including uncommitted sandbox files), checkpoints, queued dispatches and logs. The source repository, its local changes, Git branches and unrelated worktrees are preserved. External registered worktrees require their matching saved checkpoints to establish ownership. Manually managed external environments remain the external runner's responsibility.
@@ -249,7 +251,7 @@ restored before resuming. Submitted results and final acceptance receipts retain
 
 The connector keeps a local index for each workspace under `~/.engineeros/context/<connector id>/workspaces/`: file classifications, symbols, document headings, and import relationships for every safe file. Separating indexes by resolved workspace keeps the source checkout and concurrent Goal worktrees from replacing one another. An index is built at onboarding, refreshed incrementally from file digests when EngineerOS triggers a workspace refresh, and re-checked before every assignment. Symbols in Python, JavaScript, TypeScript, Go, Java, Rust, Ruby and PHP come from tree-sitter syntax trees, using grammars shipped with the connector, so methods inside classes are indexed and `engineeros_read_symbol` returns exactly one declaration; other languages use line patterns.
 
-Before a workspace assessment stage runs, the connector also extracts repository facts from that index without a model: routes and pages, data models and migrations, integrations declared in dependency manifests, configuration keys, delivery and runtime files, and files that check authentication. They are cached per commit in `.engineeros/context/repository-facts.md`. Each stage receives the slice it starts from, and the capability catalog receives draft capability areas with their locations, so stages confirm a known inventory instead of rediscovering it.
+Before a workspace assessment stage runs, the connector also extracts repository facts from that index without a model: routes and pages, data models and migrations, integrations declared in dependency manifests, configuration keys, delivery and runtime files, and files that check authentication. They are cached per commit in `.engineeros/context/repository-facts.json`. Each stage receives only a bounded slice of the facts it starts from, with no full copy for an agent to read at once, and the capability catalog receives draft capability areas with their locations, so stages confirm a known inventory instead of rediscovering it.
 
 Every assignment prompt arrives with a bounded, task-ranked Markdown working set. It names the most relevant paths, symbol and heading locations, local dependencies, direct consumers, and candidate tests, followed by a pointer to the durable source map at `.engineeros/context/source-map.md`. The connector ranks from the assignment's focused context query, frozen Goal packet, assessment stage identity, or current project request as appropriate. It never pastes source-file contents into the prompt; the Agent reads deeper through the source map, the listed files, assessment sections, ordinary file tools, or the attached `engineeros_*` MCP tools. Ranking is structural and lexical, using indexed paths, symbols, summaries, and imports; it does not generate or store embeddings.