docs: add Peru national data source proposals

[HiramPeru]

Adds documentation-only proposals for Peru-focused national data sources, RSS feed candidates, and a road transitability layer using MTC/SUTRAN sources. No code changes.

[vercel]

@HiramPeru is attempting to deploy a commit to the World Monitor Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

This PR adds three documentation-only proposal files for Peru-focused data sources: a national sources overview (peru-national-data-sources.md), a detailed road transitability layer design (peru-road-transitability-layer.md), and an RSS feed candidate list (peru-rss-feed-candidates.md). No code, configuration, or live data ingestion is introduced.

Confidence Score: 4/5

Safe to merge — documentation only, no code or config changes.

Only P2 findings present (stale next-step entries in the national sources doc). All three files are well-structured and internally consistent. Markdownlint CI enforces only MD012/MD022/MD032, all of which pass.

docs/proposals/peru-national-data-sources.md — Suggested Next Steps items 5 and 6 should be updated to reflect that the RSS doc is included in this PR.

Important Files Changed

Filename	Overview
docs/proposals/peru-national-data-sources.md	New proposal doc covering 9 Peruvian official data sources across transport, seismic, hydro, energy, and environmental domains; Suggested Next Steps items 5 and 6 are already addressed by this PR.
docs/proposals/peru-road-transitability-layer.md	Well-structured three-phase implementation proposal for MTC/SUTRAN road status layer; data model, severity mapping, and risk table are complete and internally consistent.
docs/proposals/peru-rss-feed-candidates.md	Catalogue of Peru RSS feed candidates with suggested source tiers, categories, and a validation workflow; the npm run test:feeds command referenced is advisory only (post-implementation).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Documentation PR<br/>peru-national-data-sources.md<br/>peru-road-transitability-layer.md<br/>peru-rss-feed-candidates.md] --> B[Phase 1: Source Discovery]
    B --> C{Stable public<br/>endpoint found?}
    C -- Yes --> D[Phase 2: Data Adapter Proposal<br/>Normalize status · Severity mapping<br/>Caching policy · Tests]
    C -- No --> E[Keep as proposal<br/>until endpoint confirmed]
    D --> F[Phase 3: Map Layer<br/>Toggleable layer · Markers/segments<br/>Popup · Severity filter]
    F --> G[Live data ingestion<br/>in World Monitor]

    subgraph Sources
        S1[MTC / Provias Nacional]
        S2[SUTRAN]
        S3[INDECI / COEN]
        S4[SENAMHI]
        S5[IGP / CENSIS]
        S6[COES]
        S7[BCRPData]
        S8[OEFA / MINAM / SINIA]
        S9[Peru RSS feeds]
    end

    Sources --> B

Loading

_{Reviews (1): Last reviewed commit: "docs: propose Peru road transitability l..." | Re-trigger Greptile}

[greptile-apps]

Stale next steps — RSS doc already added in this PR

Steps 5 and 6 in "Suggested Next Steps" are both completed by this same PR: step 5 ("Add a separate RSS candidate document for Peru news sources") is fulfilled by peru-rss-feed-candidates.md being added here, and step 6 ("Start with a documentation-only PR before introducing live data ingestion") describes what this PR itself is doing. Leaving these as open action items will mislead future readers into thinking they still need to be done.

Suggested change

	5. Add a separate RSS candidate document for Peru news sources.
	6. Start with a documentation-only PR before introducing live data ingestion.
	5. See `peru-rss-feed-candidates.md` for Peru RSS feed candidates (added in this PR).
	6. Next step: validate endpoint discovery per `peru-road-transitability-layer.md` Phase 1 checklist before introducing live data ingestion.

[HiramPeru]

Thanks. The Greptile feedback has been addressed in commit c8bbf6a.

The Vercel preview deployment requires authorization from a World Monitor team member because this PR comes from a fork.