feat: release v1.4.0 with cycle journal dashboard - #34
Merged
Merged
Conversation
MaxMiksa
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Dashboard now opens as a cycle-centered work journal. The current or latest cycle is prominent, historical cycles expand on demand, and next steps, output documents and runtime information have a separate side column. The implementation retains the production controls, shared language preference, usage, budget information and diagnostics.
Updates the framework version to 1.4.0. Release notes also cover the CI improvements already merged since v1.3.2.
Cycle reports and logs keep their own record identity. Live cycle numbers require matching runtime evidence, missing usage remains unknown, and daily/weekly totals use completion dates. The journal adds bounded, same-origin document and log access without new dependencies. An optional read-only archive server can use an explicitly supplied external legacy backup.
Validation: hosted CI passes all 8 selected jobs, including the required gate. The standard Python suite executes 246 tests and skips 8 live-service cases covered by separate systemd (9 tests) and macOS launchd (3 tests) suites. All 17 Chromium tests pass together, as do 7 Node checks, both PowerShell editions and 197 skill-resource references. The 3 unchanged product-example jobs are explicitly skipped. Isolated macOS fixtures now copy the new journal dependency; no real autonomous run was started.
Local legacy backups and internal release documents are excluded from the public change. Release preparation preserves the accepted README contents; the browser-test README change belongs to the feature's test documentation.