Fix(docs): replace incorrect settings.toml path with accurate storage description

[nlok5923]

• README stated settings are saved to ~/.ironclaw/settings.toml — this file is never created by ironclaw
• Settings are actually persisted in the connected database (postgres or libsql); bootstrap vars like DATABASE_URL and LLM_BACKEND go to
  ~/.ironclaw/.env
• Fixes confusion reported in Configuration is not being saved #187 where users couldn't find their config after onboarding

[gemini-code-assist]

Summary of Changes

Hello @nlok5923, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request clarifies the documentation regarding how application settings and bootstrap variables are managed. It corrects an outdated statement in the README.md about settings being saved to a settings.toml file, instead accurately describing their persistence in the connected database and the use of a .env file for initial bootstrap variables. This update aims to prevent user confusion regarding configuration storage.

Highlights

• Documentation Correction: The README.md has been updated to remove the incorrect statement that application settings are saved to ~/.ironclaw/settings.toml.
• Settings Persistence Clarification: The documentation now accurately states that application settings are persisted in the connected database (Postgres or LibSQL).
• Bootstrap Variable Location: Information has been added detailing that bootstrap variables like DATABASE_URL and LLM_BACKEND are stored in ~/.ironclaw/.env.
• User Confusion Addressed: This change resolves confusion reported in issue Configuration is not being saved #187, where users were unable to locate their configuration after onboarding.

Changelog

• README.md
  • Removed the incorrect reference to ~/.ironclaw/settings.toml for settings storage.
  • Clarified that settings are persisted in the connected database.
  • Added details about bootstrap variables (DATABASE_URL, LLM_BACKEND) being written to ~/.ironclaw/.env.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the README.md to reflect how application settings are persisted. The previous documentation pointed to a non-existent settings.toml file. The updated text accurately states that settings are stored in the connected database, and essential bootstrap variables are placed in ~/.ironclaw/.env. I've cross-referenced this with the setup and configuration logic in the source code, and it is correct. This is a good clarification that will prevent user confusion.