build: rebuild dist with widget-conformance deploy guard

[sgardoll]

No description provided.

[greptile-apps]

Greptile Summary

The PR rebuilds the deployed frontend bundle so the existing widget-conformance validation is included in the distribution.

• Replaces the generated JavaScript asset with the rebuilt bundle.
• Updates the HTML module-script reference to the new content-hashed asset.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
dist/assets/index-U3hUe5L4.js	Rebuilt generated application bundle containing the widget-conformance deploy guard; no eligible follow-up defect was established.
dist/index.html	Updates the module entrypoint to reference the new generated asset hash.

_{Reviews (2): Last reviewed commit: "build: rebuild dist with widget-conforma..." | Re-trigger Greptile}

[sgardoll]

@greptileai please help resolve dependencies

[sgardoll]

@greptileai there are branch conflicts. please resolve

[greptile-apps]

I can see the conflict — mergeable_state: "dirty" confirms it. The PR only touches generated dist/ files (dist/index.html and dist/assets/index-*.js), meaning main has diverged with different built artifacts since this branch was created.

I can't execute git commands directly, but here's exactly how to resolve it:

# On your local machine, from the feat/widget-conformance-rules branch:
git fetch origin
git rebase origin/main

# Since both sides changed dist/ (generated files), take yours:
git checkout --ours dist/index.html
git checkout --ours dist/assets/

git add dist/
git rebase --continue

git push --force-with-lease origin feat/widget-conformance-rules

If the dist files were rebuilt from source on main (e.g. by another PR), you may need to rebuild instead of just taking yours:

git fetch origin
git rebase origin/main

# Rebuild dist from the merged source
npm run build   # or vite build / whatever your build script is

git add dist/
git rebase --continue

git push --force-with-lease origin feat/widget-conformance-rules

The second approach is safer — it ensures the dist reflects the latest source from both branches rather than blindly keeping one side.

Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.