starintel-labs/starintel-gpt-auto-dig
3
0
Fork 0
Code Issues 998 Pull requests 33 Projects Releases Packages Wiki Activity Actions 2

[GH-#2004] Sync Auto-Dig graph to latest Quasar #1013

Open
nsaspy wants to merge 3 commits from agent/sync-auto-dig-quasar-latest into main
pull from: agent/sync-auto-dig-quasar-latest
merge into: starintel-labs:main
Conversation 0 Commits 3 Files changed 2 +88 -5
nsaspy commented 2026-09-08 17:06:35 +00:00
Owner
Copy link

Mirrored from GitHub https://github.com/lost-rob0t/starintel-gpt-auto-dig/pull/2004 (GitHub is authoritative for this item).

What changed

  • advance Auto-Dig's pinned Quasar runtime from 839f484a858ca7e615eceae17031e6a4d1623fee to cde3687f01698a1b64cba688e5b30d64358c1699
  • advance the pinned Quasar UI from 30f880bea88a419a3e7c84db03e53e0ecb1c76d0 to 94042592c25bf75233ce8e5283d8817ea6b19c78
  • extend the Auto-Dig site UI validation workflow so Quasar pin/build changes actually trigger PR CI
  • verify the pinned Quasar runtime/frontend pair, run Quasar check/tests/build, and include the Auto-Dig Quasar regression suite
  • replace the legacy Python tail in this site-validation workflow with the repository's canonical Nim buildFast + bin/validate-for-merge --site gate
  • keep the deterministic pinned-build model; Auto-Dig still does not follow an unpinned branch at deploy time

Root cause

Auto-Dig's graph deployment was still building the older lockfile revisions. Canonical Quasar had moved four commits ahead and its frontend pin had moved 26 commits ahead, so the deployed Auto-Dig graph could not contain recently merged Quasar UI work.

A second gap made this easier to miss: quasar-fork.lock.json was included in the production Pages trigger but not in the pull-request site validation paths, so lock-only updates did not receive the graph build gate before merge.

The new Quasar head is the merge of lost-rob0t/quasar#22, whose frontend gitlink points exactly to 94042592c25bf75233ce8e5283d8817ea6b19c78.

User-visible changes restored

This pin range includes the recently merged Quasar UI changes such as:

  • refreshed mobile navigation matching the current desktop shell
  • first-class Actors navigation
  • Black & Gold / Kinpaku shell work
  • centered red DB OFFLINE status
  • provider brand icons
  • related current shell/icon updates already present in canonical Quasar UI

Validation

The pin relationship was verified against canonical Quasar: cde3687 changes the frontend submodule from f2307c8 to exactly 9404259.

The PR gate now builds and tests the exact pinned Quasar pair whenever the lock or Auto-Dig graph integration changes, then compiles and runs the canonical Nim merge/site gate.

Repository policy requires the full merge/site gate and all GitHub checks before merge, so this PR remains draft until those gates are green.

Mirrored from GitHub https://github.com/lost-rob0t/starintel-gpt-auto-dig/pull/2004 (GitHub is authoritative for this item). --- ## What changed - advance Auto-Dig's pinned Quasar runtime from `839f484a858ca7e615eceae17031e6a4d1623fee` to `cde3687f01698a1b64cba688e5b30d64358c1699` - advance the pinned Quasar UI from `30f880bea88a419a3e7c84db03e53e0ecb1c76d0` to `94042592c25bf75233ce8e5283d8817ea6b19c78` - extend the Auto-Dig site UI validation workflow so Quasar pin/build changes actually trigger PR CI - verify the pinned Quasar runtime/frontend pair, run Quasar check/tests/build, and include the Auto-Dig Quasar regression suite - replace the legacy Python tail in this site-validation workflow with the repository's canonical Nim `buildFast` + `bin/validate-for-merge --site` gate - keep the deterministic pinned-build model; Auto-Dig still does not follow an unpinned branch at deploy time ## Root cause Auto-Dig's graph deployment was still building the older lockfile revisions. Canonical Quasar had moved four commits ahead and its frontend pin had moved 26 commits ahead, so the deployed Auto-Dig graph could not contain recently merged Quasar UI work. A second gap made this easier to miss: `quasar-fork.lock.json` was included in the production Pages trigger but not in the pull-request site validation paths, so lock-only updates did not receive the graph build gate before merge. The new Quasar head is the merge of `lost-rob0t/quasar#22`, whose frontend gitlink points exactly to `94042592c25bf75233ce8e5283d8817ea6b19c78`. ## User-visible changes restored This pin range includes the recently merged Quasar UI changes such as: - refreshed mobile navigation matching the current desktop shell - first-class Actors navigation - Black & Gold / Kinpaku shell work - centered red DB OFFLINE status - provider brand icons - related current shell/icon updates already present in canonical Quasar UI ## Validation The pin relationship was verified against canonical Quasar: `cde3687` changes the `frontend` submodule from `f2307c8` to exactly `9404259`. The PR gate now builds and tests the exact pinned Quasar pair whenever the lock or Auto-Dig graph integration changes, then compiles and runs the canonical Nim merge/site gate. Repository policy requires the full merge/site gate and all GitHub checks before merge, so this PR remains draft until those gates are green.
Run Auto-Dig site gate through Nim
Some checks failed
Validate Auto-Dig site UI / validate-site-ui (push) Failing after 46s
Details
Validate Auto-Dig site UI / validate-site-ui (pull_request) Failing after 4s
Details
dd35fceb5f
Some checks failed
Validate Auto-Dig site UI / validate-site-ui (push) Failing after 46s
Details
Validate Auto-Dig site UI / validate-site-ui (pull_request) Failing after 4s
Details
This pull request has changes conflicting with the target branch.
  • .github/workflows/validate-site-ui.yml
  • quasar-fork.lock.json
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agent/sync-auto-dig-quasar-latest:agent/sync-auto-dig-quasar-latest
git switch agent/sync-auto-dig-quasar-latest

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff agent/sync-auto-dig-quasar-latest
git switch agent/sync-auto-dig-quasar-latest
git rebase main
git switch main
git merge --ff-only agent/sync-auto-dig-quasar-latest
git switch agent/sync-auto-dig-quasar-latest
git rebase main
git switch main
git merge --no-ff agent/sync-auto-dig-quasar-latest
git switch main
git merge --squash agent/sync-auto-dig-quasar-latest
git switch main
git merge --ff-only agent/sync-auto-dig-quasar-latest
git switch main
git merge agent/sync-auto-dig-quasar-latest
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
github-mirror
Mirrored from GitHub (authoritative host)

No labels
github-mirror
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starintel-labs/starintel-gpt-auto-dig!1013
No description provided.