cleanup(sprint4): scrub stale occurrence/has_extraction/schedule refs
Post-Sprint-4 trivials bundled:
- remove dead occurrence/has_extraction detection in settings routes
plus the now-unreachable Extract toggle UI branch in workspace.html,
and drop the corresponding extract/has_extraction keys from the
generators.json baseline; refresh adjacent docstring/copy that
referenced the removed field
- normalize the schedule generator description to the post-Sprint-3
"anticipated activity records" phrasing in talent/schedule.md and
the three API baselines that mirror it
- fix stale "calendar" in the talent/journal/references/config.md
apps.order example (now "activities")
- replace retired "occurrence" hook value with live "schedule" in
the _format_tags test data
- document the sense.json/sense.md dual-write coupling to
think/cluster.py's per-segment talents/**/*.md glob