@chenpengfei/daily-brief 0.1.0

package/dist/src/storage/source-item-store.js

@@ -0,0 +1,63 @@
+import { mkdir, readFile, writeFile } from "node:fs/promises";
+import { dirname, join } from "node:path";
+import { formatDateKey, resolveDailyBriefPaths } from "../config/index.js";
+export function sourceItemStorePath(date, root = resolveDailyBriefPaths().sourceItemRoot, dateKey) {
+    const datePart = dateKey ?? formatDateKey(date);
+    const [year, month] = datePart.split("-");
+    if (!year || !month) {
+        throw new Error(`Invalid Source Item Store date: ${datePart}`);
+    }
+    return join(root, year, month, `${datePart}.jsonl`);
+}
+export async function appendSourceItems(items, date, root = resolveDailyBriefPaths().sourceItemRoot, dateKey) {
+    const path = sourceItemStorePath(date, root, dateKey);
+    const existing = await readSourceItems(date, root, dateKey);
+    const seenIds = new Set(existing.map((item) => item.id));
+    const seenHashes = new Set(existing.map((item) => item.contentHash));
+    const written = [];
+    const skipped = [];
+    for (const item of items) {
+        if (seenIds.has(item.id) || seenHashes.has(item.contentHash)) {
+            skipped.push(item);
+            continue;
+        }
+        seenIds.add(item.id);
+        seenHashes.add(item.contentHash);
+        written.push(item);
+    }
+    if (written.length > 0) {
+        await mkdir(dirname(path), { recursive: true });
+        const next = [...existing, ...written].map((item) => JSON.stringify(item)).join("\n");
+        await writeFile(path, `${next}\n`, "utf8");
+    }
+    return { path, written, skipped };
+}
+export async function readSourceItems(date, root = resolveDailyBriefPaths().sourceItemRoot, dateKey) {
+    const path = sourceItemStorePath(date, root, dateKey);
+    let contents;
+    try {
+        contents = await readFile(path, "utf8");
+    }
+    catch (error) {
+        if (isNodeError(error) && error.code === "ENOENT") {
+            return [];
+        }
+        throw error;
+    }
+    return contents
+        .split("\n")
+        .filter((line) => line.trim().length > 0)
+        .map((line, index) => parseSourceItemLine(line, path, index + 1));
+}
+function isNodeError(error) {
+    return error instanceof Error && "code" in error;
+}
+function parseSourceItemLine(line, path, lineNumber) {
+    try {
+        return JSON.parse(line);
+    }
+    catch (error) {
+        const cause = error instanceof Error ? `: ${error.message}` : "";
+        throw new Error(`${path} line ${lineNumber} contains malformed Source Item JSON${cause}`);
+    }
+}

package/dist/src/workflow/index.js

@@ -0,0 +1 @@
+export * from "./status.js";

package/dist/src/workflow/status.js

