Clarify hourly conversation naming mechanism and schedule reconciliation - #653
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge decision: ready — operators can choose the existing naming consumer and reconcile its hourly schedule without mistaking a task assignment or a create retry for activation.
User outcome
For the bounded job of inspecting an actor's owned unnamed conversations and assigning concise titles hourly, reuse the naming workflow delivered in #645. Recurring task continuation uses the same scheduler plus a Tasks/chat launch; it is useful for evolving responsibilities but adds task, conversation and execution dependencies to this existing consumer.
Material changes
Document that mechanism comparison in the VWL schedule guide. Explain how to reuse an existing schedule, explicitly resume it, and reconcile an older naming consumer before creating a replacement. The schedule creation hash includes the definition identity and inputs, so a stable caller key alone does not prevent duplicate schedules across configuration changes.
Evidence
Inspected the current naming bundle, recurring-task submission path, actor-owned schedule service and durable scheduler.
pdm run pytest -q tests/backend/test_conversation_naming_workflow.py tests/backend/test_workflow_schedule_service.py tests/backend/test_task_execution_actions.py tests/backend/test_conversation_search_service.py: 38 passed using a mock database and scripted model responses. This includes due-occurrence creation, deduplication, checkpoint recovery, canonical rename read-back and existing/concurrent-title preservation. Diff whitespace and the new local link/anchor were checked.Ship boundary
This documentation change records the current implementation and operational reconciliation behaviour. Live actor-scope definition, schedule and occurrence read-back remain outstanding: this worker has no Von control tools and is prohibited from live mutations through shell. No schedule, assignment, conversation name, represented prompt, running service or deployment is changed by this PR. Actual live title quality and hourly execution remain unverified.