Change record
Changelog
Material changes to Asmaliana's public capabilities, schemas, data revisions, and limitations.
2026-09-29 — Route evidence guide
- Added a method guide explaining dated FOSSGIS/OSRM route evidence, conservative upper bounds, buffers, expiry, and why missing coverage remains
needs_verificationinstead of a guessed travel time.
2026-09-29 — Accessible navigation context
- Primary navigation now exposes
aria-current="page"for the active home, places, planner, itinerary, or developer route, including nested place pages. - The behavior is covered by the browser representation suite and does not require client-side JavaScript.
2026-09-29 — Runtime routing health state
/api/v1/statusnow exposesproviders.routing.stateasok,stale,unavailable,disabled, ordemo.- The human status page marks an expired snapshot stale and explicitly says no route duration is used; this is separate from
effective=production, which identifies the selected adapter.
2026-09-29 — Verified coverage expansion
- Added 25 explicitly reviewed Melaka landmark identities and Wikidata coordinates, expanding the verified release to 52 places, 135 assertions, and 57 sources. New operational fields remain explicit unknowns until separately evidenced.
- Rebuilt the reviewed FOSSGIS/OSRM snapshot with 2,652 directed edges, valid through 2026-10-01T21:33:35Z.
2026-09-29 — Production seed safety and documentation parity
- Verified D1 seeding now preflights the remote revision, makes complete active releases idempotent, limits activation-only recovery, and verifies exact 52/135/57 counts before success.
- Deployment, security, and current-state documentation now identify verified-v130 and the latest production Worker instead of the superseded v80 snapshot.
2026-09-29 — Routing snapshot refresh
- Rebuilt the reviewed 27-place FOSSGIS/OSRM driving snapshot (702 directed edges) before its safety window tightened. Normalized route values were unchanged; only retrieval metadata, source hash, and the 72-hour validity deadline moved to 2026-10-01T19:26:20Z.
- Review found no errors and retained 52 explicit unknown opening-hours findings; no schedule was inferred from the refresh.
2026-09-29 — Routing release safety margin
- Production release and post-deploy smoke gates now require at least 24 hours of remaining validity on the reviewed routing snapshot, preventing a rollout from publishing a matrix that will expire during the release window.
- When the margin is not met, operators must refresh the 27-place snapshot with
pnpm data:fetch:routesand repeat review before deployment; route expiry remains visible in the machine and human status surfaces.
2026-09-29 — v131 routing snapshot pre-expiry refresh
- Re-fetched the reviewed 52-place FOSSGIS/OSRM matrix before the prior 72-hour validity deadline. All 2,652 normalized route values and coordinates remained unchanged; the v131 snapshot is now valid through 2026-10-01T22:49:12.100Z with source hash
sha256:7d38316d500b951ac34703a784660f4bdbba126bdf995cbeebd460aa98670efe.
2026-09-29 — Boundary FAQ
- Added English and Chinese FAQ pages that explain verified coverage, unknown and stale evidence, planner limits, provider scope, read-only actions, API representations, and demo/production data modes.
- Added the FAQ to the footer, machine discovery sitemap, and developer docs so users can inspect operational boundaries from one stable page.
2026-09-29 — Evidence summaries and freshness reporting
- Place pages now show each field's known, stale, unknown, conflicting, or restricted status and evidence count before the full audit JSON.
data:validatenow reports the shared effective freshness summary, including overdue counts and the next scheduled evidence recheck, for the published revision; the current verified-v131 release reports 137 fresh assertions and zero overdue rechecks.- Production remains read-only; actions, booking, payment, inquiries, ARD, and A2A are disabled.
2026-09-29 — Automated production smoke gate
deploy:productionnow runs a bounded read-only HTTPS probe after Wrangler succeeds, checking verified metadata/status parity, the next recheck clock, OpenAPI, one public fact projection, and MCP initialization before the command can report a healthy release.
2026-09-29 — Verified-v80 discovery freshness
- Metadata and public status now expose the immutable dataset revision, creation time, publication time, covered-place count, assertion/source counts, effective fresh/stale/unknown/overdue totals, and the next scheduled evidence recheck so agents can make freshness decisions without guessing from a response timestamp.
- OpenAPI now describes the metadata and status result schemas, including the revision clocks and freshness summary.
- Wikidata ingestion now preserves review timestamps and deadlines when a repeat fetch has no content change; a real double-fetch confirmed 27 unchanged candidates and zero changes.
2026-09-28 — Verified-v80 production
- Published 27 reviewed Melaka place identities and coordinates from Wikidata structured data.
- Added 13 PERZIM official ticket matrices and Tuesday–Sunday museum hours with 16:30 last admission where the official table applies.
- Enabled live area-level weather from MET Malaysia’s CC BY 4.0 Government Open API for Melaka Tengah (Ds078), with attribution, five-minute cache, rate limiting, schema validation, and explicit failure states.
- Enabled a 27-place FOSSGIS/OSRM driving snapshot with ODbL attribution, a 72-hour validity window, conservative upper bounds, and explicit no-traffic/no-navigation warnings. Accessibility and certificates remain unknown.
- Kept provenance, review, freshness, rights, and unknown states visible across HTML, Markdown, JSON, REST, and MCP.
- Actions, booking, payment, inquiries, ARD, and A2A remain disabled.
2026-09-28 — Verified-v80 certificate refresh
- Added the exact MOTAC MyTQA item 89 recognition for Muzium Sejarah & Etnografi in Melaka with source attribution and weekly recheck.
- Kept venue accessibility unknown because no reviewed facility tags or venue certification evidence supports those claims.
- Refreshed the 27-place FOSSGIS/OSRM driving snapshot with its 72-hour validity window.