# Sahil Tayal Complete Archive · Human-readable release notes

## Edition 3.1 — 25 October 2026

- **Preserved the live homepage.** This deployment remains a separate archive Pages project. It does not replace `sahiltayal.online` or any subdomain.
- **Made the three entrances legible.** Explained why `sahiltayal.com` is the primary portfolio, `sahiltayal.online` is the Other Orbit gateway, and `sahilverse.online` is a distinct editorial path.
- **Clarified the number disagreement.** `.com` advertises 171 *pathways*. The independently prepared archive contains 145 deduplicated URLs. The referenced 44-item inventory cannot yet be reconciled because its records and counting rule are not included.
- **Changed ambiguous status language.** Every entry is explicitly either observed in public retrieval or catalogued without availability verification. “Broken,” “Needs review,” and “In progress” have reserved meanings rather than being guessed from DNS.
- **Created a DNS issue register.** The known `services.sahiltayal.online` placeholder origin (`192.0.2.1`) remains out of the public index. Four additional reported faulty hosts need their actual names before remediation can be claimed. `www` merits a canonical-routing review.
- **Created an operations view.** It shows recorded HTTP history only when checks exist. No fabricated uptime percentage, fake trend or invented upcoming check time.
- **Added a script for optional HTTP checks** and explicit release, technology, feedback and QA metadata.
- **Kept original visitor value.** Search, categories, random selection, CSV export, and the substantive branded PDF remain available.

## Earlier archive edition — 25 October 2026

- Introduced a standalone 145-address catalogue, the field guide, safe embedding instructions and Cloudflare Pages configuration.

## Outstanding work

1. Identify the remaining four DNS errors from the source checklist and determine if each should be deployed, redirected or excluded.
2. Confirm whether `www.sahiltayal.online` should redirect to the apex and test HTTPS on both, before changing DNS.
3. Run repeated external HTTP checks before classifying pages as broken or claiming uptime rates.
4. Physically test five representative *external* websites on phones in addition to testing this archive at emulated mobile widths.
5. Supply the source 44-entry list if an exact one-to-one index reconciliation is needed.
6. Publish the archive via its own Pages project, then add the optional homepage link in the **current** homepage source.