@raibitsi/tiresias 0.0.0-stage → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +154 -0
- package/LICENSE +202 -0
- package/NOTICE +5 -0
- package/README.md +515 -2
- package/dist/anchor.js +768 -0
- package/dist/background.js +118 -0
- package/dist/bookmarks.js +150 -0
- package/dist/browseclear.js +219 -0
- package/dist/browsecli.js +139 -0
- package/dist/browselock.js +166 -0
- package/dist/browsetools.js +64 -0
- package/dist/cdp.js +129 -0
- package/dist/ceiling.js +138 -0
- package/dist/cleanup.js +349 -0
- package/dist/cli.js +894 -0
- package/dist/config.js +324 -0
- package/dist/confirm.js +677 -0
- package/dist/context.js +5 -0
- package/dist/cooldown.js +215 -0
- package/dist/dailylog.js +278 -0
- package/dist/diff.js +110 -0
- package/dist/dom.js +92 -0
- package/dist/doors.js +217 -0
- package/dist/echo.js +120 -0
- package/dist/engine.js +68 -0
- package/dist/envelope.js +299 -0
- package/dist/errors.js +110 -0
- package/dist/fetcher.js +68 -0
- package/dist/filereply.js +342 -0
- package/dist/files.js +492 -0
- package/dist/formflow.js +317 -0
- package/dist/forms.js +1087 -0
- package/dist/freshness.js +100 -0
- package/dist/handoffs.js +261 -0
- package/dist/history.js +119 -0
- package/dist/hook.js +101 -0
- package/dist/hookrunner.js +56 -0
- package/dist/hosts.js +408 -0
- package/dist/ics.js +371 -0
- package/dist/inside.js +277 -0
- package/dist/inspect.js +451 -0
- package/dist/itemfiles.js +84 -0
- package/dist/keys.js +404 -0
- package/dist/lang.js +285 -0
- package/dist/lifetime.js +78 -0
- package/dist/lockfile.js +32 -0
- package/dist/lru.js +27 -0
- package/dist/mcp.js +433 -0
- package/dist/needs.js +307 -0
- package/dist/nodecheck.js +12 -0
- package/dist/office.js +1518 -0
- package/dist/ots.js +310 -0
- package/dist/ownedlock.js +68 -0
- package/dist/pagecache.js +1 -0
- package/dist/parentwatch.js +18 -0
- package/dist/pdf.js +294 -0
- package/dist/pdfchild.js +17 -0
- package/dist/pdfproc.js +248 -0
- package/dist/person.js +34 -0
- package/dist/pipeline.js +757 -0
- package/dist/profiles.js +289 -0
- package/dist/queue.js +209 -0
- package/dist/reader.js +1453 -0
- package/dist/receipts.js +103 -0
- package/dist/render.js +768 -0
- package/dist/resume.js +165 -0
- package/dist/rules.js +381 -0
- package/dist/safebrowsing.js +705 -0
- package/dist/safelist.js +180 -0
- package/dist/safety.js +953 -0
- package/dist/sandbox.js +152 -0
- package/dist/saved.js +662 -0
- package/dist/savedlock.js +114 -0
- package/dist/scanner.js +219 -0
- package/dist/settings.js +419 -0
- package/dist/shelf.js +370 -0
- package/dist/shield.js +392 -0
- package/dist/shieldphrases.js +163 -0
- package/dist/signing.js +68 -0
- package/dist/sitekey.js +21 -0
- package/dist/sites.js +214 -0
- package/dist/slips.js +689 -0
- package/dist/slots.js +64 -0
- package/dist/store.js +657 -0
- package/dist/tabs.js +551 -0
- package/dist/translate.js +173 -0
- package/dist/types.js +17 -0
- package/dist/walls.js +420 -0
- package/dist/watchflow.js +216 -0
- package/dist/work.js +105 -0
- package/dist/worker.js +7 -0
- package/dist/xmltext.js +322 -0
- package/dist/zipread.js +651 -0
- package/docs/DEMO.md +229 -0
- package/docs/QUICKSTART.md +124 -0
- package/package.json +63 -4
- package/stubs/no-canvas/index.js +4 -0
- package/stubs/no-canvas/package.json +7 -0
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,154 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
Built from docs/SPEC.md, section 10, which has the full detail of every version.
|
|
4
|
+
|
|
5
|
+
## v1.0.1 (2026-11-01)
|
|
6
|
+
|
|
7
|
+
- Cancelling a read while it waits its turn no longer adds extra delays to later requests.
|
|
8
|
+
- An unexpected robots.txt “not modified” response is retried once; browsing stops if it answers “not modified” again without providing rules.
|
|
9
|
+
- Malformed Retry-After headers keep the normal fallback cooldown.
|
|
10
|
+
- Relative HTML links follow the page's first base URL; receipts still name the page that was read.
|
|
11
|
+
- Rendered text with many lines stays readable when its final lines are visible. Incomplete geometry is reported as a partial inspection.
|
|
12
|
+
- Emoji and other Unicode characters remain intact when text is split into blocks.
|
|
13
|
+
- Large plain-format reads report how much text was omitted.
|
|
14
|
+
- Cached pages honor the current rendering setting and each read's rendering request.
|
|
15
|
+
- Markdown alternatives keep the original URL's query parameters.
|
|
16
|
+
- Office text is withheld with its receipts when the reply cannot fit both.
|
|
17
|
+
- Known archive signatures keep their archive warning even when the filename claims to be an Office document or application.
|
|
18
|
+
- Concurrent page saves cannot exceed the snapshot cap or push out earlier evidence.
|
|
19
|
+
- Replacing site restrictions no longer breaks unrelated browsing while confirmed restrictions are retained.
|
|
20
|
+
- Active calls keep their starting settings, including their scanner and translator hooks.
|
|
21
|
+
- Listing settings in private mode creates nothing and leaves folder permissions alone.
|
|
22
|
+
- Resuming a handoff works when an unrelated storage limit is invalid.
|
|
23
|
+
- History keeps questions up to 1,000 characters, marks longer cuts, and keeps questions that differ after character 500 separate in the needs report.
|
|
24
|
+
|
|
25
|
+
## v1.0.0 (2026-11-01)
|
|
26
|
+
|
|
27
|
+
The first public release. Tiresias is a browser for AI agents with no screen: your agent calls it over MCP (or you run it from the command line), it reads a page into a short outline with numbered links, answers questions with exact quotes and receipts, and says honestly who is calling. It obeys robots.txt and every request to wait, stops at a CAPTCHA, a bot check or a login and hands the page to you, and runs on your machine under your keys, with no account and no telemetry. macOS and Linux; Windows is not supported yet.
|
|
28
|
+
|
|
29
|
+
What the versions before it built, in one place:
|
|
30
|
+
|
|
31
|
+
- **Reading (v0.1, v0.5.1).** Outline first, then one section or the best quoted passages, in pages that fit a context window; markdown asked for first, `llms.txt` and `llms-full.txt` used, MCP servers, API specs and feeds reported. Every quote has a receipt. Page content always sits inside `untrusted_content`; hidden text, invisible characters and instructions aimed at an AI are flagged.
|
|
32
|
+
- **Honest by default (v0.1, v0.2).** A plain user agent, robots.txt, Crawl-delay and Retry-After on every request, one second between requests to a site, and optional Web Bot Auth signing of every request with your own key. Raibit's own copy is verified by Cloudflare (2026-11-01).
|
|
33
|
+
- **Memory (v0.3).** What changed since the last visit, a cache shared by every agent on the machine, bookmarks and a watchlist, a needs report, a hand-off ticket to resume a read after a person clears a wall, and a phishing check before every fetch (optionally Google Web Risk with your own key).
|
|
34
|
+
- **Permission (v0.4).** Profiles, and forms sent only with a permission slip you grant at a terminal; login, password, CAPTCHA and payment forms are never sent.
|
|
35
|
+
- **Files (v0.5, v0.6).** A file is named by its first bytes and comes back as a warning with its fingerprint, never run; zip listings, Office text and calendar invites are read in memory; your own virus checker can be plugged in. Tabs, a downloads shelf, per-site settings and a settings page.
|
|
36
|
+
- **JavaScript pages and languages (v0.7).** Rendering in the Google Chrome you already have, off until you allow it, with every request the page makes fetched under Tiresias's rules; walls and hidden text judged by what the browser shows; the language of every read; your own translator.
|
|
37
|
+
- **Proof (v0.8).** Signed snapshots of exactly what a read received, and free Bitcoin timestamps (OpenTimestamps) that prove a receipt existed then and was not edited.
|
|
38
|
+
- **Hardening (v0.9, v0.9.1).** Risky settings take an all-caps confirmation phrase and are logged; a security audit, a fuzz script, a memory ceiling for the MCP server and an optional Docker box; then every deferred finding from the reviews closed, so v1.0 ships with no known bug.
|
|
39
|
+
|
|
40
|
+
In this release: the docs were rewritten for a first-time reader (README, QUICKSTART, SECURITY.md, and a new docs/DEMO.md with real output), the install is `npm install -g @raibitsi/tiresias`, two failures seen only on Linux were fixed (the anchor's receipt cursor after a file is written again under the same inode; a test whose waits ended during a slow run), and two refusal texts no longer say "v0.x". The key directory signing guidance now covers live signing, which Cloudflare asks for.
|
|
41
|
+
|
|
42
|
+
**Upgrading from v0.8:** if you had turned on saving, rendering or anchoring, each is held off after the upgrade until you confirm it once, with whichever of these apply:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
tiresias settings confirm saving --confirm "YES, TURN ON SAVING"
|
|
46
|
+
tiresias settings confirm rendering --confirm "YES, TURN ON RENDERING"
|
|
47
|
+
tiresias settings confirm anchoring --confirm "YES, TURN ON ANCHORING"
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
(`rendering` at `auto` takes `"YES, TURN ON AUTOMATIC RENDERING"`.) The first reply after the upgrade lists what is waiting, `tiresias mcp` prints it on standard error at start, and `tiresias settings` shows it. Upgrading from v0.9.x needs nothing.
|
|
51
|
+
|
|
52
|
+
## v0.9.1 (2026-10-31)
|
|
53
|
+
|
|
54
|
+
The pre-v1.0 sweep. Every MEDIUM and LOW finding deferred from v0.7.0, v0.8.0 and v0.9.0 (67 in all) was closed: 64 fixed, each with a test that fails without the fix, and 3 designed away (the behavior decided and written down). Two of them were decided by Travis: on a rendered page, text with `pointer-events: none` that cannot be measured for clipping now makes the inspection partial so the HTML checks also run; and any background image or gradient counts as covering the text under it (it can flag text under a see-through decorative layer, but never shows hidden text). Google Web Risk lookups stay exempt from site spacing (they are calls to Google, not site visits). Codex wrote the fixes and Claude reviewed each one; then Codex reviewed the whole sweep until a round came back clean. The full list is in SPEC.md, section 10, v0.9.1.
|
|
55
|
+
|
|
56
|
+
What you may notice:
|
|
57
|
+
|
|
58
|
+
- **`tiresias mcp` now tells you on standard error when a setting is held back.** If config.json turns on a risky setting that has not been confirmed (the usual case after upgrading from v0.8 with saving, rendering or anchoring on), the server prints one line at start with the exact `tiresias settings confirm ... --confirm '...'` command for each. Your AI app usually keeps that in its MCP server log.
|
|
59
|
+
- **Rendered pages:** walls and hidden text are judged more exactly (text in `display: contents` wrappers, dark-scheme pages, `color()` and `oklch()` colours, `xmp` and `textarea` text, page elements named like browser built-ins, CAPTCHA and password boxes past the first 2,000 candidates). A failed render keeps the last good rendered copy; an explicit `render` renders again unless a rendered copy is still fresh by the site's own caching rules (`fresh: true` always renders again); cached rendered replies keep their walls and hidden-text codes; a redirected script or style is handed to Chrome as a redirect; a large fixed layer above the text gets its own overlay note.
|
|
60
|
+
- **Save page and receipts:** a snapshot is never written that `saved verify` would refuse; quotes containing NUL and pages with odd characters verify; Office receipts name their snapshot; `clear` counts what it really removed. A failed `saved verify` or `receipts verify` now prints `status: "error"` with `reason: "verification_failed"` on standard error (exit codes unchanged).
|
|
61
|
+
- **Anchoring:** a bad answer from one calendar can no longer spoil a batch another calendar served well; calendars' Retry-After is honored; very large stores keep every batch searchable and resume long scans; `receipts prove --out` cleans up after itself on failure.
|
|
62
|
+
- **Confirmations:** every reply path carries the settings notice; a 24-hour notice is never cut short; always-allowed ports and the default spacing no longer ask for a phrase; `scanner off` and `translator off` work while `sites` is broken; suggested commands put `--confirm` in the right place.
|
|
63
|
+
- **Reading:** markdown code keeps its indentation; very deep pages and lists stay within the time budget; an unsolicited "not modified" answer is never served from an older parse; a JavaScript-only page read without rendering says so; `resume` keeps `render` and `translate`; a cancelled read writes nothing; `history --text` and `receipts --text` start with a count line. The parser version is 14, so a page cached by the older reader is parsed again once.
|
|
64
|
+
- **pdf.js's native canvas add-on** that an `npm install -g` puts on disk stays unbundled on purpose (it is never loaded; bundling would tie outside security fixes to Tiresias releases). README says so.
|
|
65
|
+
|
|
66
|
+
## v0.9.0 (2026-10-31)
|
|
67
|
+
|
|
68
|
+
Risky settings need confirmation (W-32). Turning a risky setting on or looser (`saving`, `rendering`, `translator`, `scanner` with `--send-file`, `anchoring`, `anchor_calendars`, `safe_browsing` off, and per site more `ports`, lower `spacing_seconds`, `never_visit` or `hand_off` off) takes an exact all-caps phrase naming it, passed as `--confirm` (for example `--confirm "YES, TURN ON SAVING"`); a wrong or missing phrase changes nothing and prints the phrase. Turning things off or stricter never asks. Each change is recorded in history and the daily log with who made it (a terminal or not, best effort), and CLI and MCP replies carry `settings_notice` for 24 hours. A hand edit of `config.json` that loosens is not in force until confirmed (`tiresias settings confirm`); the last confirmed state lives in `confirmations.json`, and no record means the safe defaults (an owner upgrading from v0.8 with a risky setting on confirms it once). `TIRESIAS_RENDERING`, `TIRESIAS_SAFE_BROWSING=0` and `TIRESIAS_ALLOW_PORTS` loosen only with their phrase in `TIRESIAS_CONFIRM`. `tiresias settings confirmations off|on` (each with its own phrase) stops or resumes the asking; `tiresias settings` shows the state. MCP still cannot read or change any setting. It stops accidents and casual page-text tricks, not a fully fooled agent; the log makes that visible. Full record: `docs/v0.9/confirm.md`.
|
|
69
|
+
|
|
70
|
+
**Upgrading from v0.8:** if you had turned on saving, rendering or anchoring, each is held off after the upgrade until you confirm it once. Run whichever apply:
|
|
71
|
+
|
|
72
|
+
```
|
|
73
|
+
tiresias settings confirm saving --confirm "YES, TURN ON SAVING"
|
|
74
|
+
tiresias settings confirm rendering --confirm "YES, TURN ON RENDERING"
|
|
75
|
+
tiresias settings confirm anchoring --confirm "YES, TURN ON ANCHORING"
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
(If you had `rendering` at `auto`, its phrase is `"YES, TURN ON AUTOMATIC RENDERING"`.) Until then the first reply after the upgrade, CLI or MCP, lists each held-off setting with its exact command, and `tiresias settings` shows what is waiting. If you use Tiresias only through an AI app, run `tiresias settings` once at a terminal after upgrading, since the notice reaches you only if the agent passes it on.
|
|
79
|
+
|
|
80
|
+
Hardening audit of the whole codebase as it will be published. A `SECURITY.md` threat model; SPDX license headers; `npm audit` fixes under the MCP SDK; an opt-in fuzz script (`npm run fuzz`). Fixed, each with a test: a `Content-Encoding` Tiresias does not decode now fails the request (a compressed robots.txt used to read as "no rules"); a robots.txt that is not text, any 2xx answer, a 206, and rules that write `*` or `$` as `%2A` / `%24` are all honored (unreadable means the site says no); the daily log is bounded; CLI `receipts` and `history` put their records inside `untrusted_content`, as MCP does; one MCP server runs at most 8 tool calls, 4 parser workers and 2 renders at once, with fixed-text refusals past their queues; the MCP message boundary caps arguments (1,000 elements, 8 MB) and open requests (64), pauses reading while output backs up, and never repeats a caller's text outside the envelope; bad dates get fixed texts; the in-process cooldown list is bounded (at most 10,000 waits by name, the rest in a fixed 8 MiB keyed store that never forgets or shortens a wait). README and SECURITY.md wording that overclaimed was corrected. Full record: `docs/v0.9/hardening.md`.
|
|
81
|
+
|
|
82
|
+
The MCP client is trusted, the server has a memory ceiling, and Docker is optional (W-33). The AI app that starts `tiresias mcp` is now trusted not to flood its own server (SECURITY.md says so; every limit stays). `tiresias mcp` runs the server under its own memory ceiling, `TIRESIAS_MEMORY_MB` (default 1024 MB, `off` to skip): at the ceiling it stops with a clear line on standard error and a "Server stopped" line in the daily log, and the app can start it again. A `Dockerfile` (official Node 22 slim image pinned by digest, non-root, rendering off) and `docs/docker.md` give advanced owners a hard box with memory, CPU and process limits and a read-only file system; same commands, same store. v1.0 will support macOS and Linux; Windows is not yet supported. Full record: `docs/v0.9/client-trust.md`.
|
|
83
|
+
|
|
84
|
+
A site's echo of a secret is withheld, not masked. When the answer to a sent form repeats a hidden value or a cookie the site set for that call (6 characters or more), Tiresias now withholds the whole answer (`form.reason: "secret_withheld"`, the HTTP status and size only) instead of masking it as `[hidden value]`. The answer is checked once as received, with HTML, percent and JSON escapes decoded and case, quotes and spaces ignored, and again before anything from it is recorded. `counts.receipts_withheld` is gone. Best effort, stated in SECURITY.md: an echo in an encoding Tiresias does not decode is not caught.
|
|
85
|
+
|
|
86
|
+
Private launch rehearsal: a newcomer's first hour, end to end (an npm tarball installed into a temporary prefix, a fresh home, the README followed literally, MCP through Claude Code and a small client, rendering, saving, anchoring against a local calendar, slips and forms, the upgrade from a v0.8 store, and the unhappy paths). Fixed what tripped them up: a label Tiresias makes, `(top of page)` and `(structured data)`, is no longer quoted in a receipt as if the page said it; `receipts --url https://example.com` finds what was recorded as `https://example.com/`; an older Node, a mistyped option, an address with no `https://`, a store folder that cannot be written and being offline each get a plain message saying what to do (the store one used to say "internal error"); `--text` prints a page read's receipt count instead of every receipt as JSON, and says so when a listing is empty; hints that name a risky setting now carry its phrase; `--help` starts with the first command to try. The README's Claude Code line uses `--scope user`, and states that an npm install puts pdf.js's optional native add-on on disk, where the PDF child's permission model keeps it from loading. New `docs/QUICKSTART.md` (shipped in the package). The recurring render flake under full-suite load (the first render of a test file starting Chrome cold under a shortened limit) is fixed in the tests. The parser version is 13, so a page cached by the older reader is parsed again. Full record: `docs/v0.9/rehearsal.md`.
|
|
87
|
+
|
|
88
|
+
## v0.8.0 (2026-10-31)
|
|
89
|
+
|
|
90
|
+
Save page (W-28) and tamper-proof receipts (W-08). With the owner's new `saving` setting at `ask` (default `off`; owner only, never through MCP or an environment variable), `read --save` and the MCP read's `save` keep a snapshot in the profile's `saved/` folder: the bytes the read received (after transfer framing and Content-Encoding, before charset decoding) and, for a rendered read, the rendered HTML, with a `manifest.json` signed by the profile's slip key. The snapshot's id is the SHA-256 of the manifest's facts; every receipt of that read carries it as `snapshot`. `tiresias saved` lists, shows, verifies (re-hash, signature, and each receipt's quote found in the saved bytes by the same reader steps) and deletes snapshots. A save always fetches; private mode, `no-store` pages, walls and errors save nothing; a file warning saves only its fingerprint. Caps: `max_saved_mb` (100) and 1,000 snapshots, a save over them is refused, never evicting; `keep_saved_days` (90) through `clear` and the daily trim. Full record: `docs/v0.8/save.md`. And with the owner's new `anchoring` setting `on` (default `off`; owner only, never through MCP or an environment variable), `tiresias anchor` timestamps the fingerprints of new receipt records and saved snapshots through OpenTimestamps (free, Bitcoin-backed, no wallet or account): one Merkle tree per batch over salted leaves in a random order, and only its root sent to the calendars (`anchor_calendars`, default the four public ones), through Tiresias's own fetcher. `anchor status`, `anchor upgrade`; `tiresias receipts` shows each record's `record_fingerprint` (a file warning keeps its own `fingerprint`, the file's SHA-256); `receipts prove <id> [--out]` exports the record, salt, Merkle path and a standard `.ots` file; `receipts verify <bundle>` checks it offline and names the step that needs a Bitcoin block header. The OpenTimestamps format is implemented in `src/ots.ts` (no new package). Private mode is never anchored; each profile anchors separately; anchoring is never on the read path. Full record: `docs/v0.8/anchor.md`. At integration the receipts listing's new field was named `record_fingerprint`, so a file-warning record keeps its own `fingerprint`. Integration review also closed five private-mode gaps, three of them older than v0.8: a private session (`--private` or `TIRESIAS_PRIVATE=1`) now refuses `receipts prove --out`, `clear` (except `--dry-run`), `log --to`, `keys init` and `keys sign-directory --out`, and `tiresias mcp --private` now serves a private session (the flag used to be ignored). 16 MEDIUM and LOW findings are deferred to the compute-day sweep (docs/SPEC.md section 10).
|
|
91
|
+
|
|
92
|
+
## v0.7.0 (2026-10-31)
|
|
93
|
+
|
|
94
|
+
JavaScript-only pages (W-10), translate (W-26), and walls and hidden text revisited with rendering (N-02, N-05). Optional rendering in the Google Chrome already installed, driven over a pipe with no new package, off by default and turned on only by the owner (`rendering` off|ask|auto); every request the page makes goes through Tiresias's own rules, under caps on time, requests and bytes. On a rendered page the browser decides walls and hidden text. Every read reports its language (13 languages, no dependency), the shield matches phrases aimed at an AI in all 13, and an optional owner-set translation hook (`tiresias translator`) answers `read` with `translate`. Every request is now counted and capped by the bytes its connection receives, for plain reads too. Built as three tracks, reviewed by Codex, then together; deferred MEDIUM and LOW findings are listed in SPEC.md, section 10, v0.7.0.
|
|
95
|
+
|
|
96
|
+
## v0.6.1 (2026-10-30)
|
|
97
|
+
|
|
98
|
+
The compute-day sweep: the 10 MEDIUM and LOW findings deferred from v0.6.0, each fixed with a test (written by Codex, reviewed by Claude). Office parts with repeated or out-of-order containers are refused; long Office lines page in bounded blocks and the whole reply stays in its limit; receipts from a file a person saved keep their source; resume honors section and question for a saved Office file; Office answers to a sent form withhold receipts touched by hidden values before anything is logged; tabs honor current site settings for cached copies; the downloads shelf keeps the macros flag; `tiresias settings` lists `TIRESIAS_MAX_INSPECT_BYTES`. See SPEC.md, "Deferred to compute-day sweep".
|
|
99
|
+
|
|
100
|
+
## v0.6.0 (2026-10-26)
|
|
101
|
+
|
|
102
|
+
Inside files, plus browser basics. Zip listing without unpacking, Office text without macros (with receipts, section paging and question search), and calendar events from `.ics` files; tabs and back/forward (W-24), the downloads shelf (W-27), site settings per host (W-25), the `tiresias settings` command (W-29) and a fast first read with the door checks in the background (W-30). Closes W-24, W-25, W-27, W-29, W-30 and the "Not in v0.5" items of section 4.4.
|
|
103
|
+
|
|
104
|
+
## v0.5.0 (2026-10-20)
|
|
105
|
+
|
|
106
|
+
Released: dangerous files (W-20) and the owner's own scanner (W-21), built to the coordinator's scope in section 4.4, after Codex round 68, the final, severity-rated round, found nothing HIGH (`reviews/2026-10-20-codex-round-68.md`: 0 high, 1 medium, 1 low). The entries below are the work log kept while v0.5 was built.
|
|
107
|
+
|
|
108
|
+
## v0.4.0 (2026-10-18)
|
|
109
|
+
|
|
110
|
+
Released: profiles (W-18), permission slips (W-05) and permission-gated forms (W-04), after Codex round 57 found nothing blocking. The entries below are the work log kept while v0.4 was built.
|
|
111
|
+
|
|
112
|
+
## v0.3.0 (2026-10-17)
|
|
113
|
+
|
|
114
|
+
Released: needs report (W-12), diffs (W-02), bookmarks and watchlist (W-16), handoff and resume (W-06), shared cache (W-03), Safe Browsing (W-19), after Codex round 45 found nothing blocking. The entries below are the work log kept while v0.3 was built.
|
|
115
|
+
|
|
116
|
+
## v0.2.0 (2026-10-17)
|
|
117
|
+
|
|
118
|
+
Released: signing (N-07), the daily log (W-13), private mode (W-14), storage limits (W-15) and PDFs (W-17), merged to main after Codex round 35 found nothing. **W-09:** submitted to Cloudflare's Bots and Agents Directory (BotBase) on 2026-10-17 as Tiresias, operator Raibit, Direct, category Agent, content use immediate, Web Bot Auth with the raibit.ai key directory. Status: waiting for review. The entries below are the work log kept while v0.2 was built.
|
|
119
|
+
|
|
120
|
+
## v0.1.8 (2026-10-16)
|
|
121
|
+
|
|
122
|
+
Software release. Closes the six non-blocking items from Codex review round 8 (`reviews/2026-10-16-codex-round-8.md`: no blocking findings, ready for a private push).
|
|
123
|
+
|
|
124
|
+
## v0.1.7 (2026-10-16)
|
|
125
|
+
|
|
126
|
+
Software release. Fixes Codex review round 7 (`reviews/2026-10-16-codex-round-7.md`: three blocking, two non-blocking).
|
|
127
|
+
|
|
128
|
+
## v0.1.6 (2026-10-16)
|
|
129
|
+
|
|
130
|
+
Software release. Fixes Codex review round 6 (`reviews/2026-10-16-codex-round-6.md`: round 5 verified fixed; four blocking items from a whole-repo pass, one small regression).
|
|
131
|
+
|
|
132
|
+
## v0.1.5 (2026-10-16)
|
|
133
|
+
|
|
134
|
+
Software release. Fixes Codex review round 5 (`reviews/2026-10-16-codex-round-5.md`: three blocking items in rotation, two small).
|
|
135
|
+
|
|
136
|
+
## v0.1.4 (2026-10-16)
|
|
137
|
+
|
|
138
|
+
Software release. Fixes Codex review round 4 (`reviews/2026-10-16-codex-round-4.md`: one blocking item, B1, plus small ones). Numbers: A = round-3 item status, B-1 and B-2 = new in round 4.
|
|
139
|
+
|
|
140
|
+
## v0.1.3 (2026-10-16)
|
|
141
|
+
|
|
142
|
+
Software release. Fixes Codex review round 3 (`reviews/2026-10-16-codex-round-3.md`: no High; B1 to B5 new, plus residual partials).
|
|
143
|
+
|
|
144
|
+
## v0.1.2 (2026-10-16)
|
|
145
|
+
|
|
146
|
+
Software release. Fixes Codex review round 2 (`reviews/2026-10-16-codex-round-2.md`: 13 fixed, 13 partial, 13 new). Numbers below: P = round-1 finding that was partial, N = new finding in round 2.
|
|
147
|
+
|
|
148
|
+
## v0.1.1 (2026-10-16)
|
|
149
|
+
|
|
150
|
+
Software release. Spec stays at 0.5 apart from section 6.1. Fixes Codex review round 1 (`reviews/2026-10-16-codex-round-1.md`, 26 findings, verdict "not ready").
|
|
151
|
+
|
|
152
|
+
## v0.1.0 (2026-10-16)
|
|
153
|
+
|
|
154
|
+
Software release. Spec stays at 0.5.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|