@@ -0,0 +1,95 @@
+import { readFile } from "node:fs/promises";
+import { join } from "node:path";
+import { loadSourceRegistry, resolveDailyBriefPaths } from "../config/index.js";
+export function evaluateWorkflowStatus(input) {
+    if (input.coreFailure) {
+        return {
+            health: "core-failure",
+            message: input.coreFailure.message,
+            materialPartialFailures: [],
+            coreFailure: input.coreFailure
+        };
+    }
+    if (!input.briefGenerated) {
+        return {
+            health: "core-failure",
+            message: "Daily Brief generation did not produce an archiveable Brief.",
+            materialPartialFailures: [],
+            coreFailure: {
+                kind: "brief-generation-unavailable",
+                message: "Daily Brief generation did not produce an archiveable Brief."
+            }
+        };
+    }
+    const materialPartialFailures = input.collectionResults
+        .filter((result) => result.status === "failed")
+        .map((result) => `${result.sourceId}: ${result.reason ?? "Unknown failure"}`)
+        .filter(isMaterialPartialFailure);
+    if (materialPartialFailures.length > 0) {
+        return {
+            health: "partial-failure",
+            message: "Daily Brief generated with material Source Coverage gaps.",
+            materialPartialFailures
+        };
+    }
+    return {
+        health: "success",
+        message: "Daily Brief workflow completed successfully.",
+        materialPartialFailures: []
+    };
+}
+export function createCoreWorkflowFailureNotification(failure) {
+    return [
+        "Daily Brief failed",
+        "",
+        `Core Workflow Failure: ${failure.kind}`,
+        failure.message,
+        "",
+        "No Daily Brief was generated, because sending a false or unsupported Brief would break trust."
+    ].join("\n");
+}
+export async function getOperationalStatus(options = {}) {
+    const date = options.date ?? new Date();
+    try {
+        await loadSourceRegistry(options.sourceRegistryPath);
+    }
+    catch (error) {
+        return evaluateWorkflowStatus({
+            collectionResults: [],
+            briefGenerated: false,
+            coreFailure: {
+                kind: "unreadable-source-registry",
+                message: error instanceof Error ? error.message : String(error)
+            }
+        });
+    }
+    const archivePath = briefArchivePath(date, options.archiveRoot ?? resolveDailyBriefPaths().briefArchiveRoot, options.dateKey);
+    try {
+        await readFile(archivePath, "utf8");
+    }
+    catch {
+        return {
+            health: "partial-failure",
+            message: `No Daily Brief archived for ${options.dateKey ?? date.toISOString().slice(0, 10)} yet.`,
+            materialPartialFailures: []
+        };
+    }
+    return {
+        health: "success",
+        message: `Daily Brief archive exists for ${options.dateKey ?? date.toISOString().slice(0, 10)}.`,
+        materialPartialFailures: []
+    };
+}
+function isMaterialPartialFailure(message) {
+    const normalized = message.toLowerCase();
+    const nonMaterialPatterns = ["missing transcript", "transcript missing", "rate limit", "parse failure"];
+    return !nonMaterialPatterns.some((pattern) => normalized.includes(pattern));
+}
+function briefArchivePath(date, root, dateKey) {
+    const datePart = dateKey ?? date.toISOString().slice(0, 10);
+    const [year, month] = datePart.split("-");
+    if (!year || !month) {
+        throw new Error(`Invalid archive date: ${datePart}`);
+    }
+    return join(root, year, month, `${datePart}.md`);
+}

package/docs/operations.md

@@ -0,0 +1,74 @@
+# Daily Brief Operations
+
+For end-user installation, setup, upgrade, and troubleshooting, see `docs/user-manual.md`. For maintainer release gates and publication steps, see `docs/release-workflow.md`.
+
+Installed usage uses the `daily-brief` binary:
+
+```bash
+daily-brief setup
+daily-brief run-once --date 2026-05-28
+daily-brief status
+```
+
+Development usage from a repository checkout uses `npm run cli --`:
+
+```bash
+npm run cli -- collect
+npm run cli -- generate
+npm run cli -- deliver
+npm run cli -- status
+npm run cli -- run-once
+```
+
+Expected local cadence:
+
+- 06:00 local time: run `collect`.
+- 07:00 local time: run `run-once` or `generate` followed by `deliver`.
+
+Scheduler integration is intentionally deployment-neutral. A local cron, launchd job, systemd timer, GitHub Actions workflow, or another scheduler can call the commands above; the repository does not bind the MVP to a specific host.
+
+`run-once` executes collection, brief generation/archive, and Discord delivery in order. Source Item writes are deduplicated by Source Item id and content hash within the daily JSONL store, and Daily Brief generation merges repeated mentions into one multi-citation Signal, so rerunning the workflow for the same Collection Window does not duplicate equivalent Signals.
+
+## Manual run
+
+For a one-off Manual Run against the configured Sources:
+
+```bash
+npm run cli -- sources list
+npm run cli -- run-once
+npm run cli -- status
+```
+
+`sources list` confirms which Sources are enabled, including the default `github-trending-daily` Source. `run-once` performs collection, brief generation, archive writing, and Discord Delivery once. `status` reports operational health after the run.
+
+Discord Delivery uses `DISCORD_WEBHOOK_URL` from the shell environment or local `.env`; `.env` is loaded automatically by the Operational CLI and does not need to be sourced manually.
+
+## Runtime configuration
+
+When the Operational CLI starts, it loads local `.env` values from the repository root if the file exists. Existing shell environment variables take precedence over `.env` values. The `.env` file is ignored by Git; use `.env.example` as the non-secret template.
+
+Installed operational paths can be adjusted through environment variables:
+
+- `DAILY_BRIEF_HOME`: user config directory. Defaults to `~/.daily-brief`.
+- `DAILY_BRIEF_DATA_HOME`: generated data directory. Defaults to `~/.daily-brief/data`.
+- `DAILY_BRIEF_DISCORD_TEMPLATE_PATH`: optional Discord notification template override. Defaults to the packaged Discord notification template.
+- `DISCORD_WEBHOOK_URL`: Discord webhook URL. If unset, Discord Delivery is skipped with an explicit reason.
+
+Model/provider and delivery configuration should normally be managed with:
+
+```bash
+daily-brief model configure
+daily-brief model status
+daily-brief delivery configure --enabled true --webhook-url <url>
+daily-brief delivery status
+```
+
+Secrets live in `~/.daily-brief/auth.json` or environment variables, never in `sources.yaml` or committed project files. Installed CLI configuration does not accept the faux provider; faux is reserved for tests through an explicit test-only runtime gate.
+
+`run-once` does not archive a normal Daily Brief when every enabled Source fails or when no Source Items exist for the requested date. It reports a Core Workflow Failure instead, because a false low-signal brief would hide collection failure.
+
+## GitHub Trending collection
+
+`github-trending-daily` monitors the site-wide daily GitHub Trending page. The Fetch Adapter treats each listed repository as a Trending Repository Observation and keeps parsing intentionally narrow: repository link, short description, stars/forks when visible, and stars today when visible. It does not fetch README files or repository detail APIs.
+
+The adapter relies on focused HTML parsing plus regression tests for observed GitHub page changes. A GitHub Trending parsing failure is handled as a Source-level collection failure; it should not silently fall back to stale trend-list data.

