Repository navigation
fix(archivist): keep what the family writes about a capture - #219
Merged
Merged
Conversation
arthware-dev
changed the title
added 8 commits
October 14, 2026 09:22
A photo or file posted with a caption outside the documents room was captured without it: the model summarised the picture alone and the entry had no trace of what the sender wrote. - The caption now reaches the model with the upload, as it already did for a filed document, so the summary says what the sender said. - The entry keeps the caption word for word under `## Caption`. - A correction reads the caption off the upload it was filed from, falling back to the entry's, so replying to the filing restores a caption an earlier filing dropped.
An audio file posted with a caption is transcribed into a text message before the archivist sees it, and the transcript replaced the caption, so the note kept only the spoken words. The transcript's provenance now keeps the upload's own `body` beside its `filename`, and the archivist reads the caption off them by the same rule as for a photo or a file: the model reads it with the transcript and the note keeps it under `## Caption`.
A reply in a capture's thread refiles it, and the refile wrote the entry to a new path: its file name follows the title, which the model rewords, and its folder followed whoever replied, so a capture from a topic room moved into the replier's own folder. The old file was deleted, and every link to it broke: the wiki page, the topic page and list items. A capture now keeps the path it was first filed under. A refile changes what the entry says, never where it is.
`stack messages upload <room> <path> --caption <text>` posts the file with a caption, the way a phone does when the sender types something under a picture: the words in `body`, the file's name in `filename`. The test driver passes it on as `driver as <user> send <room> <file> --caption <text>`.
A reply in a capture's thread refiles it, and the model works the reply into the summary in its own words. What the family wrote was otherwise kept only in the chat, so a detail the paraphrase left out was gone from the entry. The entry now keeps every reply in its thread under `## Replies`, with its author and in the order they came, as a diary card does. A refile reads the earlier replies back and adds the new one.
A photo posted outside the documents room was filed under `bookmarks/`, next to saved links. It is the family's own record, with their caption and replies, like a note they type. It is now filed under `notes/`. A PDF stays a bookmark. Photos filed before this move in the next change.
A reply to a filing found the capture at the path the filing message recorded. When the capture had moved since, the correction answered that it was missing. A correction now looks the capture up by its `capture_id`, the event id of the message it was filed from, in the local copy of the family memory. The recorded path is the fallback while that copy has not caught up with a write.
Photos posted outside the documents room are filed as notes now. The ones filed before still sat under `bookmarks/`. The archivist moves them once, a minute after it starts, in one commit: each photo is written under `notes/` with `type: note`, and saved links and PDFs stay where they are. An entry filed before 0.4.0-rc.1 does not show its picture, so the archivist downloads its upload to tell a photo from a PDF. Chat links and corrections find a capture by its id and follow the move. The migration is its own module, to be removed once the framework runs stacklet migrations.
arthware-dev
force-pushed
the
fix/capture-caption
branch
from
October 14, 2026 07:26
bab3594 to
a59416e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
## Replies.stack messages upload --captionposts a file with a caption, for the rig and the test driver.