astrbot_plugin_private_comp.../tests
YokiiroBW 2518f7b6bf fix: make the daily plan chain survive startup timing and same-day rewrites
Two defects that only showed up on the real machine, both of which left the
schedule frozen on a fallback plan with nothing in the logs to say so.

The plugin asked for a chat provider 0.8s before AstrBot finished loading
them, wrote a template fallback, and stamped it with today's date -- so the
next 24 hours never retried. Resolution now falls back through get_config()
(4.26.6's Context exposes nothing else) and validates the configured id with
get_provider_by_id, because a configured default is not a loaded instance.
When nothing is ready yet the round is skipped instead of downgraded, up to
DAILY_PLAN_PROVIDER_MAX_WAITS rounds.

Once the model recovered, the real plan still could not reach the archive:
the idempotency key is always daily_plan:<date> but the plan dict never
carried a version, so every rewrite re-sent v1 and the memory side rejected
it as version_conflict. The companion swallowed that -- outbox state is only
touched when enqueue accepts, and a same key/version enqueue does not. Plans
now carry a version watermark drawn from both daily_plan and its history, and
any ok=False archive response logs a warning regardless of outbox state.

Verified on the VM: provider wait counted once and no fallback written, plan
generated at v2 with 10 segments from the model, and the stored record
upserted from the 8-segment fallback to the same v2 content.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 04:16:06 +08:00
..
__init__.py feat: add safe companion data migration 2026-07-24 21:10:46 +08:00
_host_stub.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_agenda_system.py feat: isolate bot self storage from user memory 2026-07-25 23:22:41 +08:00
test_agenda_window_labels.py fix: disambiguate the two late-night windows on the timeline 2026-07-27 03:02:00 +08:00
test_audit_batch1.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_bot_self_store.py feat: isolate bot self storage from user memory 2026-07-25 23:22:41 +08:00
test_calendar_system.py feat: add temporal companion calendar 2026-07-25 01:35:56 +08:00
test_daily_plan_version.py fix: make the daily plan chain survive startup timing and same-day rewrites 2026-07-27 04:16:06 +08:00
test_m6_bot_personal_bridge.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_local_loop.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r1_maintenance.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r2_legacy_compat.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r4_creative_media.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r5_profile_injection.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r6_runtime_view.py feat: complete M6.1.3-R2 through M6.1.7 bot personal archive contract 2026-07-27 01:37:40 +08:00
test_m6_r7_privacy_residue.py fix: decouple MemoryCompanion bridge from LivingMemory switch; drop LivingMemory 2026-07-27 02:11:18 +08:00
test_provider_readiness.py fix: make the daily plan chain survive startup timing and same-day rewrites 2026-07-27 04:16:06 +08:00
test_q7_backend_contracts.py feat: freeze ops backend page contracts 2026-07-26 00:05:56 +08:00
test_temporal_context.py feat: add temporal companion calendar 2026-07-25 01:35:56 +08:00