提交图

2 提交

作者 SHA1 备注 提交日期
600b07e15c test: locate the companion repo instead of assuming one layout
test_m6_r2_real_dto_shape resolved the companion repo as a sibling directory,
which is only true of the development checkout. On the VM the skipif was
always true, so the seven cases that exercise the companion's real DTO builder
-- the only genuine check of the cross-plugin envelope shape -- never ran in
the environment that most needed them, and a skip shows up as a missing dot
rather than a failure.

test_ops_migration had the harder version of the same bug: the import simply
failed, and working around it with PYTHONPATH let the memory side's own
core/ops_migration shadow the companion module, producing two failures that
looked like product defects and were not.

Resolution now lives in tests/_companion_repo.py and tries, in order, the
COMPANION_PLUGIN_ROOT override, the sibling development directory, the
sibling deployed directory (_ops suffix), and one level up. The path helper
inserts at the front of sys.path deliberately: getting that order wrong fails
as "green but testing the wrong module", which is worse than an ImportError.

Memory suite 330 passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 05:41:32 +08:00
809a1ed3bb feat: add explicit memory data migration 2026-07-24 21:11:02 +08:00