routewatch

sneak/routewatch

Fork 0

Author	SHA1	Message	Date
sneak	ebb7bf4d71	Rewrite the README sentence by sentence (closes #157 ) check / check (push) Canceled after 0s Details The old text failed the issue's prose rules: a 60-word sentence on the content security policy, a markdown table of settings, comma-chained lists of batch sizes and error codes, undefined jargon and an edge case in the opening. The new text leads with what RouteWatch is, why it exists and how to run it, then the pages, the API and the blocklists, then the settings, memory and upaas, and last the design and the development workflow. Every statement was checked against the code on next. The PR body lists where the old text disagreed with the code. Model: fable-5-1	2026-10-27 21:03:44 +00:00
clawbot	6d4f3e3419	Say in README why RouteWatch exists (closes #204 ) check / check (push) Canceled after 0s Details The Rationale section now gives the owner's reason for the program: it is an internal API that our other services ask about IP addresses. It sees which AS routes each address and which announced prefix holds it from its own routing table. WHOIS details of each AS, kept in its database, add to that. What RIS Live does and does not give stays, shortened. Planned geojs lookups are left out, because the README describes only what is built. Model: opus-5-5	2026-10-27 21:34:08 +01:00
clawbot	47aed8761e	Give every JSON answer @meta, errors included (closes #201 ) check / check (push) Canceled after 0s Details A panic in a JSON route's handler answered 500 with an empty body, because the router's recoverer sits outside the middleware that adds `@meta`. `JSONValidationMiddleware` now wraps the handler in the same recoverer, and answers the panic with the JSON error body. `/status.json` and the health check answered chi's empty 405 to any method they do not take. They now answer with the same JSON 405 as the routes under `/api/v1` and `/ip`. The home page's IP lookup card showed only the answer's `data`. It now shows the whole answer, `@meta` included. A table test checks `@meta` on every JSON route, in its successes and its errors. Model: opus-5-5	2026-10-27 21:20:07 +01:00

Author

SHA1

Message

Date

sneak

ebb7bf4d71

Rewrite the README sentence by sentence (closes #157 )

check / check (push) Canceled after 0s

Details

The old text failed the issue's prose rules: a 60-word sentence on the
content security policy, a markdown table of settings, comma-chained
lists of batch sizes and error codes, undefined jargon and an edge case
in the opening. The new text leads with what RouteWatch is, why it
exists and how to run it, then the pages, the API and the blocklists,
then the settings, memory and upaas, and last the design and the
development workflow. Every statement was checked against the code on
next. The PR body lists where the old text disagreed with the code.

Model: fable-5-1

2026-10-27 21:03:44 +00:00

clawbot

6d4f3e3419

Say in README why RouteWatch exists (closes #204 )

check / check (push) Canceled after 0s

Details

The Rationale section now gives the owner's reason for the program: it
is an internal API that our other services ask about IP addresses. It
sees which AS routes each address and which announced prefix holds it
from its own routing table. WHOIS details of each AS, kept in its
database, add to that.

What RIS Live does and does not give stays, shortened. Planned geojs
lookups are left out, because the README describes only what is built.

Model: opus-5-5

2026-10-27 21:34:08 +01:00

clawbot

47aed8761e

Give every JSON answer @meta, errors included (closes #201 )

check / check (push) Canceled after 0s

Details

A panic in a JSON route's handler answered 500 with an empty body,
because the router's recoverer sits outside the middleware that adds
`@meta`. `JSONValidationMiddleware` now wraps the handler in the same
recoverer, and answers the panic with the JSON error body.

`/status.json` and the health check answered chi's empty 405 to any
method they do not take. They now answer with the same JSON 405 as the
routes under `/api/v1` and `/ip`.

The home page's IP lookup card showed only the answer's `data`. It now
shows the whole answer, `@meta` included.

A table test checks `@meta` on every JSON route, in its successes and
its errors.

Model: opus-5-5

2026-10-27 21:20:07 +01:00

2 changed files with 604 additions and 557 deletions

README.md

+600 -557

View File

File diff suppressed because it is too large Load Diff

									
										TODO.md
									
		+4
		
												View File
												
				@@ -35,6 +35,10 @@ tested.

				# Completed Steps

				- 2026-10-27: README "Rationale" says why RouteWatch exists: to answer our other

				  services' questions about IP addresses, from its own routing table and the

				  WHOIS details it keeps. It still says what RIS Live does not give (closes

				  #204)

				- 2026-10-27: every JSON answer carries `@meta`. A panic on a JSON route answers

				  500 with the JSON error body. `/status.json` and the health check answer 405

				  with the JSON error body to any method they do not take. The 500 and the 405

Compare commits