lumi-research-setup

To set up research API keys safely, use a configuration tool that inspects your `.env.example` file and reports missing credentials by name only, ensuring secrets are never printed or mutated during the setup process.

Configuring environment variables for ArXiv and Semantic Scholar fetchers involves checking your `.env` file against provider requirements and adding the specific API keys, where the setup process preserves existing values and only writes user-supplied inputs.

Yes, configuring the research pack runtime requires Python tooling to be available, as the setup process validates bundled fetcher and resolve tools by checking their help output to ensure they are runnable.

You can check which optional API keys are required for OpenAlex, Unpaywall, and CORE enrichment workflows by running a setup check that reports missing keys by name and explains whether they are required or optional for registration.

Safe secrets handling during literature discovery setup works by preserving existing environment keys and writing only user-supplied values, ensuring the system never creates, mutates, or prints secrets while preparing provider credentials.

Limitations when configuring the resolve_pdf ladder include the setup process never mutating the `wiki/` or `raw/` directories, only inspecting configuration files, and optionally performing a harmless smoke check to verify tool availability.