DATA-001 follow-up: substrate.retention module never landed — closed #163 has no implementation, breaks test collection #269
Labels
No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/mesh-seed#269
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Issue #163 (DATA-001: Data Retention Policies) is closed, but its implementation module
substrate/retention.pydoes not exist anywhere in the repo (checked all branches). Only the tests landed:tests/unit/test_retention.py(452 lines, committed in769e229)tests/integration/test_retention_lifecycle.pyBoth files import from
substrate.retention:Impact
pytest tests/unitfails at collection withModuleNotFoundError: No module named substrate.retentionpytest tests/integrationfails the same wayThe ledger methods the tests also exercise are likewise absent:
list_intents_for_cold_deletion,mark_intent_cold_deleted,delete_intent_hot_row,delete_expired_logs,record_retention_run,get_retention_runs,record_deletion_audit,list_deletions_since,retention_current_state— none exist insubstrate/ledger/core.py.The only related code that did land is
list_objects()on the cold-storage backends (insubstrate/cold_storage.py, same commit), plus a stale.gsd/salvage-state-Mark_mesh-seed_163.jsonclaiming Implement completed.Expected
Either implement
substrate/retention.py+ the ledger methods per the DATA-001 acceptance criteria (configurable retention periods, automated deletion, archive-before-delete, compliance reporting), or explicitly mark #163 as not-delivered and decide whether the tests should remain.Severity
HIGH — closed issue without implementation; breaks full test suite collection.
Fix landed — closing
Implementation for DATA-001 (retention) delivered in commit
8e4d491on origin/master (feat(#269): implement substrate.retention module).substrate/retention.py(686 lines) — RetentionPolicy, ArtifactRetentionPolicy, IntentRetentionPolicy, LogRetentionPolicy, CompliancePolicy, ComplianceReporter, DataRetentionScheduler, RetentionCleanersubstrate/ledger/core.py(+240) — all 9 missing ledger methods: list_intents_for_cold_deletion, mark_intent_cold_deleted, delete_intent_hot_row, delete_expired_logs, record_retention_run, get_retention_runs, record_deletion_audit, list_deletions_since, retention_current_statesubstrate/ledger/migrations.py(+61) — retention/audit tablesVerification (fresh run, repo .venv):
Test collection no longer breaks. Per the issue: implementation per DATA-001 acceptance criteria (configurable retention periods, automated deletion, archive-before-delete, compliance reporting) is delivered.