Commit History
Yesterday
-
[NOTICKET] feat(scope): relative periods resolved against today and applied by code (P0-5)
Rifqi Hafizuddin +1: Claude Opus 5.5"6 bulan terakhir" ran as week 1–44 (the whole year); the planner.md rule was prose only. period.relative_window (D7, WIB): "N bulan terakhir" = the N complete months before today's month; bulan lalu/ini, tahun lalu/ini, kuartal lalu/ini. Released to the planner: windows across two years, period comparisons (YoY, "dibanding tahun lalu"), "N bulan lalu", open ranges, weekly. A period comparison releases even when one side parses (review round 3). Comparisons against a target or between sites keep the window. All-time wording ("selama ini", "seluruh data", "ever") releases. The scope hook takes `today`; the planner eval passes each case's date. Scope line hides only `*_id` next to its code column. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>621aed1 -
[NOTICKET] fix(scope): lookup artefacts and typed site ids (P0-4)
Rifqi Hafizuddin +1: Claude Opus 5.5- only a `${tN.col}` value handoff marks tN as a lookup; a Pattern-A `${t2}` data feed made the answering query a "lookup", so the line fell back to the site lookup and read "(sebagian kueri)". - _strip_broken_id_filters strips both FK ends: a typed `vw_dim_site.site_id = 2009` (Check 8j rejected it, costing a retry). - the scope line no longer prints `site_id 2009` next to `site_code IPR`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>effd6af -
[NOTICKET] feat(scope): apply the user's own clean window by code too (P0-1b)
Rifqi Hafizuddin +1: Claude Opus 5.5Sofhia's analysis a67625f2: two turns typed "Juni–September 2026" and the planner still ran `month 6–9` with no year, reading June–September of every year. The P0-1 release ("the user named a period → planner keeps it") left that unfixed. period.turn_window: the user's own clean window → applied; months without a year → the objective's year; an unparsed period of the user's ("6 bulan terakhir", two years) → released to the planner; no period → the objective. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>fc63682 -
[NOTICKET] feat(scope): the analysis objective's period is applied by code (P0-1)
Rifqi Hafizuddin +1: Claude Opus 5.5Site/section were code-owned; the period rested on one planner.md line and was dropped or invented on casual questions (Jun–Sep 2026 objective read Jan–Sep; A/B test and correlation read every year; a planner typed 2025). - scope/period.py: parse the objective window ("tahun 2026", "Jun–Sep 2026", "Juni s/d September 2026"); no default for Q/semester/lists/"mulai Juni" or 4-digit ids ("site 2009"). Applied to every retrieve_data, replacing the planner's filter on the same period columns; ISO weeks on week-only tables. - Released when the user's own words name a period, when the plan forecasts, or when the queries compare periods (by column name). - TurnScope.periodic + "semua periode / all periods" in the scope line; period filters render first and outside the other-filters cap. - Never-throw; two independent review rounds (5 blockers fixed). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>5e5b0e3
5 days ago
-
planner (#26)
- [NOTICKET] feat(scope): code-owned conversation scope — focus from value lists, follow-up carry, scope line (111ef6b9f94acaae6932782799d7fc3c0364e845) - [NOTICKET] feat(chat): status pings always in English (144494152cfba32196cb64e75b44548a031778cc)e0411e5
