Skip to content

Build Toward the Whole: davellm - #5

Merged
DaveHomeAssist merged 3 commits into
mainfrom
law/build-toward-the-whole
Sep 10, 2026
Merged

DaveHomeAssist merged 3 commits into
mainfrom
law/build-toward-the-whole

Conversation

@DaveHomeAssist

Copy link
Copy Markdown
Owner

Applies the Build Toward the Whole patch series.

Commits

  • Remove browser copies of conversation and feedback content
  • Drop hardcoded local model paths from conversation templates
  • Give the responsive access requirement its own identifier

Gate

python -m pytest -q — 71 passed — passing locally on this branch.

Not for merge yet.

PROJECT_SPEC section 8 states that the browser may persist only the
allowlisted suggestion preferences and that prompt and response content is
forbidden from persistent browser storage. The renderer still wrote the full
conversation map to localStorage under dave_convos, wrote 200 characters of
each rated response under dave_feedback, and silently restored the browser
copy when the router was unreachable. That created a second, diverging
conversation store beside dave_conversations.json.

The renderer now treats the router as the only conversation source, leaves
the list empty and logs the failure when the router cannot be reached, stops
mirroring feedback content, and purges the two legacy keys at startup. The
renderer contract test now asserts the absence of the browser mirror.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01656XvdqNAVojSPQBtLZAAt
The three conversation templates carried preferred_model values that were
absolute llama.cpp GGUF paths on one personal desktop plus a relative
./models path. None of them can ever appear in an Ollama node inventory, and
because the template value was consulted before the project's own setting,
a project's preferred_model was never reported for a templated chat.

Templates no longer carry a model preference and the from_template response
reports only the project's preferred_model. The unused DEFAULT_MODEL_ID
constant is removed with them. MODEL_CATALOG still holds the same legacy
paths for the advisory routing and cost endpoints; that is reported
separately because retiring or rewiring it is a product decision.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01656XvdqNAVojSPQBtLZAAt
PROJECT_SPEC listed two different requirements under FR-25, exact-call
approval and responsive access. The second row is now FR-26 so each
functional requirement has one identifier.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01656XvdqNAVojSPQBtLZAAt
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@DaveHomeAssist
DaveHomeAssist merged commit e7fa5d8 into main Sep 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants