Skip to content

P1: remediate beta.5 aggregate review findings #318

Description

@gnanirahulnutakki

Problem

The aggregate dev to main release PR #317 completed after merge and reported seven review findings. One is a real Argo CD history-completeness defect; the others are documentation, portability, or stylesheet drift. Beta tagging must remain blocked until every valid finding is fixed, reviewed, and promoted back to main.

Scope

  • Preserve HistoryTruncated on the first emitted retained Argo history fact when earlier retained entries have no deployedAt, with a regression test.
  • Align F10.1 documentation with the unlabeled aggregate fleet-read outcome metrics.
  • Mark gitops.open-pr execution as planned P2 rather than shipped runtime behavior.
  • Resolve the reported console stylesheet normalization/deprecation findings without changing rendering or accessibility behavior.
  • Synchronize completed historical session statuses, sanitize the specifically reported developer-local verification paths, and clarify the internal API-contract scope statement.
  • Resolve all seven release: promote demo-ready dev for v0.3.0-beta.5 #317 review threads only after exact fix evidence exists.

Out of scope

  • New connector runtime wiring, GitOps execution, R2/R4 automation, authentication, authorization, persistence, cluster mutation, release tagging, or GHCR visibility changes.

Acceptance criteria

  • Focused Argo projection tests include the skipped-oldest-entry truncation regression and pass under the race detector.
  • All seven findings are independently validated and either fixed or closed with a concrete reason.
  • Full repository CI/release policy gates pass.
  • One signed DCO/GSTACK commit lands in dev; exact post-merge CI, CodeQL, and security queues are green.
  • The fix is promoted to main and exact main checks pass before v0.3.0-beta.5 is tagged.

Review source

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationphase-1Phase 1: read-only federation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions