@camstack/addon-export-google 0.1.47 → 0.1.48
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.
|
@@ -18660,11 +18660,30 @@ var SensorEventSchema = object({
|
|
|
18660
18660
|
value: record(string(), unknown()).nullable(),
|
|
18661
18661
|
timestamp: number()
|
|
18662
18662
|
});
|
|
18663
|
+
/**
|
|
18664
|
+
* One stored sighting on a track's trajectory.
|
|
18665
|
+
*
|
|
18666
|
+
* The array these live in is returned in TIME order (D399) — it is APPENDED in
|
|
18667
|
+
* arrival order, and the two detector passes interleave, so a consumer must not
|
|
18668
|
+
* assume the two are the same on a row written by an older build.
|
|
18669
|
+
*/
|
|
18663
18670
|
var TrackPositionSchema = object({
|
|
18664
18671
|
x: number(),
|
|
18665
18672
|
y: number(),
|
|
18666
18673
|
timestamp: number(),
|
|
18667
|
-
bbox: BoundingBoxSchema
|
|
18674
|
+
bbox: BoundingBoxSchema,
|
|
18675
|
+
/**
|
|
18676
|
+
* Which detector pass measured this box (D399): `frame` is the full-frame
|
|
18677
|
+
* pass on the analysis raster, `recovery` is the native-resolution
|
|
18678
|
+
* small-subject second pass (D377/D378). Both write into one array, and until
|
|
18679
|
+
* this field existed the only way to tell them apart was that full-frame boxes
|
|
18680
|
+
* are exact multiples of 1.2 while recovery boxes are full-precision floats.
|
|
18681
|
+
* Absent on rows written before D399.
|
|
18682
|
+
*/
|
|
18683
|
+
source: _enum(["frame", "recovery"]).optional(),
|
|
18684
|
+
/** Detection score of this box, so a position can be weighed and not only
|
|
18685
|
+
* plotted. Absent on rows written before D399. */
|
|
18686
|
+
score: number().optional()
|
|
18668
18687
|
});
|
|
18669
18688
|
var TrackSnapshotSchema = object({
|
|
18670
18689
|
timestamp: number(),
|
|
@@ -19064,14 +19083,25 @@ var TrackSchema = object({
|
|
|
19064
19083
|
*/
|
|
19065
19084
|
hasRider: boolean().optional(),
|
|
19066
19085
|
/**
|
|
19067
|
-
* WHY this track ended without a NATIVE best-shot
|
|
19068
|
-
* ([D276](../decisions/adr-0276-a-stand-in-tile-is-provisional-and-a-close-says-why.md)
|
|
19086
|
+
* WHY this track ended without a NATIVE best-shot FRAME
|
|
19087
|
+
* ([D276](../decisions/adr-0276-a-stand-in-tile-is-provisional-and-a-close-says-why.md),
|
|
19088
|
+
* widened by [D400](../decisions/adr-0400-the-picture-is-judged-on-what-is-delivered.md)) —
|
|
19069
19089
|
* a composed token line (`no-key-frame capture=keyframe:native-missx4`,
|
|
19070
|
-
* `derive-returned-null tile=standin`,
|
|
19071
|
-
*
|
|
19072
|
-
*
|
|
19090
|
+
* `derive-returned-null tile=standin`,
|
|
19091
|
+
* `native-tile tile=native no-key-frame-at-close`, …) written at close and
|
|
19092
|
+
* CLEARED by the late-keyFrame upgrade when a native tile lands after all.
|
|
19093
|
+
* The operator-facing answer to "perché manca l'immagine?" on a track whose
|
|
19073
19094
|
* tile is a face/plate stand-in, a raster crop, or an icon.
|
|
19074
19095
|
*
|
|
19096
|
+
* **`no-key-frame-at-close` (D400).** The line used to be written ONLY when
|
|
19097
|
+
* the TILE ranked below native, so a track whose thumbnail landed natively
|
|
19098
|
+
* while its key frame missed carried no reason at all — three of the four
|
|
19099
|
+
* `MISSING_KEYFRAME` tracks in the 2026-09-07 operator audit were exactly
|
|
19100
|
+
* that shape, and their "niente ultimo" had no cause anywhere on the row.
|
|
19101
|
+
* The key frame is the head of a cascade (`keyFrame ⇒ keyFrameSmall ⇒ the
|
|
19102
|
+
* lastFrame copy source`), so its absence is now on this line whatever the
|
|
19103
|
+
* tile ended up being.
|
|
19104
|
+
*
|
|
19075
19105
|
* **Absent ≠ "missed silently"**: a row written before the column, a hub
|
|
19076
19106
|
* that predates the field, and every track whose tile landed native all
|
|
19077
19107
|
* omit it. Render nothing when absent.
|
|
@@ -18656,11 +18656,30 @@ var SensorEventSchema = object({
|
|
|
18656
18656
|
value: record(string(), unknown()).nullable(),
|
|
18657
18657
|
timestamp: number()
|
|
18658
18658
|
});
|
|
18659
|
+
/**
|
|
18660
|
+
* One stored sighting on a track's trajectory.
|
|
18661
|
+
*
|
|
18662
|
+
* The array these live in is returned in TIME order (D399) — it is APPENDED in
|
|
18663
|
+
* arrival order, and the two detector passes interleave, so a consumer must not
|
|
18664
|
+
* assume the two are the same on a row written by an older build.
|
|
18665
|
+
*/
|
|
18659
18666
|
var TrackPositionSchema = object({
|
|
18660
18667
|
x: number(),
|
|
18661
18668
|
y: number(),
|
|
18662
18669
|
timestamp: number(),
|
|
18663
|
-
bbox: BoundingBoxSchema
|
|
18670
|
+
bbox: BoundingBoxSchema,
|
|
18671
|
+
/**
|
|
18672
|
+
* Which detector pass measured this box (D399): `frame` is the full-frame
|
|
18673
|
+
* pass on the analysis raster, `recovery` is the native-resolution
|
|
18674
|
+
* small-subject second pass (D377/D378). Both write into one array, and until
|
|
18675
|
+
* this field existed the only way to tell them apart was that full-frame boxes
|
|
18676
|
+
* are exact multiples of 1.2 while recovery boxes are full-precision floats.
|
|
18677
|
+
* Absent on rows written before D399.
|
|
18678
|
+
*/
|
|
18679
|
+
source: _enum(["frame", "recovery"]).optional(),
|
|
18680
|
+
/** Detection score of this box, so a position can be weighed and not only
|
|
18681
|
+
* plotted. Absent on rows written before D399. */
|
|
18682
|
+
score: number().optional()
|
|
18664
18683
|
});
|
|
18665
18684
|
var TrackSnapshotSchema = object({
|
|
18666
18685
|
timestamp: number(),
|
|
@@ -19060,14 +19079,25 @@ var TrackSchema = object({
|
|
|
19060
19079
|
*/
|
|
19061
19080
|
hasRider: boolean().optional(),
|
|
19062
19081
|
/**
|
|
19063
|
-
* WHY this track ended without a NATIVE best-shot
|
|
19064
|
-
* ([D276](../decisions/adr-0276-a-stand-in-tile-is-provisional-and-a-close-says-why.md)
|
|
19082
|
+
* WHY this track ended without a NATIVE best-shot FRAME
|
|
19083
|
+
* ([D276](../decisions/adr-0276-a-stand-in-tile-is-provisional-and-a-close-says-why.md),
|
|
19084
|
+
* widened by [D400](../decisions/adr-0400-the-picture-is-judged-on-what-is-delivered.md)) —
|
|
19065
19085
|
* a composed token line (`no-key-frame capture=keyframe:native-missx4`,
|
|
19066
|
-
* `derive-returned-null tile=standin`,
|
|
19067
|
-
*
|
|
19068
|
-
*
|
|
19086
|
+
* `derive-returned-null tile=standin`,
|
|
19087
|
+
* `native-tile tile=native no-key-frame-at-close`, …) written at close and
|
|
19088
|
+
* CLEARED by the late-keyFrame upgrade when a native tile lands after all.
|
|
19089
|
+
* The operator-facing answer to "perché manca l'immagine?" on a track whose
|
|
19069
19090
|
* tile is a face/plate stand-in, a raster crop, or an icon.
|
|
19070
19091
|
*
|
|
19092
|
+
* **`no-key-frame-at-close` (D400).** The line used to be written ONLY when
|
|
19093
|
+
* the TILE ranked below native, so a track whose thumbnail landed natively
|
|
19094
|
+
* while its key frame missed carried no reason at all — three of the four
|
|
19095
|
+
* `MISSING_KEYFRAME` tracks in the 2026-09-07 operator audit were exactly
|
|
19096
|
+
* that shape, and their "niente ultimo" had no cause anywhere on the row.
|
|
19097
|
+
* The key frame is the head of a cascade (`keyFrame ⇒ keyFrameSmall ⇒ the
|
|
19098
|
+
* lastFrame copy source`), so its absence is now on this line whatever the
|
|
19099
|
+
* tile ended up being.
|
|
19100
|
+
*
|
|
19071
19101
|
* **Absent ≠ "missed silently"**: a row written before the column, a hub
|
|
19072
19102
|
* that predates the field, and every track whose tile landed native all
|
|
19073
19103
|
* omit it. Render nothing when absent.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-export-google",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.48",
|
|
4
4
|
"description": "Google Home export — hub-side smart-home fulfillment (SYNC / QUERY / EXECUTE / DISCONNECT) for the non-camera fleet, served over the hub's own OAuth account link. No Google credential is stored, sent or required.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|