famstack 0.3.0-beta.3 - what you file stays filed

What you file stays filed.

Beta 2 was about the family brain learning to talk. Beta 3 is about the parts underneath it holding. Documents that used to get cancelled halfway through filing now finish. Links posted in chat stop dying when the server moves. Paperless makes the jump to 3.0 that beta 2 had to defer. And when something does break, stack doctor tells you which command fixes it. 52 commits since beta 2.

Highlights

• Paperless-ngx 3.0.4. Beta 2 pinned to 2.20.15 because 3.0's redesigned task API broke filing. This is the real move. 3.0 also stopped rejecting a re-uploaded identical file unless a flag is set, and reports a rejection as a task that succeeds carrying the twin's id, so left alone it would have quietly filed second copies.
• Filing finishes. Long scans and multi-page emails were cancelled partway through, leaving a document in Paperless with no tags, no summary and nothing in the wiki, findable but unreadable. The limits are measured now: one 28,000-token pass takes 163 seconds on a Mac with RAM to spare, and a filing makes three of them. Re-uploading an interrupted document finishes it, instead of answering "already filed" and stopping.
• Links that outlive the server. Every link the archivist posted into a room carried the document server's address as it looked at that moment, and chat history is append-only, so changing the domain or moving Paperless left all of them dead. They now point at the stack's own resolver, which looks up where a document lives when someone clicks.
• stack doctor. stack status tells you a stacklet is failing. Doctor tells you why and prints the command that fixes it. It catches the one that took this instance's bots down: a container keeps the environment it was created with, so editing stack.toml changes nothing until the container is recreated, and every login fails against config that looks correct on disk.
• The archivist stays out of your conversations. Talking to the agent in a thread got filed as a note, and every reply after it read as a correction to that note. Inside a thread the archivist now only acts where it answered first.
• Ask the vault a question in plain words. stack memory search --nl "what do we still need for the camping trip" turns the question into the words actually on disk, and prints what it searched for so a bad guess is visible. The default is unchanged: regex, no model, same speed.
• Installing local AI works again. Homebrew 6 refuses to run formulas from outside its own repositories until you trust them, so stack up ai died at its first brew command on any up-to-date Mac.
• The wiki looks like famstack and carries the family's name, and a write shows up in it right away instead of on the next rebuild.
• Stacky got some work too, mostly so it stops falling over: it can file things into the vault and tick items off a list rather than only reading, and it answers to its name instead of only to an autocompleted Matrix pill. Read the caveat below before you rely on any of it.

Upgrading from 0.3.0-beta.2

git fetch --tags
git checkout v0.3.0-beta.3
./stack restart all

Good to know: Paperless migrates its own database the first time it starts on 3.0. This happens unattended and nothing is asked of you. It is a one-way step though, since 2.20.15 will not boot on a migrated database, so going back to beta 2 means restoring a backup from before the upgrade.

Where it's rough

The agent is still the least finished thing here. It behaves stupidly often enough that it is not the reason to run this release: it picks a related note over the exact one, takes questions more literally than a person would, and needs another round of work before it earns being called a feature. Treat it as something to try, not something to depend on.

The filing timeouts are generous now rather than smart. famstack still can't tell a model working slowly from one that has stopped, it just waits a lot longer before giving up. On a 16 GB Mac running photos and documents alongside, a long scan is still minutes of waiting.

Open an issue or come to the Discord.