mine-gemini-workflowslisted

# Mine Gemini workflows Use session evidence to find workflows worth porting. This is workflow archaeology, not a bulk conversation export. ## Non-negotiable privacy boundaries - Require one explicitly selected Gemini project/session directory. Never crawl the entire home directory by default. - Run the metadata-only pass first. - Do not extract or summarize private thoughts, reasoning fields, tool arguments, secrets, or complete transcripts. - Do not commit `.context-os/migrations/` or raw Gemini recordings. - Ask before any `--include-content`, `--include-summaries`, or `--include-paths` pass and explain exactly which selected sessions will be read. - A repeated pattern is a candidate, not authorization to create or install a skill. ## Procedure ### 1. Select evidence Ask the user for the relevant Gemini project/session directory and optional date boundary. If they do not know the directory, help them locate candidate directories using names and modification dates only; do not read session bodies during discovery. ### 2. Create a metadata-only inventory Run: ```bash python3 scripts/mine-gemini-workflows.py \ <selected-session-directory> \ --output .context-os/migrations/<timestamp>/gemini-inventory.json ``` Add `--since YYYY-MM-DD` when the user supplied a date boundary. The default report includes tool names, validation status, file basenames, and session identifiers. It excludes message text, free-form workflow summaries, tool arguments, and full paths. ###