Skip to content

feat: expose lensing catch-up freshness in cockpit - #110

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/memory-cockpit-catch-up
Oct 1, 2026
Merged

Jammy2211 merged 1 commit into
mainfrom
feature/memory-cockpit-catch-up

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Summary

The catch-up banner used activity from all research topics to recommend a lensing action, and the cockpit did not expose the banner's condition as an actionable row. Derive the banner and cockpit row from one lensing-specific freshness model using the existing seven-day policy and /catch_up lensing procedure.

The model distinguishes actual bib-plus-sources ingestion from queue completion (which can mean read-without-filing). It includes cutoff, age, deadline, observation time and provenance. Healthy activity adds no attention row; missing, invalid, inconsistent and future evidence stays unknown. Actions remain manual, with scientific-judgement metadata and a runbook link.

Closes #109. Builds on PyAutoBrain#434 / PR #435; no Brain or website edits.

API Changes

  • Additive lensing_ingest_evidence in board collection and lensing_catch_up in state.json.
  • Shared v1 optional item metadata identifies stale/unknown lensing catch-up and its recommended action.
  • Preserve existing all-scope last_ingested and days_since_ingest; new fields explicitly distinguish last_ingestion, last_completed and last_activity.
  • No paper selection, ingestion, automated remediation, scientific-library API or scheduling changes.

Test Plan

  • Full Memory test suite: 254 passed.
  • make validate: citation metadata, repository structure and wikilinks passed.
  • Live/stale/unknown outputs pass Brain's shared feed validator.
  • Browser: 390px/1280px light/dark Memory banner; existing cockpit renders stale/unknown rows, one catch-up button, scientific-judgement label, runbook link and working clipboard; no JS errors.
  • In-session diff/visual review. No independent review claimed. Physical devices untested.

Heart gate

Live user authorization: “I authorize”, in direct response to “Ship Memory #109 despite Heart RED”. Commit, push and opening the pending-release PR only; no merge or release authorization.

Heart RED: release validation FAILED (stage integrate) (snapshot 2026-10-01T10:10:03.098482+00:00).
Other reasons: workspace validation not passing (0 failed, 1 timeout, cloud#36404726969: autolens_test scripts/multi_dataset/rectangular.py); manifest drift: public front-door organ tables (generated) — 1 mismatch(es) vs PyAutoMind/repos.yaml.

Passed gates: 254 Memory tests, make validate, shared feed validator for live/stale/unknown data, Chromium mobile/desktop light/dark, cockpit action/clipboard/runbook checks and in-session diff/visual review. No independent review claimed. Tested diff unchanged before shipping.

@Jammy2211 Jammy2211 added the pending-release Awaiting coordinated release label Oct 1, 2026
@Jammy2211
Jammy2211 merged commit dc9c3b5 into main Oct 1, 2026
1 check passed
@Jammy2211
Jammy2211 deleted the feature/memory-cockpit-catch-up branch October 1, 2026 10:26
@Jammy2211 Jammy2211 removed the pending-release Awaiting coordinated release label Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: expose lensing catch-up freshness in the cockpit

1 participant