[hellices]

Closes #513

Summary

Slice P2 of #410. The :consumers view now says whether a change to the selected ConfigMap or Secret, seen this session, followed each environment-variable or subPath consumer's container start. It follows the design's "P2: when a change is known to follow a start" section.

• Start times (core/config_consumers.py): Consumer.started_at holds only state.running.startedAt, read from the container's own status list (containerStatuses, initContainerStatuses or ephemeralContainerStatuses) and matched by name. A container that is waiting, terminated or has no status has no start. lastState and terminated.startedAt are never read, and no other status field reaches the result.
• Bounds and ordering (new core/config_changes.py, pure):
  • A change is bounded by the old sighting's send time and the new sighting's arrival, so a delayed old-version response can't push the bound past the change.
  • Resource versions are compared for equality only.
  • A change counts as after the start only when the whole bound is at least one minute after it (sent_old >= started_at + 1m), and as before only when it ends at least one minute before (arrived_new <= started_at - 1m). Anything else is "not established".
  • ChangeLog is keyed by context epoch, session generation, kind, namespace, name and observed UID. It holds at most 256 objects and ignores a sighting sent before the last one.
• Sightings (core/config_propagation.py): each run takes a send time before its reads and reports PropagationReport.sighting from the metadata GET's resourceVersion and the observation's arrival. The design didn't say which reads make sightings; the plan's "Where the sightings come from" section explains the choice. As a result, a change is seen only when the view was opened both before and after it.
• Controller: keeps the ChangeLog across runs and passes the latest change to the view.
• View:
  • An Object change column appears only when a change is known. It reads "changed after this container started", "changed before this container started" or "not established" on environment and subPath rows, and is empty on volume rows.
  • A note gives the change's bounds in UTC and says a new resource version may change only metadata.
  • Without a known change, a note says how a change is seen.
• Docs: docs/tui.md, the unreleased notes, and the plan docs/superpowers/plans/2026-10-31-config-change-order.md.

No version-matrix scenario is added: a matrix cluster's Pods are not guaranteed to be running, and P2 doesn't depend on the API version.

Verification

• Tests were written to fail first for each task. New tests:
  • tests/core/test_config_changes.py: straddling, a delayed old response, the skew boundaries, another scope or UID, out-of-order and same-moment sightings, eviction, input checks.
  • Start-time projection cases in tests/core/test_config_consumers.py: each status list, waiting/terminated/missing, a restart, a naive timestamp, the repr-leak check.
  • tests/core/test_config_propagation.py: the report's sighting.
  • tests/ui/test_config_propagation_controller.py: changes across runs, a denied run, a new UID, epoch or session.
  • tests/ui/test_config_propagation_screen.py: cells, notes, the column only with a change.
  • tests/ui/test_config_propagation_workflow.py: reopening end to end.
• Mutation-checked every new condition: the skew comparisons, the out-of-order guard, same-version replacement, eviction order, the status list per category, the timezone check, and the screen's cell, column and note. All are caught, except the UID guard in the controller, which exists only for mypy (an observed object always has a UID).
• Local gate, using the venv's tools behind the corporate mirror:
  • scripts/check_source_size.py, ruff check src tests, ruff format --check src tests, mypy src (272 files), tach check: all passed.
  • pytest -n 8: 14951 passed, 40 skipped, 2 failed.
    • test_device_login_prefixes::test_the_measured_release_is_the_installed_one is the known local-only failure: the local venv has litellm 1.100.3 and can't re-sync behind the mirror. CI has 1.100.4.
    • tests/performance/test_replay.py::test_replay_forbidden_aborts_with_an_explicit_terminal_error failed under -n 8 load; the file passes on its own (21 passed), and this branch doesn't touch k8s/ or the store.

Checklist

• This closes an accepted issue in this repository that is assigned to me.
• Tests cover the change, written to fail first where behavior changed.
• make check passes locally.
• User-facing docs and the README match the change, or nothing user-facing changed.
• No security invariant is weakened: writes still need a keystroke approval
  and a fail-closed audit entry, and sensitive reads are still masked.

[Copilot]

🟡 Changes recommended

A backwards system-clock adjustment can trigger an uncaught ValueError in explain_propagation, preventing the consumers view from opening despite successful reads.

1 open issue

• Discard backward clock sightings without failing propagation report · New

What changed in this PR

Adds session-observed change ordering to the :consumers view, extending ConfigMap and Secret propagation diagnostics with comparisons against each consumer’s current container start.

Changes:

• Projects running-container start times and tracks bounded, UID- and session-scoped resource-version changes.
• Shows before/after/unknown ordering for environment and subPath consumers, with a one-minute clock-skew allowance.
• Adds core and UI coverage and documents the limits of session-only, metadata-based evidence.

File	Description
tests/​ui/​test_config_propagation_workflow.py	Tests change ordering after reopening the view.
tests/​ui/​test_config_propagation_screen.py	Tests ordering cells, conditional columns, and explanatory notes.
tests/​ui/​test_config_propagation_controller.py	Tests sightings across runs and scope changes.
tests/​test_optional_extras.py	Checks the new module imports without optional extras.
tests/​core/​test_config_propagation.py	Tests sighting creation and unavailable resource versions.
tests/​core/​test_config_consumers.py	Tests start-time projection and status-field isolation.
tests/​core/​test_config_changes.py	Tests change bounds, ordering, isolation, and eviction.
src/​korvid/​ui/​widgets/​config_propagation_screen.py	Displays object-change ordering and evidence limits.
src/​korvid/​ui/​config_propagation_controller.py	Retains sightings and supplies changes to the view.
src/​korvid/​core/​config_propagation.py	Adds timed resource-version sightings to reports.
src/​korvid/​core/​config_consumers.py	Projects each running container’s current start time.
src/​korvid/​core/​config_changes.py	Implements bounded change tracking and skew-aware ordering.
docs/​tui.md	Explains the new column and its limitations.
docs/​superpowers/​plans/​2026-10-31-config-change-order.md	Records the implementation plan and verification approach.
docs/​release-notes/​unreleased.md	Announces session-observed change ordering.

_{Review effort: Balanced}

[my-reviewer-agent]

이슈 2건을 인라인 코멘트로 남겼습니다.

[Copilot]

🟢 Approved

No active review issues block approval of the session-observed ConfigMap and Secret change-ordering update.

No open issues 🎉

1 resolved since last review

• Discard backward clock sightings without failing propagation report

_{Review effort: Balanced}

[my-reviewer-agent]

이슈 4건을 인라인 코멘트로 남겼습니다.

[Copilot]

🟢 Approved

No active review issues are identified for the session-observed change-ordering update.

No open issues 🎉

_{Review effort: Balanced}

[my-reviewer-agent]

이슈 3건을 인라인 코멘트로 남겼습니다.

[my-reviewer-agent]

이슈 2건을 인라인 코멘트로 남겼습니다.

[my-reviewer-agent]

검토 범위에서 보고할 이슈가 없습니다.