package/docs/release-workflow.md

@@ -0,0 +1,220 @@
+# Formal Release Workflow
+
+Formal Releases publish both a GitHub Release and the npm package `@chenpengfei/daily-brief`. The installed command remains `daily-brief`.
+
+The workflow has three human-triggered Release Gates:
+
+1. Agent Release Preparation Gate
+2. Agent Release Review Gate
+3. Human Release Gate
+
+Publication commands are never run before the Human Release Gate.
+
+## Release Invariants
+
+- The Release Version uses SemVer: npm/package uses `X.Y.Z`, while GitHub tag and release title use `vX.Y.Z`.
+- Release Pull Requests normally prepare release materials only: package metadata, version, Changelog, User Manual, release workflow documentation, and evidence.
+- Release Pull Requests should not include ordinary product code fixes.
+- Product-code Release Blockers normally leave the release line and are handled through a separate issue or fix PR.
+- A minimal Release-Blocking Fix may remain in the Release Pull Request only when it is required to prove installability or publishability for the same release, is explicitly recorded in the Release Checklist Issue and Release Pull Request, and is called out for focused Agent Release Review.
+- Published tags and npm versions are immutable. Post-Release Incidents use documentation and patch releases instead of moved tags or silent rollback.
+
+## Gate 1: Agent Release Preparation
+
+Trigger this gate by asking an Agent to prepare release `vX.Y.Z`.
+
+The Agent must:
+
+- Create or update the Release Checklist Issue.
+- Create a `release/vX.Y.Z` branch and Release Pull Request.
+- Update `package.json` and `package-lock.json` to the Release Version and package metadata.
+- Update `CHANGELOG.md` with user-visible changes, installation or upgrade notes, and known limitations.
+- Update `docs/user-manual.md` for any user-facing behavior changes.
+- Update `docs/release-workflow.md` if the release process changes.
+- Run `npm run release:check`.
+- Run `npm run release:publish:dry-run`.
+- Run the isolated Release Install Smoke Test.
+- Record command evidence and any Release Blockers in the Release Checklist Issue and Release Pull Request.
+
+The Release Check Command runs:
+
+```bash
+npm test
+npm run typecheck
+npm run build
+npm pack --dry-run
+```
+
+The npm publish dry-run verifies scoped package publication metadata without publishing:
+
+```bash
+npm run release:publish:dry-run
+```
+
+The Release Install Smoke Test must use temporary npm and Daily Brief paths:
+
+```bash
+npm pack
+npm install --prefix /tmp/daily-brief-smoke -g ./chenpengfei-daily-brief-X.Y.Z.tgz --no-audit --no-fund
+DAILY_BRIEF_HOME=/tmp/daily-brief-home \
+DAILY_BRIEF_DATA_HOME=/tmp/daily-brief-data \
+/tmp/daily-brief-smoke/bin/daily-brief --help
+DAILY_BRIEF_HOME=/tmp/daily-brief-home \
+DAILY_BRIEF_DATA_HOME=/tmp/daily-brief-data \
+/tmp/daily-brief-smoke/bin/daily-brief setup
+```
+
+Use a unique temporary directory for real runs. Do not install into the maintainer's real global npm prefix or real `~/.daily-brief` during the smoke test.
+
+If a product-code blocker appears, stop the release preparation and classify it:
+
+- If the blocker is not required to prove this release's installability or publishability, record the blocker, create or link the fix issue, and restart this gate after the fix is merged.
+- If the blocker is a minimal Release-Blocking Fix, keep it in the Release Pull Request only after recording the reason, affected files, extra tests, smoke evidence, and review focus in the Release Checklist Issue and Release Pull Request.
+
+Release-Blocking Fixes are exceptions, not a way to bundle unrelated behavior change into a release. The Agent Release Review Gate must review the exception explicitly.
+
+## Gate 2: Agent Release Review
+
+Trigger this gate in an independent Agent context after the Release Pull Request is ready.
+
+The reviewing Agent must use a review stance and inspect:
+
+- Release Checklist Issue evidence.
+- Release Pull Request diff.
+- `package.json` and `package-lock.json`.
+- `CHANGELOG.md`.
+- `docs/user-manual.md`.
+- `docs/release-workflow.md`.
+- Release CI Workflow result.
+- Local evidence for `npm run release:check`.
+- Local evidence for the Release Install Smoke Test.
+- Any Release-Blocking Fix exception, including affected files, scope justification, targeted tests, smoke evidence, and whether a separate fix PR would be safer before release.
+
+The reviewing Agent should report blocking findings first, with file and line references when possible. It may recommend approval or request fixes, but it must not publish the release or approve its own preparation work.
+
+## Gate 3: Human Release
+
+Only the maintainer can pass the Human Release Gate.
+
+Before publishing, verify:
+
+- Release Pull Request is merged.
+- Local `main` matches `origin/main`.
+- Release CI Workflow is green on the merged state.
+- Agent Release Review Gate recommends approval or all findings are resolved.
+- npm credentials and GitHub credentials are available to the maintainer.
+- npm package state has been checked with `npm view @chenpengfei/daily-brief version`; first release should be unpublished, and later releases should show a version lower than the target Release Version.
+- release notes have been prepared from the matching `CHANGELOG.md` entry.
+
+Run the Human Release helper in preflight mode first:
+
+```bash
+npm run release:human -- --version X.Y.Z
+```
+
+After the maintainer confirms the preflight output, publish with explicit confirmation:
+
+```bash
+npm run release:human -- --version X.Y.Z --publish --yes --issue <release-checklist-issue-number>
+```
+
+The GitHub Release notes should be derived from the `CHANGELOG.md` entry and include:
+
+- User-visible changes.
+- Installation or upgrade notes.
+- Known limitations.
+- Installation command: `npm install -g @chenpengfei/daily-brief`.
+
+After publication, verify public installation:
+
+```bash
+npm view @chenpengfei/daily-brief version
+npm install --prefix /tmp/daily-brief-public-smoke -g @chenpengfei/daily-brief@X.Y.Z --no-audit --no-fund
+/tmp/daily-brief-public-smoke/bin/daily-brief --help
+```
+
+The Human Release helper performs this public installation verification after `npm publish` and GitHub Release creation.
+
+Record the npm version, GitHub Release URL, tag, and public install verification in the Release Checklist Issue.
+
+## Post-Release Incidents
+
+If npm publish succeeds but GitHub Release creation fails, continue by fixing GitHub Release creation for the same tag and version.
+
+If GitHub Release is public but install verification fails, record the incident in the Release Checklist Issue, update release notes when relevant, create a fix issue, and publish a patch Release Version after the fix. Do not move the tag or unpublish the npm package unless the release exposed a severe secret or credential issue.
+
+## Release Checklist Issue Template
+
+```md
+# Release vX.Y.Z
+
+## Scope
+
+- Release Version: X.Y.Z
+- GitHub tag: vX.Y.Z
+- npm package: @chenpengfei/daily-brief
+- Release Pull Request:
+
+## Gate 1: Agent Release Preparation
+
+- [ ] Release branch created: release/vX.Y.Z
+- [ ] Release Pull Request opened
+- [ ] package metadata updated
+- [ ] CHANGELOG.md updated
+- [ ] docs/user-manual.md updated
+- [ ] docs/release-workflow.md updated if needed
+- [ ] npm run release:check completed
+- [ ] npm run release:publish:dry-run completed
+- [ ] Release Install Smoke Test completed with temporary npm prefix and Daily Brief homes
+- [ ] Release Blockers recorded or confirmed absent
+- [ ] Release-Blocking Fix exceptions recorded or confirmed absent
+
+### Preparation Evidence
+
+- release:check:
+- publish dry-run:
+- npm pack output:
+- npm package state before publish:
+- install smoke test:
+- Release-Blocking Fix exception:
+- git status:
+- notes:
+
+## Gate 2: Agent Release Review
+
+- [ ] Independent Agent review requested
+- [ ] Release Pull Request reviewed
+- [ ] Release Checklist evidence reviewed
+- [ ] Release CI Workflow result reviewed
+- [ ] Release-Blocking Fix exceptions reviewed or confirmed absent
+- [ ] Review recommendation recorded
+
+### Review Findings
+
+- Blocking:
+- Non-blocking:
+- Recommendation:
+
+## Gate 3: Human Release
+
+- [ ] Release Pull Request merged
+- [ ] main matches origin/main
+- [ ] npm package state checked
+- [ ] GitHub Release notes file prepared
+- [ ] tag pushed: vX.Y.Z
+- [ ] npm publish completed
+- [ ] GitHub Release created
+- [ ] public install verification completed
+
+### Publication Evidence
+
+- npm version:
+- npm package state before publish:
+- GitHub Release URL:
+- tag:
+- public install:
+
+## Post-Release Incidents
+
+- None known.
+```

