Unify platform releases and stage the complete DSP experience - #1
Merged
Conversation
* Add guarded GitHub release publication and repository workflow * Verify release component versions and document dependency bootstrap * Validate workflow syntax and exercise publication failure recovery * Allow repositories to bound test runner concurrency --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Bootstrap DSP CI from pinned Core packages and guard release publication * Prepare trusted tools for DSP browser and collector checks * Seal hosted Chrome ownership and pin the reviewed Core dependency * Add a blank-window smoke check for hosted browser diagnostics * Synchronize browser fixtures and serialize DSP test files --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Pin Core 0.0.1 platform bundle for DSP releases * Wait for rendered pages in native browser fixtures --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Add verified independent release discovery and staging * Wire independent owner updates to durable Core and DSP lifecycles --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Fix Paycom credential saves under DSP capacity contention * Bound authentication handoff to the idle capacity needed --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Copy optional plugin code only when a DSP installs it * Verify Cortex-only startup and installed Paycom upgrades in native DSPs * Hide Dev-only plugins from production session bootstrap --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Start Paycom verification immediately after saving credentials * Cover pending verification and verified Paycom workspace states * Keep Core-only browser previews independent of DSP fixtures --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
* Show centered development notice on DSP home page * Include built dashboard development notice assets --------- Co-authored-by: Dillon <260170482+dillonlille@users.noreply.github.com>
dillonlille
marked this pull request as ready for review
September 13, 2026 06:47
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.
Consolidates Dispatch into one public repository while preserving both source histories. One platform release has Core, DSP and Plugins changelogs and independently installable Core/DSP packages. Plugin-only changes are DSP updates; unchanged components retain their previous package identity.
The Platform Owner dashboard ships with Core. DSP dashboard assets are stored centrally per release and selected through authenticated DSP authority, including owner DSP views. Update Dev and sequential Rollout Update govern the dashboard, runtime, catalog and installed plugins together. Verified snapshots preserve the old dashboard during migration; stale dashboard writes are rejected.
Includes portable builds, guarded GitHub publication/provenance verification, one Updates page, plugin preview support, migration preparation and workflow documentation. Private data stays outside Git. Publishing does not activate Core or roll out DSPs.
Validation: separate Core/DSP dashboard and package builds; 143 Core unit tests; 323 DSP unit tests; 140 integration tests; six monorepo/release tests; four browser acceptance tests including owner DSP views and stale-write protection; desktop/mobile visual review; publication packaging rehearsal. Required PR and resulting main checks passed.