WIP: Reuse the dashboard line buffer #6

Closed
erikinkinen wants to merge 3 commits from feature/monitor-render-buffer into feature/ci-source-acquisition
Owner

Reuse the dashboard line buffer. Keep the associated implementation, fixtures and component contract together so the change can be reviewed independently of later behavior.

Depends on the preceding feature branch feature/ci-source-acquisition; this PR contains only the next feature in the stack.

  • Preserve the original source changes and squash dependency-pin churn.
  • Complete the feature acceptance checks and required regression coverage.
Reuse the dashboard line buffer. Keep the associated implementation, fixtures and component contract together so the change can be reviewed independently of later behavior. Depends on the preceding feature branch `feature/ci-source-acquisition`; this PR contains only the next feature in the stack. - [x] Preserve the original source changes and squash dependency-pin churn. - [ ] Complete the feature acceptance checks and required regression coverage.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:46:51 +01:00
feat: Reuse the dashboard line buffer
Some checks failed
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 5s
CI / rust (push) Failing after 1m2s
4eedb2680d
Reuse the dashboard line buffer. Keep the associated implementation, fixtures and component contract together so the change can be reviewed independently of later behavior.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 8s
CI / rust (push) Failing after 36s
27baadf398
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Declare policy helper and output boundaries
Some checks failed
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / rust (push) Failing after 1m44s
6161ef8b2c
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Author
Owner

Superseded by #9. The implementation, component documentation and tests are identical; the replacement removes an unused Cargo dependency and uses the working explicit CI provider selection. Closing this duplicate while retaining its branch.

Superseded by #9. The implementation, component documentation and tests are identical; the replacement removes an unused Cargo dependency and uses the working explicit CI provider selection. Closing this duplicate while retaining its branch.
erikinkinen closed this pull request 2026-11-13 02:34:26 +01:00
Some checks failed
CI / rust (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / rust (push) Failing after 1m44s

Pull request closed

Sign in to join this conversation.
No description provided.