docs: improve README

[webbrain-one]

Makes one small, focused improvement to the existing README.

[qodo-code-review]

PR Summary by Qodo

Docs: clarify README config files and tidy footer

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Document auto-created workflow_state.json in the config directory tree.
• Remove trailing blank lines at the end of the README.

High-Level Assessment

The current approach (directly updating the README to reflect the actual config file layout and cleaning up formatting) is the simplest and most appropriate option for this change.

Files changed (1) +3 / -2

Documentation (1) +3 / -2

README.mdDocument workflow state file and clean up trailing whitespace +3/-2

Document workflow state file and clean up trailing whitespace

• Adds 'workflow_state.json' to the documented configuration directory structure as an auto-created workflow state file. Removes extra trailing blank lines at the end of the README for cleaner formatting.

README.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Workflow state doc conflict 🐞 Bug ⚙ Maintainability

Description

README now claims workflow state is saved in ~/.neoCoder/workflow_state.json, but another repo
document states workflow state is saved to .neoCoder/context.md. This inconsistency can cause
users to inspect/backup/edit the wrong file when trying to resume workflows or debug persistence.

Code

README.md[R413-416]

├── 📄 settings.json        # Agent configuration
├── 📄 models.json          # Model definitions
├── 📄 tool_selection.json  # Tool selection settings
+├── 📄 workflow_state.json  # Workflow state (auto-created)

Evidence

The README change introduces workflow_state.json as the workflow state file, while the manifesto
explicitly calls out a different file (context.md) for workflow state persistence, creating
conflicting guidance within the repo.

README.md[409-418]
NEOCODER_MANIFESTO_EN.md[617-617]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README now documents `~/.neoCoder/workflow_state.json` as the workflow-state persistence file, but `NEOCODER_MANIFESTO_EN.md` states workflow state is saved to `.neoCoder/context.md`. These statements conflict and can confuse users.

## Issue Context
- README config tree lists `workflow_state.json` as "Workflow state (auto-created)".
- The manifesto describes workflow state being saved to `context.md`.

## Fix Focus Areas
- README.md[409-418]
- NEOCODER_MANIFESTO_EN.md[617-617]

## Suggested resolution
Pick the correct/authoritative behavior and make both documents consistent. If both files exist for different purposes (e.g., `context.md` = session context, `workflow_state.json` = workflow engine state), explicitly document that distinction in both places.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Workflow state doc conflict 🐞 Bug ⚙ Maintainability

README now claims workflow state is saved in ~/.neoCoder/workflow_state.json, but another repo
document states workflow state is saved to .neoCoder/context.md. This inconsistency can cause
users to inspect/backup/edit the wrong file when trying to resume workflows or debug persistence.

Agent Prompt

## Issue description
The README now documents `~/.neoCoder/workflow_state.json` as the workflow-state persistence file, but `NEOCODER_MANIFESTO_EN.md` states workflow state is saved to `.neoCoder/context.md`. These statements conflict and can confuse users.

## Issue Context
- README config tree lists `workflow_state.json` as "Workflow state (auto-created)".
- The manifesto describes workflow state being saved to `context.md`.

## Fix Focus Areas
- README.md[409-418]
- NEOCODER_MANIFESTO_EN.md[617-617]

## Suggested resolution
Pick the correct/authoritative behavior and make both documents consistent. If both files exist for different purposes (e.g., `context.md` = session context, `workflow_state.json` = workflow engine state), explicitly document that distinction in both places.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools