smallwebwaf

72 Commits 8 Branches 2 Tags

3 Commits

Author	SHA1	Message	Date
sneak	e44ba7ee5e	SPEC rework after review: each requirement once, gitea notes to docs/ check / check (push) Canceled after 0s Details Every requirement is stated once, where it belongs, and linked from elsewhere. The notes on gitea move to docs/gitea.md, which script/gitea-requests points at. The list of settings that take off is exact, the non-goal that contradicted the planned item is gone, and the sentences the review named are split or reordered. The package comments in internal/waf and internal/anomaly point at the renamed sections. Model: fable-5-1	2026-10-22 19:43:03 +00:00
sneak	7fb8662e69	SPEC rewritten from scratch, short and plain, built and planned apart (closes #156 ) check / check (push) Canceled after 0s Details The old SPEC opened with a draft status and milestone narrative, said several requirements twice, and ended with a build order that is all built. The new one keeps every requirement the old one states, said once, in short sentences with bulleted lists in place of comma chains. What the code on next does is in the main sections; the two points the old SPEC deferred, sharing bans between instances and RELP, are in a last section, "Planned, not built", each marked as planned. The status line, the milestones and the build order are dropped as history. Where the old SPEC disagreed with the code, the new one follows the code; the PR body lists each such point. Model: fable-5-1	2026-10-22 18:52:51 +00:00
sneak	a0d2c21346	Add README, SPEC and tool evaluation, closes #1 Initial documents: what smallwebwaf is and why, the proposed feature list, the design spec with the rule file format and the open design questions, and the survey of existing tools. Model: fable-5-1	2026-09-21 07:42:45 +00:00

Author

SHA1

Message

Date

sneak

e44ba7ee5e

SPEC rework after review: each requirement once, gitea notes to docs/

check / check (push) Canceled after 0s

Details

Every requirement is stated once, where it belongs, and linked from
elsewhere. The notes on gitea move to docs/gitea.md, which
script/gitea-requests points at. The list of settings that take off
is exact, the non-goal that contradicted the planned item is gone,
and the sentences the review named are split or reordered. The
package comments in internal/waf and internal/anomaly point at the
renamed sections.

Model: fable-5-1

2026-10-22 19:43:03 +00:00

sneak

7fb8662e69

SPEC rewritten from scratch, short and plain, built and planned apart (closes #156 )

check / check (push) Canceled after 0s

Details

The old SPEC opened with a draft status and milestone narrative, said
several requirements twice, and ended with a build order that is all
built. The new one keeps every requirement the old one states, said
once, in short sentences with bulleted lists in place of comma chains.
What the code on next does is in the main sections; the two points the
old SPEC deferred, sharing bans between instances and RELP, are in a
last section, "Planned, not built", each marked as planned. The status
line, the milestones and the build order are dropped as history. Where
the old SPEC disagreed with the code, the new one follows the code; the
PR body lists each such point.

Model: fable-5-1

2026-10-22 18:52:51 +00:00

sneak

a0d2c21346

Add README, SPEC and tool evaluation, closes #1

Initial documents: what smallwebwaf is and why, the proposed feature list, the design spec with the rule file format and the open design questions, and the survey of existing tools.

Model: fable-5-1

2026-09-21 07:42:45 +00:00