package/docs/user-manual.md

@@ -0,0 +1,146 @@
+# Daily Brief User Manual
+
+Daily Brief is an installed command-line tool for generating a recurring Agent architecture and AI Coding brief from Sources you explicitly configure.
+
+## Install
+
+Daily Brief is distributed as the npm package `@chenpengfei/daily-brief` and installs the `daily-brief` command.
+
+```bash
+npm install -g @chenpengfei/daily-brief
+daily-brief --help
+```
+
+Daily Brief requires Node.js 22 or newer.
+
+## First Setup
+
+Run setup after installing the package:
+
+```bash
+daily-brief setup
+```
+
+Setup creates user configuration and generated-data directories, initializes the Source Registry from the packaged example, prepares credential storage, and reports readiness. Setup does not collect Sources, call an LLM, generate a Daily Brief, or send a delivery notification.
+
+By default, configuration files live under `~/.daily-brief/`, and generated data lives under `~/.daily-brief/data/`.
+
+## Configure Sources
+
+Sources are manually controlled. The agent processes configured Sources, but it does not autonomously add or remove them.
+
+```bash
+daily-brief sources list
+daily-brief sources edit
+daily-brief sources validate
+daily-brief sources enable <source-id>
+daily-brief sources disable <source-id>
+```
+
+Use `sources validate` after editing the Source Registry.
+
+## Configure Model Access
+
+Agent Stages require an LLM Provider Configuration before real Daily Brief generation.
+
+```bash
+daily-brief model configure
+daily-brief model status
+daily-brief model login
+daily-brief model logout
+```
+
+Credentials are stored in the Model Credential Store or environment variables. Do not put secrets in `sources.yaml` or committed project files.
+
+## Configure Delivery
+
+Discord Delivery is optional. Configure it when you want generated Daily Brief notifications pushed to Discord.
+
+```bash
+daily-brief delivery configure --enabled true --webhook-url <url>
+daily-brief delivery status
+daily-brief delivery test
+```
+
+If Discord Delivery is disabled or no webhook is configured, generation can still run and will report skipped delivery explicitly.
+
+## Run Daily Brief
+
+For a full manual run:
+
+```bash
+daily-brief run-once
+```
+
+For separated operational steps:
+
+```bash
+daily-brief collect
+daily-brief generate
+daily-brief deliver
+daily-brief status
+```
+
+The expected local cadence is collection at 06:00 and generation or delivery at 07:00 local time. Daily Brief does not include a built-in scheduler; use an external scheduler to invoke the CLI.
+
+## Inspect Status
+
+Use status after setup, after manual runs, or when diagnosing failures:
+
+```bash
+daily-brief status
+```
+
+Status output is the operational surface for collection, analysis, archive, and delivery health.
+
+## Paths and Environment
+
+The installed CLI uses user-home paths by default:
+
+- `DAILY_BRIEF_HOME`: configuration directory, default `~/.daily-brief`.
+- `DAILY_BRIEF_DATA_HOME`: generated data directory, default `~/.daily-brief/data`.
+- `DAILY_BRIEF_DISCORD_TEMPLATE_PATH`: optional Discord notification template override.
+- `DISCORD_WEBHOOK_URL`: optional Discord webhook URL.
+
+Repository checkouts may use a local `.env`; installed usage should normally rely on user configuration and credential commands.
+
+## Upgrade
+
+Upgrade the installed package through npm:
+
+```bash
+npm install -g @chenpengfei/daily-brief@latest
+daily-brief status
+```
+
+Run `daily-brief setup` again when release notes or status output indicate that configuration needs to be refreshed. Setup preserves existing files unless an overwrite or force behavior is explicitly selected.
+
+## Troubleshooting
+
+If setup has not run, run:
+
+```bash
+daily-brief setup
+```
+
+If Sources are not collected, run:
+
+```bash
+daily-brief sources validate
+daily-brief sources list
+```
+
+If model access fails, run:
+
+```bash
+daily-brief model status
+```
+
+If Discord delivery fails or is skipped, run:
+
+```bash
+daily-brief delivery status
+daily-brief delivery test
+```
+
+If a run cannot honestly produce a Daily Brief, the CLI reports a Core Workflow Failure rather than archiving a false normal Daily Brief.

