aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* a symlink in the sorted directory no longer redirects a stepLukasz Kasprzak2 days1-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | Placeholders were already stopped from sending a file out of the directory a rule named. A symlink is a name too, and the directory krino sorts is by the threat model's own premise a place the internet writes into: a link named after a rule's destination sent moves and copies anywhere, and under (on-conflict overwrite) trashed a file OUTSIDE the sorted directory - while the plan showed the in-tree text and the run reported success. A step whose destination passes through a symlink at or below the directory being sorted now fails. A destination the configuration names outside it - ~/docs on another disk - is the user's own arrangement and is followed as before; both cases have a test. End to end, the review's scenario (Out -> ~/secret, overwrite): before: 1 applied, the user's file replaced and trashed after: 0 applied 1 failed, the file untouched, nothing trashed Two bookkeeping bugs in MkdirAllTracked went with it: a dangling symlink read as a missing directory and was then recorded as one krino had created - undo would have unlinked a link krino never made - and a directory created by someone else between the check and the mkdir was recorded the same way.
* a duplicate test in an exclude protects like one in a ruleLukasz Kasprzak2 days1-4/+6
| | | | | | | | | | | | The scopes that drive "no rule deletes a file krino found to be a duplicate" were collected from rules only. A directory whose duplicate tests lived in (exclude ...) forms had no scopes at all, so the protection never engaged: krino explain said "yes duplicate" and the next rule permanently deleted every copy. The README's promise was false in that shape, and the spec's wording permitted it. What matters is what krino knows, not which form taught it. The spec and krino.conf(5) now say so too.
* the module path is git.labunix.xyz/krinoLukasz Kasprzak3 days2-9/+10
| | | | | | | | | | | So that go install can find it. cgit serves no go-import meta tag, so nginx answers a ?go-get=1 request for /NAME with one pointing at https://git.labunix.xyz/NAME.git; the alternative was carrying a .git suffix through every import line forever. One sed over the imports, both go.mod files, and the dependency gate's whitelist. Nothing else depends on the path. go install works from the next tag, the first release whose go.mod carries it.
* comments that explain the code, not how it was writtenLukasz Kasprzak3 days3-24/+15
| | | | | | | | | | | | | | | | | | About 340 comments cited the development process: task and plan numbers, fix waves, rulings, reviewers, and the author in the third person with a date. None of that exists outside the work itself, so to a reader it pointed at nothing. Each one now states the engineering reason it was standing in front of; where a comment was provenance and nothing else, it is gone. References to docs/design.md and docs/gui-design.md by section stay: both ship with the repository. The design documents lose their amendment diaries - CHANGELOG.md is that record - and the GUI's says plainly that the window has gone further than the document. Only comments changed. Every .go file was parsed and its code printed with comments stripped, before and after: the two hashes are identical across all 175 files.
* README for a stranger: a screenshot, a rules file, and a third less of itLukasz Kasprzak3 days1-0/+0
| | | | | | | | | | | | | | It opened with a paragraph of version history and spent 148 of its 273 lines on a walkthrough. What sells the program is a rules file and the plan it produces, so those come first, with a screenshot of the window above them. Every command and every pasted line was run again in a scratch config: the plan, the apply, the log line and the undo are this morning's real output, and the example rules file passes krino check as written (with the paths pointed at a sandbox). docs/krino-gui.png is from invented files under /tmp/krino-demo.
* gui: the path keeps its telling end, and the checklist grows three itemsLukasz Kasprzak3 days1-0/+9
| | | | | | | | | | | Squeezed, the toolbar's path label read "/t... ds". It now elides the start, since the end of a path is the part that says which directory this is, and will not shrink below about sixteen characters; the tooltip still holds it in full. The checklist gains the reordered bar, the About block, and the sandbox trap that had every file skipped: krino's own (min-age 2m) ignores a file written in the last two minutes.
* gui: an exclude is not a rule - the form no longer assumes onev0.0.11Lukasz Kasprzak3 days1-0/+2
| | | | | | | | | | | Selecting the exclude row in Forms panicked: newFormEditor read the form's rule for its when, name, action and stop, and an exclude has only the when. The editor now takes the conditions from whichever of the two the form holds and leaves out the fields an exclude has not got. Checklist item 49 covers it. Also the 0.0.11 changelog and README, and header floors wide enough that the age heading is not clipped.
* gui: conditions as a nested tree, and a way to add a directoryLukasz Kasprzak3 days1-0/+5
|
* gui: name the other copy of a duplicate, and offer to keep this one insteadLukasz Kasprzak3 days1-0/+5
|
* gui: sort the plan by name, size, age, action or ruleLukasz Kasprzak3 days1-0/+3
|
* gui: size and age columns, column toggles, readable colours, a laid-out ↵Lukasz Kasprzak3 days1-0/+6
| | | | explanation
* gui: keep every divider where it is put, and let the columns shrinkLukasz Kasprzak3 days1-0/+3
|
* gui: an applied plan says it is history; Settings says what needs savingLukasz Kasprzak3 days1-0/+5
|
* gui: aligned columns, theme colours, a second layout, and a scan-selection ↵Lukasz Kasprzak3 days1-0/+7
| | | | setting
* gui: coloured actions with headers, a filter over the plan, bulk trash or deleteLukasz Kasprzak3 days1-0/+8
|
* gui: the preview is as big as you drag it, and PDFs render to suitLukasz Kasprzak3 days1-1/+5
|
* gui: syntax colours, a file preview, and a settings windowLukasz Kasprzak3 days1-0/+11
|
* krino-gui(1), README and changelog for 0.0.10v0.0.10Lukasz Kasprzak3 days1-0/+91
|
* milestone 1 review: claims span the run, explain's chain is opt-in and its ↵Lukasz Kasprzak4 days1-4/+7
| | | | own, overrides keyed by clean path, splice and enum guards
* release notes and version mentions for 0.0.9v0.0.9Lukasz Kasprzak4 days1-1/+2
|
* krino.conf(5): WRITING RULES guide; reference corrected against the codeLukasz Kasprzak4 days1-3/+9
|
* docs: GUI design draft; code comments no longer name the ownerLukasz Kasprzak4 days1-0/+202
|
* docs: make ci passes on OpenBSD and FreeBSD; OpenBSD's go needs GOTOOLCHAIN=autoLukasz Kasprzak5 days1-1/+4
|
* release notes and version mentions for 0.0.8v0.0.8Lukasz Kasprzak5 days1-1/+5
|
* only where an earlier directory's files ended up stays claimedLukasz Kasprzak5 days1-2/+2
|
* a permanently deleted file's steps do not keep a run partly undoneLukasz Kasprzak5 days1-1/+2
|
* (matched) is unknown after an undecided rule, so a catch-all leaves an ↵Lukasz Kasprzak5 days1-1/+3
| | | | unreadable file alone
* an earlier directory's applied results stay claimed for later onesLukasz Kasprzak5 days1-1/+3
|
* tests read real documents from LibreOffice and pandoc; antiword's ↵Lukasz Kasprzak5 days1-3/+8
| | | | short-document limit documented
* krino log marks a run partly undone while reversible steps remainLukasz Kasprzak5 days1-2/+4
|
* build: VERSION checked for build and install, cross names without v, ↵Lukasz Kasprzak5 days1-4/+8
| | | | dependency gate covers tests and BSDs, tarball install, examples and extractor list tested
* main excludes checked with the defaults' case and fold; Latin-1 decoding ↵Lukasz Kasprzak5 days1-1/+4
| | | | memory; hardlink election documented
* output: wrap by terminal columns, names cannot fake step lines, -v lists ↵Lukasz Kasprzak5 days1-2/+4
| | | | unscanned destinations
* a real run's later directories are not blocked by earlier claims; -n across ↵Lukasz Kasprzak5 days1-4/+9
| | | | directories documented
* content tests are three-valued: unknown when unreadable or read in partLukasz Kasprzak5 days1-8/+18
|
* captures keep the name's diacriticsLukasz Kasprzak5 days1-4/+4
|
* text that turns binary further on has no content, like an imageLukasz Kasprzak5 days1-4/+4
|
* plan 10 re-check: cut run column, damaged undo run, emptied directory ↵v0.0.7Lukasz Kasprzak5 days1-3/+6
| | | | cleanup, text turning binary, explain flags, interrupt docs
* plan 10: docs (-n, README version and scope, trash identity, --json U+FFFD, ↵Lukasz Kasprzak5 days1-4/+16
| | | | limitations, changelog)
* plan 10: an interrupt stops between steps; nohup keeps ignoring hangupsLukasz Kasprzak5 days1-2/+5
|
* plan 10: a damaged log line refuses only its file, not the runLukasz Kasprzak5 days1-0/+4
|
* plan 10: a format with no text is no match, not unreadableLukasz Kasprzak5 days1-2/+5
|
* plan 9: docs and changelog describe what 0.0.7 doesLukasz Kasprzak5 days1-11/+27
|
* plan 9: undo review matches review, --min-age validated, future mtimes, rule ↵Lukasz Kasprzak5 days1-2/+3
| | | | names, conflict enum, dependency gate, absolute tool paths
* plan 9: content excludes fail closed; krino.conf excludes checked without ↵Lukasz Kasprzak5 days1-1/+9
| | | | directories
* plan 9: keyword cache keys on extension, max-read and Unicode tables, trims ↵Lukasz Kasprzak5 days1-11/+17
| | | | removed keywords
* plan 9: an interrupted or failed undo can be finishedLukasz Kasprzak5 days1-3/+13
|
* plan 8: fuzz decoders; fold ẞ and invalid UTF-8 correctly, refuse ↵Lukasz Kasprzak5 days1-2/+3
| | | | non-UTF-8 paths in krino new
* go 1.25, toolchain go1.26.8, x/text v0.41.0: fixes GO-2026-5970 and the ↵Lukasz Kasprzak5 days1-1/+5
| | | | reachable stdlib vulnerabilities
* plan 8: threat model, make fuzz, race and vulncheckLukasz Kasprzak5 days1-1/+40
|