Store Seafile references as share tokens and resolve full URLs at sync time, while removing the now-obsolete temporary access notice from the homepage after HTTPS migration.
Constraint: Seafile host/domain can change independently from content manifests
Rejected: Keeping /f/<token>/?dl=1 in manifest entries | repeats fixed URL boilerplate and increases bulk-edit risk
Confidence: high
Scope-risk: narrow
Directive: Keep Seafile manifest values token-first unless a non-standard external link is explicitly required
Tested: npm run build; ./scripts/deploy-homepage.sh --dev-deploy
Not-tested: Manual click-through verification for every share/download link on production domain
Co-authored-by: OmX <omx@oh-my-codex.dev>
SepCometandOmX
afa01ce2af