docs: finalize bug_reseed in-container reseed fix (PR #564)

[SoundMindsAI]

Summary

Finalization for #564 (bug_reseed_resolve_engine_base_url_not_idempotent_in_container, squash-merged e7b787a4).

• state.md: PR fix: in-container demo reseed stuck at Scenario 0 (idempotent resolver + Solr data-dir + Arq dedup-retry) #564 prepended to "Last 5 merges"; feat_studies_starting_metric (feat(studies): show starting metric beside best metric in studies list #545) rolled into the older-entries line; branch-context + Last-updated refreshed (now lead with fix: in-container demo reseed stuck at Scenario 0 (idempotent resolver + Solr data-dir + Arq dedup-retry) #564; scenario-clarity noted as next).
• state_history.md: full three-root-cause narrative prepended (idempotent resolver · install.sh Solr data-dir · Arq singleton-dedup retry-clear).

The resolved bug_reseed_failure_blocks_retry_arq_singleton_dedup folder removal + dashboard/roadmap regen already shipped in #564 itself.

Docs-only. No code change.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the project's state and history documentation (state.md and state_history.md) to reflect the merge of bug_reseed_resolve_engine_base_url_not_idempotent_in_container (PR #564). The changes detail the resolution of three stacked issues that caused the in-container demo reseed to fail: making _resolve_engine_base_url idempotent, pre-creating the ./data/solr directory in install.sh to prevent Solr collection creation failures, and deleting stale Arq result keys before enqueueing to allow immediate retries. There are no review comments provided, so I have no additional feedback to offer.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.