package/package.json

@@ -0,0 +1,65 @@
+{
+  "name": "@chenpengfei/daily-brief",
+  "version": "0.1.0",
+  "description": "Agent-driven daily brief CLI for manually curated Agent architecture and AI Coding sources.",
+  "private": false,
+  "type": "module",
+  "license": "MIT",
+  "homepage": "https://github.com/chenpengfei/daily-brief#readme",
+  "bugs": {
+    "url": "https://github.com/chenpengfei/daily-brief/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/chenpengfei/daily-brief.git"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [
+    "agent",
+    "daily-brief",
+    "cli",
+    "ai-coding",
+    "briefing"
+  ],
+  "files": [
+    "dist/src",
+    "config/sources.example.yaml",
+    "templates",
+    "docs/operations.md",
+    "docs/user-manual.md",
+    "docs/release-workflow.md",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
+  "bin": {
+    "daily-brief": "dist/src/cli.js"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "cli": "tsx src/cli.ts",
+    "prepack": "npm run build",
+    "release:check": "npm test && npm run typecheck && npm run build && npm pack --dry-run",
+    "release:human": "node scripts/human-release.mjs",
+    "release:publish:dry-run": "npm publish --dry-run --access public",
+    "test": "vitest run",
+    "typecheck": "tsc -p tsconfig.json --noEmit"
+  },
+  "dependencies": {
+    "@earendil-works/pi-agent-core": "^0.76.0",
+    "@earendil-works/pi-ai": "^0.76.0",
+    "fast-xml-parser": "^5.2.2",
+    "yaml": "^2.8.0"
+  },
+  "devDependencies": {
+    "@types/node": "^22.15.24",
+    "tsx": "^4.19.4",
+    "typescript": "^5.8.3",
+    "vitest": "^3.1.4"
+  },
+  "engines": {
+    "node": ">=22"
+  }
+}

package/templates/daily-brief.md

@@ -0,0 +1,9 @@
+# Daily Brief -- {{date}}
+
+## Executive Summary
+
+## Top Signals
+
+## Source Coverage
+
+## Sources

package/templates/discord-notification.md

@@ -0,0 +1,7 @@
+Daily Brief -- {{date}}
+
+今日重点：
+{{summary_bullets}}
+
+完整简报：
+{{brief_path}}