fix: repin ASM to merged pi-timestamps commit

[ashwch]

Summary

Repin engineering-website to the merged ASM commit for the pi-timestamps redesign.

Why

Main is currently pinned to an ASM PR-branch commit (05e1217...) that is not fetchable from the remote after merge, so GitHub Actions cannot check out the pinned SHA.

The merged ASM change now lives at:

114806ed9777cb9dfb74259a21d6bead02178b28

This PR updates agent-skills-source.ref to that merged main commit so website CI can fetch ASM again.

Files Changed

• agent-skills-source.ref — repinned from PR-branch SHA to merged ASM main SHA

Validation

cp ../agent-skills-marketplace/website/src/data/marketplace.json src/data/marketplace.json
AGENT_SKILLS_REPO_DIR=../agent-skills-marketplace npm run build

Build completed successfully.

Notes

• This is a follow-up fix to PR chore: pin ASM to pi-timestamps status-bar redesign #7.
• The failure on main was caused by pinning to a branch commit instead of the merged ASM commit.

[little-person]

Naboo CI commands

Naboo can answer read-only CI questions directly in this PR. Comment with one of these commands on its own line:

Command	What it does
/ci help	Show the command reference
/ci status	Show current check-run statuses for this PR
/ci explain	Show check statuses + CI routing/policy notes
/ci run (full / optimo / diversio / minimal)	Trigger Django4Lyfe backend CI manually (write/maintain/admin/allowlist only)
/ci retry	Rerun the latest Django4Lyfe backend CI pipeline for this PR SHA (write/maintain/admin/allowlist only)
/ci cancel	Cancel the in-flight Django4Lyfe backend CI pipeline for this PR SHA (write/maintain/admin/allowlist only)

Read-only commands work everywhere Naboo is installed.
Manual backend commands are limited to Django4Lyfe and require write/maintain/admin/allowlist access,
direct CircleCI-control enablement, and repo permission.

Backend auto-trigger policy:

first PR commit          -> CI runs (mode depends on files)
intermediate commits     -> CI usually skips
checkpoint every 5 commits -> runs only after 30m cooldown
shared/risky paths       -> full CI runs
force-push / ready PR    -> CI runs (mode depends on files)
draft/conflicted PR      -> CI is blocked

The trigger mode (optimo, diversio, full, or minimal) is chosen
automatically based on which product directories changed.
Run /ci explain to see the routing decision for this PR.

Need CI right now? A user with write, maintain, admin, or explicit allowlist access can comment /ci run full. Naboo still dedupes by branch + SHA so repeated commands do not create duplicate pipelines.

_{A flaky test, a Sith trick it may be.}

This one-time message is posted automatically when the PR opens.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.