| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat(telemetry): accept disclosed default-on usage policy without fabricated consent Add closed schema3/notice_version5 ingest and generated CWC contract. Preserve original v1 first-party-only and v2/consent4 semantics, reject mixed policy fields before storage or forwarding, and retain IP/host/operator/content guards. Existing Analytics Engine column positions remain fixed; schema_version distinguishes old consent from new notice metadata. Document the founder's amended default-on/opt-out policy and preserve prior declines. Rust/app preference changes are integrated separately. Validation: ingest 171 passed, 0 failed across 6 files; TypeScript, facts, 23 documentation topics and git diff checks passed. Original validator rejects the new v3 fixture; current validator accepts v2 and v3. Proposed Rust v3 fixture accepted by ingest; sender proof pending Rust integration. Root npm test && npm run check:web exits1 because no test script exists (0 tests, check:web not reached). No hosted deployment, processor activation or runtime-installed policy change claimed. Signed-off-by: CodeWhale Bot <bot@codewhale.net> | 30 天前 | |
feat(telemetry): report observed active installs with trend, freshness, and caveats Operationalize the owner report around the honest metric: observed active installs = distinct rotating anonymous install ids with a session_start ingested on a UTC day. The canonical report:active-installs command prints the daily series, a complete-days 7-vs-7 trend, event freshness, and an always-printed coverage-caveat block; report:dau remains as a pure re-export compat alias. Exclusion guarantees are now pinned by tests (index1 only inside count(DISTINCT), no content/identity/network columns anywhere in the report path), and the output is forbidden from claiming DAU/unique users. Known floor semantics recorded in docs: day attribution is ingest-day (events carry no per-event timestamps), distinct counts cannot be sampling-corrected, and id rotation can double-count across a trend window — all framed as the lower-bound caveats they are. Verified: telemetry-ingest npm test (109/109), npm run typecheck, CLI smoke against fixtures. Implemented with Claude Code agent assistance. | 1 个月前 | |
feat(telemetry): report observed active installs with trend, freshness, and caveats Operationalize the owner report around the honest metric: observed active installs = distinct rotating anonymous install ids with a session_start ingested on a UTC day. The canonical report:active-installs command prints the daily series, a complete-days 7-vs-7 trend, event freshness, and an always-printed coverage-caveat block; report:dau remains as a pure re-export compat alias. Exclusion guarantees are now pinned by tests (index1 only inside count(DISTINCT), no content/identity/network columns anywhere in the report path), and the output is forbidden from claiming DAU/unique users. Known floor semantics recorded in docs: day attribution is ingest-day (events carry no per-event timestamps), distinct counts cannot be sampling-corrected, and id rotation can double-count across a trend window — all framed as the lower-bound caveats they are. Verified: telemetry-ingest npm test (109/109), npm run typecheck, CLI smoke against fixtures. Implemented with Claude Code agent assistance. | 1 个月前 | |
feat(telemetry): report observed active installs with trend, freshness, and caveats Operationalize the owner report around the honest metric: observed active installs = distinct rotating anonymous install ids with a session_start ingested on a UTC day. The canonical report:active-installs command prints the daily series, a complete-days 7-vs-7 trend, event freshness, and an always-printed coverage-caveat block; report:dau remains as a pure re-export compat alias. Exclusion guarantees are now pinned by tests (index1 only inside count(DISTINCT), no content/identity/network columns anywhere in the report path), and the output is forbidden from claiming DAU/unique users. Known floor semantics recorded in docs: day attribution is ingest-day (events carry no per-event timestamps), distinct counts cannot be sampling-corrected, and id rotation can double-count across a trend window — all framed as the lower-bound caveats they are. Verified: telemetry-ingest npm test (109/109), npm run typecheck, CLI smoke against fixtures. Implemented with Claude Code agent assistance. | 1 个月前 | |
feat(telemetry): report observed active installs with trend, freshness, and caveats Operationalize the owner report around the honest metric: observed active installs = distinct rotating anonymous install ids with a session_start ingested on a UTC day. The canonical report:active-installs command prints the daily series, a complete-days 7-vs-7 trend, event freshness, and an always-printed coverage-caveat block; report:dau remains as a pure re-export compat alias. Exclusion guarantees are now pinned by tests (index1 only inside count(DISTINCT), no content/identity/network columns anywhere in the report path), and the output is forbidden from claiming DAU/unique users. Known floor semantics recorded in docs: day attribution is ingest-day (events carry no per-event timestamps), distinct counts cannot be sampling-corrected, and id rotation can double-count across a trend window — all framed as the lower-bound caveats they are. Verified: telemetry-ingest npm test (109/109), npm run typecheck, CLI smoke against fixtures. Implemented with Claude Code agent assistance. | 1 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 30 天前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 1 个月前 |