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. If it prints a `.md` path (zero tickets), relay it. Done. 3. Otherwise: read the printed evidence file, invoke the `unioss-knowledge-report` skill, and write one report section per ticket (**daily** depth) to `digests/<date>-daily.md`. Relay the 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. Customer sentiment on this GitLab is **relayed**: customers (municipalities) never comment directly — team members carry their voice. Extract **customer-impacting signal**, whoever typed it: - **Criticism** — bugs reported from municipalities/production, complaints, repeated requests, dissatisfaction, urgent escalations relayed in comments. - **Praise** — relayed thanks, satisfaction, positive confirmations from the customer side. - Still ignore: pure dev/PM process chatter (review approvals, merge/deploy notices, refactor debates, CI/test logs) with no customer-impacting content. - Read Japanese natively; one concise line in the user's current conversation language + source URL per item; ≤20 per l