unioss-knowledge-refreshlisted

# UNIOSS Knowledge — Refresh ## Input - One of `daily` (default), `weekly`, `monthly`, `yearly`. ## Workflow — daily 1. Run: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/refresh.mjs" daily ``` 2. Relay the written digest path. ## Workflow — weekly | monthly | yearly (two phases) 1. **Crawl** — run: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/refresh.mjs" <weekly|monthly|yearly> --phase=crawl ``` It prints the evidence path (`sentiment/evidence-<period>.json`) and observation count. 2. **Classify** — read the evidence file and extract **customer voice only**: - Ignore developer chatter, code snippets, logs, test output, merge/CI noise. - Read Japanese comments natively; write each finding as one concise English line. - Each item: `{ "body": "<≤200 chars>", "source": "<ticket url>" }`; max 20 per list. - Genuinely empty is fine — empty arrays render "(none yet)". Never pad with noise. Write the result as `sentiment/classified-<period>.json` next to the evidence file: ```json { "praise": [{ "body": "...", "source": "..." }], "criticism": [{ "body": "...", "source": "..." }] } ``` 3. **Finalize** — run: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/refresh.mjs" <weekly|monthly|yearly> --phase=finalize --classified=<classified-path> ``` Relay the written paths — `sentiment/current.md` and `GLOBAL.md`. ## Notes - `daily` windows on **creation** date — the digest answers "what new tickets arrived today". - `week