chore: pin ASM to pi-timestamps status-bar redesign

[ashwch]

Summary

Pin engineering-website to the ASM commit that contains the pi-timestamps status-bar redesign.

Why

The pi-timestamps package docs and metadata are source-owned in agent-skills-marketplace and rendered here at build time.
This website repo should therefore follow the same pattern we used last time:

ASM change merges or is prepared for review
    ↓
engineering-website updates `agent-skills-source.ref`
    ↓
default website builds render the reviewed ASM source of truth

This update ensures the site picks up the new pi-timestamps package docs, including the explanation that the newest live relative age moved to the status bar to avoid historical transcript rerendering problems.

Files Changed

• agent-skills-source.ref — updated to c1612db610d1a93ce0150e5396550d20c36bb352

How to Test

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

Validation

• npm install --package-lock=false ✅
• AGENT_SKILLS_REPO_DIR=../agent-skills-marketplace npm run build ✅
• git diff --check ✅

Notes

• src/data/marketplace.json remains an untracked copied artifact and was not committed.
• This PR is intentionally tiny: it only updates the ASM lock file so the reviewed source docs render on the website.

[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.

_{When red the pipeline is, patient you must 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.