Commit History
Yesterday
-
[NOTICKET] fix(aggregate): RANKING description is for median rankings only
- The RANKING paragraph (#10) read as "any ranking goes here"; on the relative_last6_months_id eval case 5.4 mini once pulled raw rows and ranked them with analyze_aggregate instead of grouping in the query (Rifqi, audit A1-F7) - Now: only a median ranking sets sort_by/top_n here; a sum/avg/count/min/max ranking is a grouped retrieve_data with order_by + limit, matching planner.md:107 - sort_by example changed from is_bad_actor_sum to pa_median - Median rankings (units by PA, sections by MTTR): analyze_aggregate + sort_by + top_n 6/6, same as before; 6 avg/count ranking eval cases 6/6 via retrieve_data; relative_last6_months_id 3/3 via retrieve_data - Full suite 403 passed, 6 pre-existing failures Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>94de89b -
[NOTICKET] fix(validator): reject an aggregate alias that names another column (#16)
- Test demo #16 (chat 2 Q6, Q8): `AVG(mtbf) AS avg_mtbs` passed, and the answer reported MTBF as MTBS; only Traceability showed it - _reject_misleading_aliases only caught an alias equal to another column's name - New _alias_stem(): strip one aggregate prefix/suffix (avg_, sum_, total_, min_, max_, _avg, _mean, ...) and reject when the rest names a different column; retry follows - Replay of 346 stored retrieve_data IRs (all analyses): only Q6, Q8 and the old `ma AS backlog` are rejected, no new false rejects - Local tests; full suite 403 passed, 6 pre-existing failures Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>db195e3 -
[NOTICKET] feat(report): trend evidence shows rows per period and stub periods
Rifqi Hafizuddin +1: Claude Opus 5.5When analyze_trend reports per-point `n` / `stub` (P0-8), the evidence table reads period · value · n · note ("few rows" on a stub); older records keep period · value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>493b0b8 -
[NOTICKET] feat(assembler): stub periods and weak results are worded as such (P0-11)
Rifqi Hafizuddin +1: Claude Opus 5.5Sofhia's local run (analysis a67625f2) after P0-8: the trend answer opened with "puncak pada September" on a 9-row stub month, and a weak correlation (n=4) opened with "Ya" without p. One assembler.md bullet: a stub period is never the peak, the lowest point or where a trend ends; a weak result does not open with a plain yes/no and gives n and p when present. Prompt change: a small chat check is still to run (tracker). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>632caf8 -
[NOTICKET] fix(query): GROUP BY without an aggregate is DISTINCT on uploaded files (P0-10)
Rifqi Hafizuddin +1: Claude Opus 5.5The pandas compiler applied group_by only with an aggregate, so `SELECT site_code GROUP BY site_code LIMIT 50` on a tabular source returned 50 raw rows. The scope value index for uploaded files therefore held only the first rows' values (analysis da688944: site_code ['LAT','BIN','SDJ'] of 7; section missing OB LOADER), marked complete, and the objective's site ADT was never pinned — Sofhia's "ADT lost" turns. Now drop_duplicates() after the select, matching SQL; the rendered query shows it. Same turn's value index now loads all 7 sites and the objective resolves to site_code ADT + OB HAULER. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>d20cd21 -
[NOTICKET] feat(correlation): pairwise n, p-value and a quality block (P0-8)
- Each pair now carries n (rows complete for both columns), p_value (scipy pearsonr / spearmanr / kendalltau) and weak (n < 10 or p >= 0.05) - Reserved `quality` block for the strongest pair, so CK7 surfaces a weak correlation; a caveat says one point can drive r on few rows, or that a large-n r is not significant - With no column_ids, `n_*` row-count columns (the repair's n_periods) are skipped - ADT OB HAULER monthly means: PA-MTTR r=-0.42 now reads n=9, p=0.26, weak; unit-month rows (n=2,379) stay strong; a ranking table no longer correlates n_periods - Reported by Rifqi (audit P0-8, decision D4) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>1ac2267 -
[NOTICKET] feat(trend,forecast): row count per period and stub flag (P0-8)
- Each trend point and forecast history point now carries `n` (rows) and `stub` - A stub has fewer rows than half the median non-empty period (needs >= 3 periods); empty periods are not stubs - analyze_trend leaves stubs out of first/last, direction, slope and R^2, with a caveat naming them; it falls back to all periods if every one is a stub - analyze_forecast still fits every period but caveats a thin last actual period - IPR OB LOADER (Sep 9 rows vs 63-66): sum(mtbs) "down" -> "up" (R^2 0.01 -> 0.91); mean(pa) last 99.95 (Sep) -> 92.45 (Jul) - Reported by Rifqi (audit P0-8, decision D4) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>50cae40 -
[NOTICKET] fix(trend,forecast): a period with no rows stays empty (P0-8)
- resample().agg("sum") turned a month with no rows into 0: the trend read it as a collapse and the forecast fitted it as a real value - New temporal._resample(): sum uses min_count=1, so an empty period is None; count keeps 0 (zero events is the true count); other aggs were already None - analyze_forecast uses the same helper, so the empty month is interpolated for the fit - Example (April empty): trend R^2 0.06 -> 0.90, forecast no longer dips after "April 0" - Chart already draws None as a gap; the report table shows it as a dash - Reported by Rifqi (audit P0-8, decision D4) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>f28898b -
[NOTICKET] fix(planner): a failed plan is not a data gap (P0-9)
Rifqi Hafizuddin +1: Claude Opus 5.5TaskList._exhausted (private attr, not in the model's schema) marks a plan that failed validation on every attempt; the coordinator shows its own text without the data-gap lead. New EN/ID texts (register "Anda"): the plan failed its checks, which does not mean the data is missing; ask more specifically. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>863bf8e -
[NOTICKET] feat(report): cap answers on a weak model fit, not on a non-significant test (P0-7)
Rifqi Hafizuddin +1: Claude Opus 5.5anchored._weak_fit: when analyze_importance / cluster / forecast / anomaly mark their own quality weak, the answer is at most "partially answered" with the fit in the reason; a weak primary sorts behind a clean one; limitation line. analyze_ab_test is excluded (weak there = "not significant", a valid answer). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>5595f0e -
[NOTICKET] feat(report): summary written after the per-question answers (P0-6)
Rifqi Hafizuddin +1: Claude Opus 5.5ReportSummaryNarrative field order = generation order: bq_answers → title → executive_summary → next_analyses; report_summary.md: the summary restates the answers only. Analysis 2d841e2f's summary had contradicted its own Q4 band counts. Prompt change: report fixture + 7-question gate pending (tracker). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>d8c4759 -
[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(router): short follow-ups take the route of the answer they follow
- Test demo Q2: "unitnya yg mana aja?" after a model ranking (and a chart turn) was routed to `check` and listed the data sources instead of the units - Reproduced with the real chat-1 history: `check` 3/3 runs before, `structured_flow` 3/3 after; "sitenya mana aja?" the same - `check` definition: asking which rows/entities in the data match is not inventory - New follow-up rule: a short follow-up keeps the previous answer's route (analysis -> structured_flow, document -> unstructured_flow, source/column list -> check) - One few-shot in another domain (sales branches), not the demo sentence - Intent eval 56/57 before and after; the one miss (unstructured_04) predates this Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>35886db -
[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(assembler): show what ran; label planner notes as pre-execution (P0-3)
Rifqi Hafizuddin +1: Claude Opus 5.5A planner note ("no site-code mapping for IPR") reached the answer and the report under a scope line showing IPR applied; a "last 6 months" objective was repeated over a query on weeks 1-44. - render each retrieve_data as "(ran on <table> · <n> rows · filters: …)". - carried open_questions labelled "Planner notes, written BEFORE the queries ran (unverified …)"; assembler.md open_questions line matches. - Prompt change: 7-question chat_sim gate still to run (tracker). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>04d356d -
[NOTICKET] feat(planner): rows of a per-period table are not entities (P0-2)
Rifqi Hafizuddin +1: Claude Opus 5.5"equipment mana yang PA-nya paling rendah tahun 2026?" ranked raw month rows (one 8-day April row read as the unit's 2026 PA). - validator Check 8m: an ordered+limited ungrouped query on a year/month/ week/quarter table must group by the entity or select the period column. - validator Check 8n: analyze_segmentation may not band raw period rows. - IRRepairer: a grouped ranking over such a table gets COUNT(*) AS n_periods (not when grouped by a period, not when it already counts). - Replay of 135 stored planner-eval plans: 0 new rejects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>63e17f7 -
[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 -
[NOTICKET] fix(planner,ab_test): Check 8h reads the selected month column; "1" matches 1
Rifqi Hafizuddin +1: Claude Opus 5.5- validator Check 8h looked `month` up by NAME across the catalog and took the last one; on the EMA source that is a decimal column in another view, so a month-without-year trend passed and failed at execution (Luna demo run 2026-11-03, Q2). 8h and 8l now share _upstream_column, the exact column the upstream retrieve selected. - analyze_ab_test: when the exact group match finds no rows, a group written as text matches the same number and vice versa ("1"/"0" on an integer 0/1 flag raised GroupNotFoundError, Q5). Exact matches take the old path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>b820983 -
[NOTICKET] feat(llm): LLM_PROFILE selector for the chat LLM quad (54m default, 6l trial)
Rifqi Hafizuddin +1: Claude Opus 5.5- settings: azureai__*__6l quad + LLM_PROFILE (default "54m"); call sites read settings.llm_* instead of the _54m fields. Fallback = one env var + restart. - GPT-6 Luna on chat/completions refuses function tools (every with_structured_output) unless reasoning_effort="none", and accepts temperature 0 or 1 only: llm_reasoning_effort / llm_temperature() handle both. For 54m they send exactly the previous request (reasoning_effort=None is omitted, temperature unchanged). - eval: intent/help runners label the active deployment; chat_sim gains the ema_demo suite (the BMDP 7-question script) and Suite.business_questions. - CONTEXT.md: profile note. The demo stays on 54m. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>268ef5d -
[NOTICKET] fix(report): no default chart for descriptive evidence
- Since 0e64f6ba a descriptive answer's report evidence is its statistics table (column, count, mean, median, std, min, max). - analyze_descriptive draws no chart, so _default_chart built one from the first measure, `count`: "Count by column" with identical bars (1080 x 4 on the test-demo Q13 record). - The other statistics mix units (PA in %, MTBS/MTTR in hours), so no single bar chart reads right. - _default_chart now returns None when the record ran analyze_descriptive; the statistics table stays, rankings keep their default chart. - Reported by Rifqi in the review of 3 Nov. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>9f5b58c -
[NOTICKET] feat(report): evidence tables for cluster, anomaly, descriptive, data-quality and forecast
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>0e64f6b -
[NOTICKET] feat(aggregate): optional sort_by / top_n for rankings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>a79d8da
2 days ago
-
[NOTICKET] fix(demo): tool-result evidence, trend chart, week-column check, importance baseline, source-name repair
Rifqi Hafizuddin +1: Claude Opus 5.5Fixes from the 2026-11-02 demo test (analysis 2d841e2f): - report: evidence table comes from the analysis tool's result (pareto, segmentation, ab_test, trend, correlation, importance), not raw rows - analyze_trend: auto line chart + value_column in the output - validator Check 8l: reject trend/forecast on week-number date columns - analyze_importance: weak when accuracy <= majority-class baseline - IRRepairer: source name in source_id -> that source's id (unique only) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>21fd955 -
[NOTICKET] feat(cluster): name example members per cluster
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>cf34801 -
[NOTICKET] fix(data-quality): fix missing-rate chart axis to 0-100%
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>0fb7af8 -
[NOTICKET] fix(anomaly): scatter skips low-variety axis columns
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>5af2746
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
7 days ago
-
/fix demo prep (#25)
- [NOTICKET] fix(planner): match the question's time grain; reject non-task placeholders (ac68af5f1fedb87cd64b206a25c539136e1e491e) - [NOTICKET] docs(plans): report reframe and prompt cleanup plan (1acca723005e9ce364981a6e8e20684dc41dddee) - [NOTICKET] feat(report): question-anchored report with scope, checks and an analysis ledger (564c8270c31e0729288f251c918ea075ed042ae7) - [NOTICKET] fix(report): English structure, content in the user's language (99ed8a1a0af610180bd77a65bb952d79aa7fd906) - [NOTICKET] refactor(prompts): one home per rule — planner.md 7.1k -> 3.9k tokens (71c6f2b2bf958186f1d0b430b237229f5fdcf03d)4a5f122
8 days ago
-
/fix help and active tools (#24)
- [NOTICKET] fix(help): suggest the analytical tools that are now active (b1ef6f048c8dd469a7f3d2214fae3bbfe7da4e46) - [NOTICKET] eval(help): capability cases for the v7 tool sync (87bb688ca6d8b1de28e3f911bf8502ab504012d3) - [NOTICKET] fix(chat): load the latest history, not the first ten messages (b3a1a3557a8946a0d493084be741105e0293f45e) - [NOTICKET] docs: sync REPO_STATUS, DEV_PLAN and contract with the code (19587bc335e857a2d3c992b9d2fd16e0b7e37159) - [NOTICKET] docs: close DEV_PLAN #32 — live Neon matches Go 0007 (17b54e212416e06fe32e3942ebf951856b03792e) - [NOTICKET] fix(report): no user-scope catalog fallback in the data-source appendix (35a6aedb48870a8c6007b845c7a5ff1d0f57c324) - [KM-717] feat(planner): read the catalog data dictionary into the planner's catalog summary (2d70efebcdfecd9f1fce6cfa43c5e304bf6edbe4) - [KM-717] eval(planner): data-dictionary cases, and live Neon knowledge tables verified (97b27d162f937dfe302e17c432a7e76e3cdfb937) - Merge remote-tracking branch 'origi…00ca133
-
/fix planner and unstructured pipeline (#23)
- feat(documents): v2 unstructured ingestion, image-token, scoped retrieval (b848f739c23c9ea152c5bcc5ea4b9d8b4ca64afa) - feat(prompts): mixed document+data path, figure markers (39019d57e159b510fda1f5bd813d051e1ba7c05c) - eval(chat_sim): doc + mixed suites with bound documents (b6e060b328c8dbbdb19f3da466fe97f62dab09aa) - [NOTICKET] docs: unstructured v2 plan, contract, status sync (6702119c2705ef9a99a4a0ba0adaab9ac7a28c54) - fix(check): list data and documents when both are asked (2b7c3bd79fe73b693634e583be46c812b6c74d3c) - [NOTICKET] docs: mixed suite result, check + router fixes, U8 done (0e1ad6e143e30ec20960d3a2c5ae22190aa512ff) - feat(router): a figure IN a document vs a chart FROM data (770b98855d640c727a402b0db1252638364c20d7) - fix(chatbot): reply in the turn's language, not the documents' (b6150d58b991fb5d98b0bb2278956c938d80d4c0) - fix(query,planner): stable capped rows, plan-time handoff check, trimmed records (ea9848db5ec39e32067a2c3dbc9453f1a94736d2) - eval: scoped/DB/docum…7124acf
-
/feat ds tools (#22)
- feat(tools): analytical-tools foundation — spec_builder + ml executor (ee1a76a466c6ea6dc52f337d0fd9534ca0271a86) - feat(tools): shared chart kit + auto-chart builders (535f17340950e070556441140276c47d074606e2) - feat(tools,spine): wire tool auto-charts to chart persistence (522e582bab372b645577789cbbd59d5105a66632) - build(deps): add statsmodels + explicit scikit-learn pin (4d76bd0e57f5f7b1bbb0b77e49970063d1898a1b) - [NOTICKET] docs: analytical-tools foundation — conventions, DEV_PLAN 0.9, status sync (a7f0bca51ed8ff08784cca3fd4179dce56ef7622) - [NOTICKET] eval(planner): skip cases whose tool is withheld, don't fail them (845284b4a3b32df142565de23386dee739d0f733) - [NOTICKET] feat(tools): analyze_forecast (ETS) — first ML tool, DEFERRED (dae102f68fc36cf755e7d53df10affb4ec7edaa6) - [NOTICKET] planner: rebalance few-shot exemplars EN/ID, demo the reply-language rule (fb30aec99586daf12a4799087ae538e5e862451c) - [NOTICKET] feat(tools): analyze_anomaly (Isolation Forest) — second ML tool,…e201ae4
-
/fix parsing and term extract (#21)
- [NOTICKET] fix: retire the fuzzy clustering pass; add E1c post-cluster recall (2cc21c92688d662c5cfdfeeb6784bb85b98575ca) - [NOTICKET] feat: parsing schema 0.4.0 — asset pointers for figures and tables (e662ac089b741c90e19b9f51f4933fb97a1225bc) - [NOTICKET] docs: sync REPO_STATUS / DEV_PLAN / contracts for pipeline v2 (c3c184d83bec4a4d42e9ad3f7265560802817e5b) - [NOTICKET] docs: close K15 with the paid v1-vs-v2 comparison (62782fed9292f67d7b376783920a07197d6776e9) - [NOTICKET] fix: test the caption hypothesis; ship the signal at weight 0.0 (36a166e1844d186d6cfb8fff9ea070f3dc69b220) - [NOTICKET] fix: cap key-parameter pre-emption in the review queue (Step 2) (4e3a6aefef7024db3ea4b7946fd7771a6c269601) - [NOTICKET] feat: assert on invariants, report a band, classify the genre (Steps 0 + 5) (f1d64b113db0289601806635a9b154201a6127fc) - [NOTICKET] fix: gate spend in cluster units and surface the estimate (Step 6) (cdb5fe82cc5f2893ccbb5e28282e8dc46a27e061) - [NOTICKET] fix: retire escalation…f07443e
-
/feat knowledge management (#20)
- [NOTICKET] docs: knowledge pipeline test integration — context, audited task checklist, DEV_PLAN §0.8 (8e69dc6c638509f4dd7b6775d520fb4aa4efbd3e) - [NOTICKET] docs: knowledge pipeline — reframe kex as prototype, not port target (7cce5ffc9ab88791ac139dbef8e88e124a3d049e) - [NOTICKET] feat(eval): knowledge-extraction gold set, scorer + frozen prototype baseline (60cf4a885ef31a8aa64916f5a70ac5a0e8062c5f) - [NOTICKET] chore: add missing planner and readiness eval results (bd6659b3bf523597e4482b04ab1fcff5e1284d25) - [NOTICKET] feat(knowledge_extraction): free stages — models, seam adapter, filters, cluster, ranking (024c30abd1189119d33508eded334fe5a3ed5011) - [NOTICKET] fix(knowledge_extraction): move runner into the package; fix two ranking defects (72605ff6876a7936ab685d417c766ce820f6214b) - [NOTICKET] feat(knowledge_extraction): span filter — E1 recall 0.8537, matches the frozen baseline (3a016343398753cf730d50548c0e92ff47c6716c) - [NOTICKET] feat(knowledge_extraction): paid extraction …b68816f
-
/fix planner count and report (#19)
- /fix planner count question (11de970ff65be9b4f81f773cfb355d3dc57358d7) - [noticket] fix report bug where some answered analysis isnt included in report summary answers (8dec1825cf803ad28f4ff0400b9c373250a7d90a) - [NOTICKET] fix: split report floor from report body; scope analysis reads by user_id (fd4865b20dfc46782706be9aab318f909b9903c3) - [NOTICKET] docs: sync report floor/body + security posture; add review remediation tracker (fc5200c994441ec505ea7a82469da577afe170a5) - [NOTICKET] test: planner eval harness (rule-compliance, --selfcheck/--rescore) (4292522aa3fa3a7af8f933307334cb7e5eb0b377) - [NOTICKET] eval: repair readiness harness; commit intent/help/readiness baselines (08a0a4ad5eacc6c90df22fab5be69f2d33579f29) - [NOTICKET] fix: compiler parity — F-17 fabricated column, F-18 LIKE nulls, F-25 empty in/not_in (8f736f90f1958960a83847d332b45b13fa346168) - [NOTICKET] feat: bound catalog render + blob read; scope charts/traceability; mark degraded seams (0cb7d53cb6f7f7e7b687dd6d9c27…f282b15
-
/fix report not working (#18)
- [NOTICKET] fix: write reports.user_id (Neon NOT NULL column broke report persistence) (13f74e11df6058800f71e539fe135eeba7576f24) - [NOTICKET] docs: correct 13f74e1 root cause — Go migrations are non-convergent (86d0805130637d66082c5a75b8da71fae36002ad)9070d67
-
/fix change model to gpt 5.4 mini (#17)
- [NOTICKET] chore: rename LLM env quad __4o -> __54m (GPT-5.4-mini) (790ef0c7aaac6e76eb01b0ef9a3398ff4249416d)d65c41d -
fix/ check and new chart tool (#16)
- check: table-level column drill + drop misleading "name a table" hint (ef0c7b1c5aa49a244b02f1b5eea15cc77dcf2bcb) - [KM-715] charts: render_chart tool + message_charts store + GET /api/v1/charts + planner viz slice (87cfcf884d923ee4bcd722e0e4ef4d90d7eaedca) - [KM-715] checkpoint: S1a deterministic quality checkpoint between runner and assembler (f3c8de34dc19a573031b67fd4f48dcfbadcdfed8) - [KM-715] docs: sync REPO_STATUS/DEV_PLAN + land SPINE_V2_PLAN (W1/W2 done) (434eacbf2ac8324188ebe5e32775dbc9d2a3f49a) - planner: value-handoff (${tN.col} → list) for tabular lookup/anti-join (54070ac1407b751000e49dfe7f102a2be5ab1ff8) - [KM-715] charts: GET /charts by message_id only + tri-state status marker (b8d15761addf4d499c9631df64e7693aa1d61fa2) - [KM-715] report: embed charts as plotly EDA fences; render_chart counts toward the floor (89db8be6b6f11e86ad0776d2ee07f2306e3b6079) - [KM-715] docs: contract + status deltas for the charts lead-review round (96347ee7c55a4eb39a906409ec214463e25c5e35) - …5a60e93
-
/fix traceability (#15)
- [KM-691] Traceability: add resolved data_used layer for the FE (a646735e33f6ac725d0756a88956b0aec15fe495) - check: don't leak user-scope catalog when analysis catalog missing (c0ba82938383169b41059c4125765db5275885e7) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>32abc41 -
/fix help and tools analyze (#14)
- [KM-711] Retire /report slash command; report is Generate-button only (f7f7b172da0dc16adac0a7555f6d34a704cc2050) - fix(analyze_trend): handle value_column == date_column (count events per period) (55e3327f7b2e21a954b317e143f46bcea8b5ada7) - [KM-711] Docs: drop /report from list_skills catalog examples (0772863b296e2ed3e2d559df05e98540764e58b0) - fix(planner): reject inlined table-ref as analyze_* data (Pattern A) (776fae3c7c6e3d3a07c22bef10898f6b1c33c701) - fix(analyze_aggregate): reject non-string group_by (CASE/binning) keys (b40fa76e2fa68572dad0d8532e07076207095d6b) - fix(planner): reply-language for infeasible_reason + answer-only-asked rule (4d89d7d93938e41892979cd20e5ccf0c97441dac) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>17e31c6
-
/fix planner and report (#13)
- [KM-644] planner: infeasible plan outcome + entity-ranking few-shots (089b69d9b6111e813307c6afbd3e7613bb823f9d) - [KM-644] harden query path: grouped-select rule, int-date trends, sample decode, trace guard (74ad5261736bda0bd72bccdb41565ea67313993a) - [KM-703] add analyze_merge tool: two-table combine (analytics.combine) (8abf635532366d670367557a3ffa03d42371d831) - [KM-567] planner support for analyze_merge: data_right guard + two-retrieve merge few-shot (a029a843247e6ea4d3c79a4e2c1b7571ba4cda69) - [KM-644] report v2: BQ answers, unresolved/excluded sections, evidence tables + curation/readiness endpoints (4ceb058d85c5a2a289443b9411d2b345027fa226) - [NOTICKET] refactor: mint message_id as UUID to mirror analyses_messages id shape (4253733b6b8db0449a82442a915c732ddd55f528) - [KM-644] report: drop Notes/Unresolved/Method sections from rendered markdown (compact report) (eef6de811a139402c79fd74ad4adfc00cf7aff01) - /edit md file (8198cc188ff05a2798ae2056b90b6e56e1bea87b) Co-authored-by…49b0848
-
fix/ check (#12)
- [NOTICKET] check: scope to analysis catalog + list database tables (db2a10f61e1f6ff9579deaaeafed8fdf0cdf5bb7) - feat(planner/help): graceful degradation for gated analytics capabilities (efc0af7c05308acb564bffdd7d8ab8abd2dd2e81) - Scope structured_flow + report to analysis catalog; drop dead data_sources binding (c333ec84a96b171484af7a87bdf07fd1fb0e9c69) - update md file (c5e2e1b1adcba46b56eaf6bbb85d9b8bb0a0d277) - [NOTICKET] check: read documents from analysis-scope catalog (6977394de88d7944dd2504beeed3e00eafe7857a) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>b9dfc76
-
/feat traceability (#11)
- [NOTICKET] Fix check skill: reply language + tabular inventory routing (1367f41269cf9ef42fd91f311b24d4edf5885c7b) - [KM-691] Develop traceability (23cc2079989fef931a6e146980fe6bf528ee6e92) - [NOTICKET] Humanize check output: hide UUIDs, add lead-in, list format (2bdda8fc3fc4b4e17b4df7fb53aee5abede45add) - [NOTICKET] check: schema-detail view for column/type questions (9e248d9cc5688d6ee622be523a6bedddf5010995) - [KM-691] Make sources trace-authoritative; drop stream sources (b43ecc77f26c1537cbbfddb6800ec4ff62d16441) - [KM-691] Bound traceability payload + reject contradictory IR filter ranges (db6db73d6ab0c2175447946742038443d67b2f78) - /fix planner can now plan quarter comparison (839e32c8d6d5895029072074ab7aba8bb4fcdb6e) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>f873f92
-
/fix validator and report (#10)
- /fix report: remove record_id hash citations, EDA (for future tool) change to data source, transform to mdx-safe (b1b101730ccf5628e43e80f2ad654f78fbed5207) - [NOTICKET] fix(planner): repair near-miss catalog ids in QueryIR before validation (aacd4d13def258a9815761aecbd7b246a8dae9fc) - /fix report: group findings by analysis, dedup, code-span-safe MDX escaping (029b48894e9f79af6c0d81c00a2d811a982f87ae) - [NOTICKET] fix(tools): log swallowed analytics tool errors in AnalyticsToolInvoker (93d9381b2a5f5efe058c913fe0b793ce994a9097) - fix(planner): harden plan validation to reduce retry thrash on structured questions (1619dd3c0fa74825010c7af6d4b375e3b9404847) - [NOTICKET] fix(tools): coerce numeric-string columns before analyze_* compute (6bda333866a1a8ccf1b3fe6fcee7a8e1832f28d7) - fix(planner): correct top-N guidance — in-query ranking IS supported (99aa4141aed8241a625d290fb170f74192a6d831) - feat(guardrails): add input guard, out_of_scope intent, and refusal handling (0bbc27bc40ba20e7a8e…0e5fdb5
-
/fix analysis + report_inputs and storage update (#9)
- fix(chat): drop ENABLE_SLOW_PATH flag + make chat persistence read-only (b8b76c4fb8db21de183cc6f80c0acba0d35bdad1) - [NOTICKET] feat(storage): read tabular Parquet from Supabase S3 via provider toggle (3f48226adaf2ed107a4eb2c0373cbb73fc62f552) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>079782d -
/fix check and help tool (#8)
- /fix data_catalog model + CatalogStore to dedorch schema (data → catalog_payload) (09857fc52486354f53e752e3ea329b064a9e4c4b) - [NOTICKET] fix(help): lock reply language to user's language on button path (cb7f5ac484ad4a510e68faf5291091958b6d2f42) - /fix default SKIP_INIT_DB=true for dedorch cutover (skip init_db on Go-owned schema) (781b93c6b8744209a1101629b5170175e9212592) - /fix surface catalog foreign keys to the planner (FK-backed joins) (446c57524e932fcdbb0ddecc049189c443b6ae97) - [NOTICKET] feat(eval): add help-skill eval harness + goal-based language fallback (cbdbefb7ab0ffa36949713f18422213db480a959) - [NOTICKET] fix(eval): update readiness eval to post-KM-652 floor (drop problem_validated) (6f46e81bdeb1eb987f9dac8af0e22a975474cbb1) - /fix infer FKs for FK-less dedorch catalog + log repr(e) in db executor (3669290474583ae011f5ed5e50b94dad146fbc77) - Merge eval/help + readiness eval fix into PR #8 (5f4818a8e38f93988ab5756f3a06c94645826b15) - /docs REPO_STATUS: FK inference (FK-…3743cfe
-
/fix v2 chat stream api update to analyses_messages (#7)
- [NOTICKET] fix(db): reconcile analyses schema + migrate chat to analyses_messages (283eb0e4653acfe9311f42e3bb12d0490b8c9751)0066161 -
/fix message_id for chat/stream Endpoint (#6)
- [NOTICKET] refactor(api): server-mint message_id only; unwire v1 chat (729086150b982cbd747829074658bc798d8e18f4)d8e7745 -
feat/ Endpoint Restructure (#5)
- [KM-686] Unwire Non-AI Routers from Main + Swagger (0b2d6785801ecc4d58a32580b1a9ef6238059de2) - [NOTICKET] docs: pr/5 sprint tracker + endpoint-restructure contract + REPO_STATUS banner (ce7be178428cadf1884a77d3d1f1398dccf32f6e) - [KM-687] Add Dedicated /tools/help Endpoint + Regroup Tools List (a881d38851470bf685990fdb554417da4fc1eccd) - [KM-688] feat(api): v2 chat pilot + regroup report under /tools; adopt lead API contracts (ad2ce619b51c234a8cd1c3772417a9a542a9a40d) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>3bacc1d
-
feat/Analysis State & Report Rework (#4)
- [NOTICKET] Add project repo documentation (ade9c0c635b1bb6f171a3f4e710e6d0f9bae28f3) - [KM-674] feat(report): adapt report generator to objective + business_questions (9bd8ec51fdcd5057b5e8ba6b219a7d9dce945144) - [NOTICKET] Add revision plan md file (e0384e1dc600b2496f96cbba152e616d65650f07) - chore(docs): tidy root markdown — archive stale docs, delete superseded ones (4835fb85915bd69079fb43d7c602774d514e02ae) - [KM-652] refactor: remove problem_statement skill + problem_validated gate (057e0b24b56dd697603d183f508cb1e8a87268fd) - [KM-678] feat(tools): trim FE slash menu to /help + /report (fed17ccc98ec523088c482673132763826f86701) - [NOTICKET] docs: sync DEV_PLAN status (#8/#9/#20) (e936cfafdfde1385fe16bd7e3796e7d46c193197) - [KM-679] fix(help): drop problem_statement refs after KM-652 (0bec4725db572d492634ced6a80ef6e65d075edc) - [KM-680] feat(report): show author display name (users.fullname) (9bccc122878fbdbae0ac1bd0b4316f5ea8af658c) - [NOTICKET] docs: add API_ENDPOINTS.md (FE surf…0e02a0f