# Maintenance Checklist

Use this checklist before doing any cleanup or review-maintenance action for reader keyword artifacts.

## Pre-check

1. Confirm the current repo root is `/home/ubuntu/zhu/github/reader`
2. Confirm the user asked for a maintenance / cleanup / review-prep action
3. If the user actually wants formal keyword review generation, route to reader-side `keyword-cleanup-review` instead of using this maintenance skill
4. Identify whether the action targets:
   - current bundle
   - suggestions JSON
   - markdown display draft
   - old review outputs

## Safety check

Before deleting or overwriting anything:

1. Do not touch:
   - `data/term_index/daily/*.json`
   - `data/term_index/term_stats.json`
   - `configs/filter_context.personal.json`
   - `configs/term_watchlist.json`
   - `configs/term_aliases.json`
   - `configs/term_stopwords.json`
   - `configs/term_change_log.json`
2. Confirm the suggestions JSON to keep is not the one about to be applied
3. Treat markdown drafts as disposable only after confirming they are display-only artifacts

## Review-prep flow

When preparing manual review:

1. Ensure the latest bundle exists
2. Ensure the latest suggestions JSON exists
3. Generate markdown only if the user explicitly wants human-readable review material
4. Prefer showing conclusions in chat before creating more files

## Cleanup flow

Recommended order:

1. remove old markdown display drafts
2. keep only the current/latest bundle
3. prune old suggestions JSON conservatively
4. leave facts/state/config untouched

## Post-check

After the action:

1. verify the expected kept files still exist
2. verify no config file was accidentally changed
3. summarize what was kept vs removed