@adhdev/mesh-shared 1.0.56-rc.18 → 1.0.56-rc.19
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/dist/index.js.map +1 -1
- package/dist/index.mjs.map +1 -1
- package/dist/node-facts.d.ts +15 -0
- package/package.json +1 -1
- package/src/node-facts.ts +15 -0
package/dist/node-facts.d.ts
CHANGED
|
@@ -75,6 +75,21 @@ export interface MeshNodeFactsProviderQuota {
|
|
|
75
75
|
* rather than presenting them as a freshly measured value.
|
|
76
76
|
*/
|
|
77
77
|
lastGoodWindows?: boolean;
|
|
78
|
+
/**
|
|
79
|
+
* Unix ms when the reporting node last ATTEMPTED a refresh of this
|
|
80
|
+
* provider — deliberately distinct from `updatedAt`, which dates the
|
|
81
|
+
* DATA. They differ for file-source providers (claude-cli reports its
|
|
82
|
+
* statusline snapshot's capture time, codex-cli the rollout entry's),
|
|
83
|
+
* whose `updatedAt` does not move while the source file is unchanged
|
|
84
|
+
* however often it is successfully re-read.
|
|
85
|
+
*
|
|
86
|
+
* A reader judging FRESHNESS wants `updatedAt`. This field answers the
|
|
87
|
+
* different question "is that node still looking?", which is what makes
|
|
88
|
+
* "3h old but re-checked a minute ago" distinguishable from "3h old and
|
|
89
|
+
* nobody has looked since". Absent on entries written by daemons
|
|
90
|
+
* predating the field.
|
|
91
|
+
*/
|
|
92
|
+
fetchedAt?: number;
|
|
78
93
|
[extra: string]: unknown;
|
|
79
94
|
};
|
|
80
95
|
[extra: string]: unknown;
|
package/package.json
CHANGED
package/src/node-facts.ts
CHANGED
|
@@ -78,6 +78,21 @@ export interface MeshNodeFactsProviderQuota {
|
|
|
78
78
|
* rather than presenting them as a freshly measured value.
|
|
79
79
|
*/
|
|
80
80
|
lastGoodWindows?: boolean
|
|
81
|
+
/**
|
|
82
|
+
* Unix ms when the reporting node last ATTEMPTED a refresh of this
|
|
83
|
+
* provider — deliberately distinct from `updatedAt`, which dates the
|
|
84
|
+
* DATA. They differ for file-source providers (claude-cli reports its
|
|
85
|
+
* statusline snapshot's capture time, codex-cli the rollout entry's),
|
|
86
|
+
* whose `updatedAt` does not move while the source file is unchanged
|
|
87
|
+
* however often it is successfully re-read.
|
|
88
|
+
*
|
|
89
|
+
* A reader judging FRESHNESS wants `updatedAt`. This field answers the
|
|
90
|
+
* different question "is that node still looking?", which is what makes
|
|
91
|
+
* "3h old but re-checked a minute ago" distinguishable from "3h old and
|
|
92
|
+
* nobody has looked since". Absent on entries written by daemons
|
|
93
|
+
* predating the field.
|
|
94
|
+
*/
|
|
95
|
+
fetchedAt?: number
|
|
81
96
|
[extra: string]: unknown
|
|
82
97
|
}
|
|
83
98
|
[extra: string]: unknown
|