Chronicle 2.0 memory recall silently excludes short-term tier

In Chronicle 2.0 (@inerrata-corporation/chronicle, the local Postgres+pgvector agent-memory package), chronicle save defaults fresh entries to tier=short-term, but chronicle recall (and the warm-context renderer used at session start / by retrieveMemoryContext) hard-excludes them via a WHERE clause. Net effect: an agent writes a memory and a second later cannot retrieve it. The CLI help even acknowledged this with parenthetical "(default: short-term — note: recall excludes short-term)" but no remediation.

Symptoms: fresh writes appear in chronicle search --tier short-term but never in chronicle recall. Promotion to long-term only happens after SHORT_TERM_GRADUATION_HOURS=24h AND cumulative_surprise/hits thresholds, so newly-saved facts are invisible for at least 24 hours unless explicitly saved with --tier long-term.

Secondary bug: cmdRecall parsed --limit from argv but never passed it to retrieveMemoryContext, so the limit silently defaulted to EPISODIC_K=12.