@holmes-lab/holmes-kit 0.35.13 → 0.35.14
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/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
<!-- @implements A-SPEC-209 -->
|
|
8
|
+
## [0.35.14] - 2026-10-08
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- **The graph had almost no import edges for TypeScript projects that write `./x.js` for a `x.ts` source**
|
|
13
|
+
(A-SPEC-688.1). That spelling is the ES-module convention (mandatory under `moduleResolution: node16/nodenext`);
|
|
14
|
+
the resolver appended extensions to the name as written, found nothing, and emitted no edge. Measured on a public
|
|
15
|
+
TypeScript monorepo of 1,121 scanned files: 6,854 import relations in the scan, **3** `imports` edges in the
|
|
16
|
+
graph; with this release 4,628. `.js` resolves to `.ts` then `.tsx`, `.jsx` to `.tsx`, `.mjs` to `.mts`, `.cjs`
|
|
17
|
+
to `.cts`; a scanned file of the name as written still wins and only a scanned file is ever the answer. Projects
|
|
18
|
+
that write extensionless specifiers are unaffected (this repository: 1,194 edges before and after). The cycle
|
|
19
|
+
ratchet uses the same resolver and now sees these edges, so a project using the convention may be told about
|
|
20
|
+
import cycles it already had. The graph's extractor version is raised to `holmes-rtm/5`, so a graph cached by an
|
|
21
|
+
earlier build is rebuilt on first use. **What this does not change:** the graded impact list
|
|
22
|
+
(`impacts.rankedImpact`) is seeded from code nodes and does not walk file-to-file import edges, so its answers are
|
|
23
|
+
the same (measured: 4,625 added edges, 0 of 113 lists changed) — handing the import neighbourhood to the ranking
|
|
24
|
+
was measured separately and not adopted in the form tried. A workspace package name (`@scope/pkg`) is still not
|
|
25
|
+
resolved to its directory.
|
|
26
|
+
|
|
8
27
|
## [0.35.13] - 2026-10-08
|
|
9
28
|
|
|
10
29
|
### Changed
|
package/README.md
CHANGED
|
@@ -9,8 +9,8 @@
|
|
|
9
9
|
<!-- holmes-kit:attest:begin -->
|
|
10
10
|

