chore: pin ASM to pi-timestamps follow-up merge

[ashwch]

Summary

Pin engineering-website to the merged ASM commit that contains the pi-timestamps follow-up fixes.

Why

agent-skills-source.ref is the website repo's default ASM lock file.

After ASM PR #84 merged, this repo was still pinned to the previous ASM SHA:

old pin -> 4ebdc684f962411bb72e965b94479d0657b558ac
new pin -> f1e935c952c6a5b12e49d98f4e48a6a0b1e36076

Updating the pin keeps default website builds aligned with the merged ASM source of truth.

Files Changed

• agent-skills-source.ref — updated to merged ASM commit f1e935c952c6a5b12e49d98f4e48a6a0b1e36076

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

• src/data/marketplace.json remains an ignored copied artifact and was not committed.
• This PR is intentionally tiny: it only updates the reviewed ASM lock file.

[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          -> full CI runs
intermediate commits     -> CI usually skips
checkpoint every 5 commits -> runs only after 30m cooldown
shared/risky paths       -> full CI runs
force-push / ready PR    -> full CI runs
draft/conflicted PR      -> CI is blocked

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.

_{Failing tests lead to fear. Fear leads to hotfixes.}

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.