chore(cleanup): remove dead crates code and stray config/seed/test cruft #220
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/pms-202-remove-dead-code"
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?
Remove dead structs, traits, params, and config fields across the workspace crates, plus stray config, seed, migration-gap, and test cruft surfaced by the platform audit. No behavior change: every removed code item was dead (an unused export, an
#[allow(dead_code)]-annotated helper, or a config field read only by a Debug impl).Crates: drop the unused
CurrentUserextractor; remove theNowOrDefaulttrait (callers useClock::nowdirectly); drop the unused_user_agentparam onverify_only; remove_enforce_user_id_usedand the unusedUserIdimport in signup; delete the never-usedRefreshTokenRow/RefreshFamilyRowrows and theirFromimpls; drop the 4 deadAuthConfigbool fields and the now-unusedparse_boolhelper; drop the 3 deadEngineConfigTTL defaults; remove the supersededUserRepository::list_by_tenantandAuditLogger::list_recent; drop the unused_verifying_keysmap; delete the never-constructedTicketActivityenum.Stray: remove the dead
ticket.sla_warning/ticket.sla_breachseed templates (no emitters); replace the hardcoded developer LAN IP in the demo script with alocalhostdefault; add a20260506000007_DELETED.mdplaceholder documenting the intentional auth-migrations gap (sqlx ignores non-.sqlfiles); document multi-tenant-only tenancy in the README now that thesingle-tenantcargo feature is gone (PMS-262); provision anE2E_FOREIGN_COMPANY_IDfixture inglobal.setup.tsso the cross-tenant company canary runs unconditionally; remove the spurious same-file#[allow(dead_code)]annotations in the contacts and knowledge_base integration tests.#PMS-202