|
|
11
11
|
|
|
12
|
-
**436/436** source files (100%) trace to an approved spec · **
|
|
13
|
-
Measured at `
|
|
12
|
+
**436/436** source files (100%) trace to an approved spec · **752/815** approved A-SPECs (92.2%) are anchored from code.
|
|
13
|
+
Measured at `d2852f9a42c2` (specs `sha256:2730ac4791a0`) — reproduce with `holmes-kit attest --exclude dist-tools/,docs/goals/probes/,reference/`.
|
|
14
14
|
<!-- holmes-kit:attest:end -->
|
|
15
15
|
|
|
16
16
|
---
|
|
@@ -23,6 +23,7 @@ Measured at `22ddb0979f45` (specs `sha256:5a9f37e1c454`) — reproduce with `hol
|
|
|
23
23
|
|
|
24
24
|
### 🛡️ Currently Supported Features (Production Features)
|
|
25
25
|
|
|
26
|
+
- **ES-module TypeScript projects get their import graph** *(new in 0.35.14 — fix)*: a specifier written `./x.js` for a `x.ts` source (the ESM convention) now resolves, where it used to emit no edge at all — on a public TypeScript monorepo the graph went from 3 import edges to 4,628 of 6,854 import relations. Extensionless projects are unchanged. The cycle ratchet sees the same edges. Workspace package names are still unresolved, and the graded impact list does not yet use import edges.
|
|
26
27
|
- **The impact list also knows where work is concentrating, and a release cannot ship a stale badge** *(new in 0.35.13)*: for a named change, `impacts.rankedImpact` is fused once more with each file's recency-weighted change frequency (same single `git log`; rows may carry `changeFrequency`). On 703 replayed changes neither corpus had been measured on before, recall among the ten rose 0.485 → 0.545 and 0.378 → 0.540 on a second, Python repository (both above the minimum detectable effect) and 0.521 → 0.551 / 0.419 → 0.477 here; precision rose detectably on all four windows. Stated plainly: against the modelled human engineer this project aims at (`docs/NORTH-STAR.md` — recall 0.67–0.78, precision ≈ 0.9) recall is still below the band and precision about a sixth. Separately, `npm publish` now refuses when the README shows the attest badge and `.ax/badges/traced.svg` was not re-measured since the previous release.
|
|
27
28
|
- **What else moves when you change this file — ranked by history too** *(new in 0.35.12)*: when `maintenance_analyze` is given `changedFiles`, its graded impact list (`impacts.rankedImpact`) fuses the call-graph ranking with recency-weighted co-change from git history (files committed together with the changed ones, recent commits counting more). On replayed changes of a second, Python repository a file that really changed with the named one is among the ten shown with recall 0.44 instead of 0.34 (beyond the minimum detectable difference, and replicated on further changes); on this repository the difference is positive and not detectable. Walking the call graph deeper was measured at the same time and not adopted: it reaches more and ranks worse.
|
|
28
29
|
- **The graph states what the code does, and intake answers in one call** *(new in 0.35.11)*: three corrections to what the traceability graph and `requirement_triage` say, each measured before it was built. `requirement_triage` ranked every requirement lineage on the first 64 distinct words of its text; it now reads the whole text (right lineage in the top five: 0.28 → 0.66 on this repository, 0.76 → 0.85 on a second one, both beyond the minimum detectable difference). A call with `persist: true` waits up to 20 seconds for the refresh it requested instead of returning `ambiguous` and asking to be repeated (`HOLMES_TRIAGE_WAIT_MS` sets the bound, 0 turns it off). `maintenance_analyze` lists `relevantTests` in relevance order — tests named after the changed file first — so the ten a bounded response shows are no longer the alphabetically first ten (a test the change also touched is among them with recall 0.48 instead of 0.21 here). TypeScript `calls` edges are bound by the compiler's symbol resolution — 21% of the name-bound edges linked a standard-library call such as `xs.map()` to an unrelated symbol — using only the files the scan already read plus TypeScript's bundled library; and an `@implements` anchor written in or directly above a function links the spec to that function instead of to every function of the file. **What is not claimed:** on replayed changes neither graph correction moved what `maintenance_analyze` returns beyond the minimum detectable difference; they change what the graph states, and the CHANGELOG records one measured cost.
|
package/dist/.build-id
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
7bc430d2-muyiyuem
|
|
@@ -34,7 +34,7 @@ var __importStar = (this && this.__importStar) || (function () {
|
|
|
34
34
|
})();
|
|
35
35
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
36
36
|
exports.createImportResolver = createImportResolver;
|
|
37
|
-
// @implements A-SPEC-688
|
|
37
|
+
// @implements A-SPEC-688, A-SPEC-688.1
|
|
38
38
|
/**
|
|
39
39
|
* The ONE place an import specifier becomes a scanned file path.
|
|
40
40
|
*
|
|
@@ -71,7 +71,29 @@ function createImportResolver(scanned, opts) {
|
|
|
71
71
|
const known = new Set(scanned.map((f) => f.sourcePath));
|
|
72
72
|
const EXTENSIONS = ['', '.ts', '.tsx', '.mts', '.cts', '.js', '.mjs', '.cjs', '.jsx', '.py',
|
|
73
73
|
'/index.ts', '/index.js', '/__init__.py'];
|
|
74
|
-
const
|
|
74
|
+
const firstKnownAsWritten = (base) => EXTENSIONS.map((ext) => `${base}${ext}`).find((candidate) => known.has(candidate)) ?? null;
|
|
75
|
+
// @implements A-SPEC-688.1 — the ESM convention: TypeScript that emits ES modules writes
|
|
76
|
+
// `./memory.js` for the source file `memory.ts`, and the compiler resolves it that way. Appending
|
|
77
|
+
// extensions to the name as written (`memory.js.ts`) finds nothing. Measured on a public
|
|
78
|
+
// TypeScript monorepo: 6,854 import relations, 3 edges; with this rule 4,628. A scanned file of
|
|
79
|
+
// the name as written still wins, and only a scanned file is ever the answer.
|
|
80
|
+
const SOURCE_OF_EMITTED = [
|
|
81
|
+
['.js', ['.ts', '.tsx']], ['.jsx', ['.tsx']], ['.mjs', ['.mts']], ['.cjs', ['.cts']],
|
|
82
|
+
];
|
|
83
|
+
const firstKnown = (base) => {
|
|
84
|
+
const asWritten = firstKnownAsWritten(base);
|
|
85
|
+
if (asWritten !== null)
|
|
86
|
+
return asWritten;
|
|
87
|
+
for (const [emitted, sources] of SOURCE_OF_EMITTED) {
|
|
88
|
+
if (!base.endsWith(emitted))
|
|
89
|
+
continue;
|
|
90
|
+
const stem = base.slice(0, -emitted.length);
|
|
91
|
+
const source = sources.map((ext) => `${stem}${ext}`).find((candidate) => known.has(candidate));
|
|
92
|
+
if (source !== undefined)
|
|
93
|
+
return source;
|
|
94
|
+
}
|
|
95
|
+
return null;
|
|
96
|
+
};
|
|
75
97
|
// A-SPEC-525.1 — the five languages' resolution rules, selected by the IMPORTING file's
|
|
76
98
|
// extension because resolution IS per-language semantics. The founding rule is unchanged
|
|
77
99
|
// everywhere: resolve only to files the scan actually contains; the ambiguous resolve to none.
|
|
@@ -39,7 +39,7 @@ exports.warmRequirementSemanticCache = warmRequirementSemanticCache;
|
|
|
39
39
|
exports.headOf = headOf;
|
|
40
40
|
exports.refreshSemanticVectors = refreshSemanticVectors;
|
|
41
41
|
exports.createGraphOperationsHandlers = createGraphOperationsHandlers;
|
|
42
|
-
// @implements A-SPEC-719, A-SPEC-734, A-SPEC-741.1, A-SPEC-758.1
|
|
42
|
+
// @implements A-SPEC-719, A-SPEC-734, A-SPEC-741.1, A-SPEC-758.1, A-SPEC-688.1
|
|
43
43
|
// @implements A-SPEC-614, A-SPEC-613, A-SPEC-100.2, A-SPEC-121.2, A-SPEC-128, A-SPEC-139, A-SPEC-189, A-SPEC-280, A-SPEC-282, A-SPEC-283, A-SPEC-419, A-SPEC-433, A-SPEC-469, A-SPEC-478, A-SPEC-568.1, A-SPEC-568.2, A-SPEC-569.1, A-SPEC-569.2, A-SPEC-569.3, A-SPEC-589
|
|
44
44
|
// @implements A-SPEC-632
|
|
45
45
|
const fs = __importStar(require("node:fs"));
|
|
@@ -74,7 +74,9 @@ const SUMMARY_CAP = 40;
|
|
|
74
74
|
// @implements A-SPEC-756.2 — /3: the extractor binds anchors to functions by place.
|
|
75
75
|
// @implements A-SPEC-758.1 — /4: TypeScript `calls` edges are bound by the compiler; a /3 store holds
|
|
76
76
|
// library calls linked to unrelated symbols by name and is rebuilt.
|
|
77
|
-
|
|
77
|
+
// @implements A-SPEC-688.1 — /5: `.js` specifiers resolve to their TypeScript sources, so a graph
|
|
78
|
+
// cached by an earlier build lacks those import edges.
|
|
79
|
+
const RTM_EXTRACTOR_VERSION = 'holmes-rtm/5';
|
|
78
80
|
// @implements A-SPEC-632 — the two rebuild paths a completed integration's discharge runs are the
|
|
79
81
|
// SAME functions explicit reindex runs, so a discharged graph and a reindexed graph are one artifact.
|
|
80
82
|
/** Publish the complete graph for `specs` over `scanned` at the live path (A-SPEC-631 primitive). */
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"//": "@implements A-SPEC-209",
|
|
3
3
|
"name": "@holmes-lab/holmes-kit",
|
|
4
|
-
"version": "0.35.
|
|
4
|
+
"version": "0.35.14",
|
|
5
5
|
"description": "Holmes-Kit — deterministic Agentic Software Engineering (ASE) harness with causal traceability (spec chain + D-CPG + RTM + phase guardrail)",
|
|
6
6
|
"main": "dist/holmes/mcp/server.js",
|
|
7
7
|
"types": "dist/holmes/mcp/server.d.ts",
|