Design organization dry-run plans and downstream profiles #6
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
david/library-manager#6
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?
Start M3 by designing and implementing organization dry-run planning from persisted scanner candidates.
Scope:
First M3 organization checkpoint implemented.
Implemented:
internal/organizationAudiobookshelf dry-run planner.Disc Ndestination folders for multi-disc audiobooks.organization_plansandorganization_plan_actionspersistence.make check-organizationfixture smoke command.Verification:
make testpassed.make check-organizationpassed and produced 17 actions: 4 organize, 7 review, 6 hold.Leaving #6 open for the next M3 step: expand organization planning from persisted scanner candidates and continue Grimmory compatibility research.
Progress update: the organization dry-run foundation is now connected to a local Go-hosted prototype. The browser can run the fixture scan, persist scanner/import records, persist the Audiobookshelf organization plan, and review the latest plan. This keeps all operations dry-run/non-destructive. Remaining M3 work: expand planning from persisted candidates beyond the fixture endpoint, define review/apply safeguards, and continue Grimmory compatibility research.
M3 foundation delivered in
ffcbab7.Included:
Verified: make test, make check-organization, make check-large-scan, make check-persistence, HTTP smoke for health/scan/approve/apply, and 9 copied fixture outputs in the temp managed output root.