You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`POST /analysis/author` (HTTP API) now supports the full `gitsema author` CLI flag surface: `since`, `detail`, `includeCommits`, `hybrid`, and `bm25Weight` are wired through to the same author-attribution logic the CLI uses, plus `chunks`/`level`/`vss` are accepted for flag-surface parity (no-op, matching the CLI's own behavior for these three). Breaking change: the response shape is now `{ authors, commits? }` instead of a bare array, to carry `includeCommits` results.
|`POST /api/v1/analysis/clusters`| Clustering — accepts `{model, textModel, codeModel}` overrides for CLI/HTTP flag parity (Phase 140), though `computeClusters()` doesn't filter by model so behavior is unchanged today |
Copy file name to clipboardExpand all lines: docs/parity.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -336,6 +336,11 @@ This table shows less common flags used by specific commands or command groups.
336
336
|`--include-content`|`evolution`, `concept-evolution`| bool | false | Add stored file text in JSON output |
337
337
|`--include-commits`|`first-seen`| bool | false | Also search commit messages |
338
338
|`--alerts`|`file-evolution`|[int]|`5`| Top-N largest semantic jumps with author/commit-URL enrichment; `true`/flag-only → default 5. Also `alerts: <n>` (required, no implicit default) on `POST /evolution/file` since Phase 139 |
339
+
|`--since`|`author`| date | — | Only consider contributions since this date (HTTP: also accepted by `POST /analysis/author`, Phase 141) |
340
+
|`--detail`|`author`| bool | false | Include per-blob contribution detail (HTTP: also accepted by `POST /analysis/author`, Phase 141) |
341
+
|`--hybrid`|`author`| bool | false | Use hybrid (vector + BM25) candidate selection (HTTP: also accepted by `POST /analysis/author`, Phase 141) |
342
+
|`--bm25-weight`|`author`| float | 0.3 | BM25 weight when `--hybrid` is set (HTTP: also accepted by `POST /analysis/author`, Phase 141) |
343
+
|`--chunks` / `--level` / `--vss`|`author`| bool/enum/bool | false/—/false | Declared on the CLI but not wired to anything in `computeAuthorContributions` (blob-level only); `--vss` prints a warning and is ignored. HTTP's `POST /analysis/author` accepts all three for flag-surface parity with the same no-op behavior (Phase 141) — not a gap, a documented CLI limitation mirrored intentionally. |
339
344
340
345
### 2.3 Flag Coherence Issues
341
346
@@ -569,7 +574,15 @@ this section's prior open-ended bullets into concrete, numbered
569
574
-**Phase 140:** systemic `--model`/`--text-model`/`--code-model` gap
570
575
across `analysis.ts` HTTP routes (one shared fix, not 8 per-route ones).
571
576
-**Phase 141:**`author` HTTP route full parity (largest single-command
572
-
gap found).
577
+
gap found). ✅ done — `POST /analysis/author` now accepts `since`,
578
+
`detail`, `includeCommits`, `hybrid`, `bm25Weight` (all wired to
579
+
`computeAuthorContributions`/`hybridSearch`/`searchCommits`, mirroring the
580
+
CLI `author` command exactly) plus `chunks`/`level`/`vss` for flag-surface
581
+
parity (accepted, no-op — matching the CLI's own dead-flag behavior for
582
+
these three). Response shape changed from a bare array to `{ authors,
583
+
commits? }` (breaking change, per §4's parity-over-stability rule) to
0 commit comments