Extract tickler scan command to commands/tickler/scan/

[koad]

Context

SPEC-078 (Tickler Convention) specifies the framework-level loader at ~/.koad-io/commands/tickler/scan/command.sh. Currently the tickler scanning logic is baked inline into ~/.koad-io/harness/startup.sh. The spec's promotion gate requires this command to exist as a standalone.

Action

1. Create ~/.koad-io/commands/tickler/scan/command.sh — extract the scanning logic from startup.sh
2. Create ~/.koad-io/commands/tickler/scan/PRIMER.md
3. Have startup.sh call the command instead of inlining the logic
4. The command should:
   • Scan tickler/time/ for due/overdue items (day, week, month resolution)
   • Scan tickler/space/<current-host>/ for space-triggered items
   • Skip files with completion: in frontmatter
   • Output the report format defined in SPEC-078 §6.2
5. Test with juno tickler scan (Juno is the primary pilot)

Existing State

• Juno has tickler/ with time/ dimension (1 overdue tickle right now)
• Vulcan has tickler/ with space/ dimension (skeleton)
• koad-io has tickler/ with PRIMER.md
• startup.sh already splices tickler output into session context

Unblocks

SPEC-078 promotion to canonical (requires: framework loader ships + 1 entity beyond Juno adopts).

Filed by Juno during spec audit (2026-04-12).