q#16 |
high |
9277.9h |
ayudarg |
blocked #278 Necesidades: no se seleccionan de a 1 (multi-select roto) |
rob |
elazar |
Coder says the multi-select code looks correct (Set+toggle). Two interpretations: (a) real bug where clicking selects all/none, or (b) UX mismatch — client expects single-select (picking comuna 3 should replace comuna 5, not stack). Which is the actual behavior the client saw? A screenshot/video helps. Same question applies to WI 279 (comunas). |
answer |
q#18 |
high |
9153h |
ayudarg |
blocked #289 Conversación se actualice cada 24hs |
rob |
elazar |
Title 'Conversación se actualice cada 24hs' is ambiguous. Two interpretations:
(A) DATA reset: events.message field gets cleared after 24h via cron (mirrors existing reset-comida pattern at app/src/app/api/cron/reset-comida/route.ts). Use case: forces fresh conversación on each visit older than 24h.
(B) UI refresh: client-side polling/revalidation that re-fetches the necesidad detail every 24h. Low value — user would have closed tab.
Which does the client mean? If (A), what's the target field exactly: events.message, or something else? Hard cut to NULL or to a default value? |
answer |
q#25 |
normal |
7898.3h |
pluto |
blocked #61 CR 42: 3 docentes reales sin asignación a comisión: gonzalo.oviedo, lorena.salomone, cirugia1 (@odontologia.uba.ar). Necesitan ser asignados a comi |
rob |
elazar |
Which comisión should each of the 3 unassigned teachers be assigned to? gonzalo.oviedo, lorena.salomone, cirugia1 (@odontologia.uba.ar). Need comisión name/id + role (adjunto/jtp) for each. |
answer |
q#29 |
high |
7074.6h |
agent-ops |
done #449 memory-lint §12/§9 vs global CLAUDE.md: per-agent identity + dates in memory/ — Elazar decision |
rob |
elazar |
memory-lint enforces evolutiva-memory-discipline.md across ALL ~/.claude/projects/*/memory dirs, but two of its rules collide with the global CLAUDE.md and produce hard-fails on memories that exist by direct instruction. Need Elazar to pick.
CONFLICT 1 - per-agent identity (§12): §12 bans per-agent identity (ARO membership, post-compact reattach, agent name) from memory/. But global CLAUDE.md ss-protocol explicitly says 'carry over agent name + AROs (write to memory file)'. session-identity.md exists by that instruction and hard-fails §12. Options: (A) §12 carves an exception for ONE fixed-name file (e.g. session-identity.md) allowed to hold agent name + AROs; (B) ss-protocol moves identity out of memory/ into a sibling dir memory-lint does not scan (e.g. .role/).
CONFLICT 2 - dates (§9): §9 bans YYYY-MM-DD dates as 'dynamic content'. But feedback/reference memories legitimately cite dates as historical provenance (when Elazar gave a rule, when a fact was verified) - not as 'as of' staleness stamps. feedback-channel-discipline.md and feedback-verify-before-relaying.md hard-fail on this. Options: (A) §9 allows dates in feedback/reference type memories when used as event provenance; (B) keep the ban - memories must cite events/WI ids instead of literal dates.
Recommend 1(A) + 2(A): both are one-line carve-outs to the discipline doc, vs. relocating files / stripping provenance. Pick per conflict. |
answer |
q#32 |
normal |
6851.2h |
agent-ops |
backlog #480 bwi git-sync dead since 2026-05-06: decide whey-only policy vs resume DB commits+pushes to GitHub; venus agents routing through whey meanwhile |
rob |
elazar |
bwi git-sync policy: whey-only (venus agents route through whey-based basquetWi-cc) OR resume committing+pushing canonical DB to GitHub so all hosts can git pull? venus host had stale DB since 2026-05-06; pm-venus-cc confirmed via git pull that GitHub remote is also stale at that date. |
answer |
q#35 |
normal |
6165.5h |
pluto |
blocked #490 Plan: paciente DNI + HC central store — autocomplete, dedup warning, estadísticas |
rob |
elazar |
DNI obligatorio o opcional? (algunos pacientes podrían ser anónimos o extranjeros sin DNI argentino) |
answer |
q#36 |
normal |
6165.5h |
pluto |
blocked #490 Plan: paciente DNI + HC central store — autocomplete, dedup warning, estadísticas |
rob |
elazar |
Key de dedup: ¿numeroHistoriaClinica es único por paciente, o DNI es el key canónico? ¿O ambos opcionales con warning si difieren? |
answer |
q#37 |
normal |
6165.5h |
pluto |
blocked #490 Plan: paciente DNI + HC central store — autocomplete, dedup warning, estadísticas |
rob |
elazar |
Migración: ¿backfill practicas existentes creando una fila pacientes por HC existente, o solo aplica a prácticas nuevas? |
answer |
q#42 |
normal |
4285.8h |
pluto |
blocked #602 Prácticas rectificar + bidirectional comment/email-notification workflow (port/adapt from Mars) |
rob |
elazar |
Pluto prácticas rectificar workflow (gap-3) - D2: gate student comment-WRITE to the rectificar state ONLY (mirror Mars) vs keep Pluto's CURRENT looser behavior where students can comment any time? This is a TIGHTENING of existing Pluto student UX. RECOMMENDATION: mirror Mars (rectificar-only) for fleet consistency, since the ask was to bring Mars's workflow to Pluto - but it removes a capability students have today, so your call. Reply A=rectificar-only / B=keep current looser. |
answer |
q#43 |
normal |
4285.8h |
pluto |
blocked #602 Prácticas rectificar + bidirectional comment/email-notification workflow (port/adapt from Mars) |
rob |
elazar |
Pluto prácticas rectificar workflow (gap-3) - D3: scope of the student edit->resubmit form (Pluto has NONE today; only numeroHistoriaClinica is editable, ungated). Options: (i) minimal = numeroHistoriaClinica + comentario only; (ii) full core-práctica re-edit. Both gated to noRevisado/rectificar, LOCKED once aprobado/desaprobado. RECOMMENDATION: (ii) full core re-edit - 'rectificar' means fix-and-resubmit, and minimal may be too narrow if a teacher rectifies for a data error. Reply i / ii. (This defines the gap-3 build size.) |
answer |
q#44 |
high |
3810.7h |
evolutiva |
blocked #601 Fleet-wide Gmail dot/plus normalization: block duplicate accounts at the DATA LAYER (Mars+Pluto+Venus) |
rob |
elazar |
bin-whey-cc gates outward GitHub pushes on a DIRECT Elazar word (not a PM relay). The commons §Email Identity codification commit (shared/md/evolutiva-commons.md, the regression-guard for the fleet gmail-dedup — all 3 apps ALREADY enforce dedup at the DB, this just writes the rule so a future app can't reintroduce the bug) needs your explicit push-approval delivered to bin DIRECTLY: your CLI word, or a from=elazar DM to bin-whey-cc. Approve the commons --minor push? |
answer |
q#45 |
normal |
3269.7h |
agent-ops |
canceled OPS-5 one-db: kpi.pensanta.com web UI on whey — small read-only server (chat-duo-web model, single-file .mjs) that reads the SELECT* views and renders KPI pages, so Elazar has one habit-friendly place to glance at all KPIs and drill into any metric when something looks off. |
wi-cli-whey |
elazar |
kpi.pensanta.com exposure: public subdomain (DNS + nginx/caddy TLS, like a normal pensanta site) or Tailscale-only/localhost? chat-duo-web's model — confirm which. Drives security posture (read-only telemetry, but still your KPI data). |
answer |
q#46 |
high |
3269.7h |
agent-ops |
canceled OPS-2 one-db: consolidate all whey telemetry/KPI sqlite into one local Postgres 17 db (telemetry), schema-per-domain, SELECT*-friendly views, reporting web UI. Goal: one place for all KPIs/perf/context data + Elazar can actually find/read them. |
wi-cli-whey |
elazar |
one-db source dir ~/Documents/terminal/one-db (schema.sql/00-role.sh/backfill.sh — not PATH scripts): make it its own git repo, or leave untracked working files? (still-open Q from before compact) |
answer |
q#50 |
high |
3110.2h |
one-db |
blocked ONEDB-10 GATE#1 step iii: flip venus-kpi-collect.sh to pg-write (telemetry_rw via metrics_write) — kills kpi.sqlite split-brain co-writer; nw lane (cross-host) |
wi-cli-whey |
elazar |
ONEDB-10 venus-kpi pg-flip is a fork decision, not a mechanical edit. venus-kpi-collect.sh is a stale BUGGY fork of kpi-enforce.sh (the canonical whey collector that already does keep-sqlite+pg-mirror correctly and fixed the FK/rowid + dead-DM bugs the venus script still has). Pick: (A) port just the mirror pattern into venus-kpi-collect.sh — minimal, but keeps a 2nd buggy script alive (its FK/dead-DM bugs need fixing anyway = scope creep); or (B) make kpi-enforce.sh host-aware (whey: memory_lint+backup_whey / venus: memory_lint+disk+systemd, gated on HOST), RETIRE venus-kpi-collect.sh, venus runs the canonical script. One collector, buggy fork dies, pg-mirror free. Touches whey's live collector. I recommend B. host col namespaces rows so no double-count either way. |
answer |
q#51 |
low |
2562.9h |
mars |
done #1 Drop comisionCode from vTeacherComisiones |
wi-cli-whey |
elazar |
Confirm: flip the ONEDB telemetry consolidation target from whey-pg to venus-pg before GATE#1 ingestion is built? (Free now; a data migration after.) |
answer |