Repository navigation
Conversation
alcxyz
changed the title
Adopt the shared workflow update that validates CHANGELOG.md on every push and renders the current version's section as the GitHub release notes, and backfill the changelog for every published version.
Keep squash merges for feature PRs, but merge promotions to main with a merge commit so the branches share history and releases need no squash reconciliation.
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.
What: Adds the standalone DankT3Code DMS companion repository and the first read-only T3 activity collector, a standard-library Go helper that currently supports T3 0.0.40.
Why: Not stated directly; this is the draft PR for the v0.1.0 promotion, and ADRs record the separate product scope, GitHub-first release workflow and HTTP collector choice.
Risk: Compatibility evidence documents the available read scope's broader file authority and remaining frontend/navigation limits. The QML widget still shows a development placeholder. Keep
plugin.jsonat 0.0.0 until the pre-promotion gates in #7 pass, and do not delete the long-liveddevbranch.After merge: Verify the release and close #7. #1 and #2 (both open) remain open for their outstanding acceptance criteria; distribution follows in #8.
Details
DankT3Code adds a standalone DMS companion repository and the first read-only T3 activity collector. The Go helper accepts an explicit loopback origin and owner-only bearer file, checks the server version, and returns a minimized HTTP shell observation. Failed or malformed collection returns a defined error rather than a fresh empty activity list.
The runtime uses only Go's standard library and currently supports T3 0.0.40. It drops raw errors, workspace paths, scripts, and conversation data. ADRs record the separate product scope, GitHub-first release workflow, and the HTTP collector choice. Compatibility evidence documents both the available read scope's broader file authority and remaining frontend/navigation limits.
Validation: Go tests with race detection, go vet, build, canonical CI drift check, and an isolated published t3@0.0.40 smoke run. The smoke run covers pairing-scope narrowing, denied writes, HTTP/WS snapshots, restart continuity, and revocation, including the Go binary's success/failure behavior. Fixtures are synthetic; no live installation was accessed.
This PR remains draft for the v0.1.0 promotion. The QML widget still displays a development placeholder, and pairing, polling/backoff, activity presentation, navigation, notifications, and release packaging remain milestone work. Keep plugin.json at 0.0.0 until the pre-promotion gates in #7 pass; verify the release and close #7 afterward. Do not delete the long-lived dev branch.
Progress: #1 and #2 remain open for their outstanding acceptance criteria. Distribution follows in #8. Milestone.