@titan-design/session-graph 0.9.0 → 0.9.1
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 +10 -4
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -5,8 +5,8 @@ buckets, permission phases, touched files, branches, PRs, subagents, and the edg
|
|
|
5
5
|
them, all in one SQLite file built from `@titan-design/store-sqlite` kit tables and kept
|
|
6
6
|
current incrementally.
|
|
7
7
|
|
|
8
|
-
Tier 2 of the titan-platform DAG. Depends on `session-read`, `store-sqlite`,
|
|
9
|
-
`cluster`. Extracted from active-work's session index (AW-23, TP-6).
|
|
8
|
+
Tier 2 of the titan-platform DAG. Depends on `session-read`, `store-sqlite`,
|
|
9
|
+
`cluster`, `locator`, and `agent-protocol`. Extracted from active-work's session index (AW-23, TP-6).
|
|
10
10
|
|
|
11
11
|
```ts
|
|
12
12
|
import { discoverTranscripts } from "@titan-design/session-read";
|
|
@@ -100,8 +100,9 @@ await refreshCorpus(graph, transcripts, {
|
|
|
100
100
|
- **Failure.** Same as the task resolver: the pass completes, the rows stand, and
|
|
101
101
|
`summary.prs` carries `failed` plus `error`.
|
|
102
102
|
|
|
103
|
-
`reconcile`
|
|
104
|
-
|
|
103
|
+
`reconcile` sets `merged_at` from merge sightings only for a PR the resolver has not yet
|
|
104
|
+
checked. Once the resolver has answered for a PR, its `merged_at` is the forge's and a later
|
|
105
|
+
pass never overwrites it with a sighting time.
|
|
105
106
|
|
|
106
107
|
## Tables
|
|
107
108
|
|
|
@@ -169,6 +170,11 @@ empty tables, so existing rows are untouched.
|
|
|
169
170
|
and latest `effective_from`; an unmatched model reads `priced = 0` and costs 0.
|
|
170
171
|
`context_contribution` attributes each request's context growth to the blocks before it.
|
|
171
172
|
|
|
173
|
+
Migration 6, `episode transcript ids`, adds nullable `start_transcript_id` and
|
|
174
|
+
`end_transcript_id` columns to `episode`, surfaced as `EpisodeRow.startTranscriptId` and
|
|
175
|
+
`endTranscriptId`. A session resumed across two transcripts then orders by timestamp,
|
|
176
|
+
transcript id, and byte offset, because byte offsets reset with the new file.
|
|
177
|
+
|
|
172
178
|
For snapshot-only usage across multiple physical sources, queries select one source
|
|
173
179
|
by latest native usage timestamp, then greatest usage-record coverage and stable
|
|
174
180
|
source ID. Source-local reset epochs cannot safely be summed across copies. This is
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@titan-design/session-graph",
|
|
3
|
-
"version": "0.9.
|
|
3
|
+
"version": "0.9.1",
|
|
4
4
|
"description": "Fold session events into the activity graph on store-sqlite",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -33,9 +33,9 @@
|
|
|
33
33
|
"dependencies": {
|
|
34
34
|
"@titan-design/cluster": "^0.1.2",
|
|
35
35
|
"@titan-design/locator": "^0.2.1",
|
|
36
|
-
"@titan-design/session-read": "^0.5.
|
|
36
|
+
"@titan-design/session-read": "^0.5.1",
|
|
37
37
|
"@titan-design/store-sqlite": "^0.3.1",
|
|
38
|
-
"@titan-design/agent-protocol": "^0.
|
|
38
|
+
"@titan-design/agent-protocol": "^0.2.0"
|
|
39
39
|
},
|
|
40
40
|
"scripts": {
|
|
41
41
|
"build": "tsup",
|