how to file a good support request
a good request gets you a good answer faster. the web form, a report started from the journal or an app, and the signed-in services portal at services.solstone.app all use the same request lifecycle below. email is a separate mailbox channel.
what to include
- what happened: the actual behavior, in your words. "the journal's thinking app won't load" beats "it's broken."
- what you expected: so we know what "fixed" looks like to you.
- your version: open about and copy the line, then paste it into the request. finding your version shows where about is on each app and the journal. if you installed from a source checkout, the reported version can lag your actual code. mention that if it's you.
- your os and platform: macos, windows, linux, android, or iphone or ipad, and your processor (apple silicon, x64 or arm64) if you know it.
- how to reproduce: the steps that trigger it, and whether it happens every time or only sometimes.
a report from the journal or an app does some of this for you
if you start a report from the journal or an app, your versions and system are already filled in, along with the app's status and the lines it logged where it has them, and the journal adds which screen you were on. all of it is shown to you before anything sends, so you can edit or remove anything you don't want to share.
if you used to file from the command line: that path is gone. sol is retired and there's no CLI support command in 2.x.
what we do with it
every request is read. we'll reproduce what we can, ask if we need more, and propose a fix. you decide whether it's resolved. a request left waiting on you closes by itself. closing a request permanently removes its submitted details and leaves the disclosed minimal closed marker and narrow operational records. closing a request does not delete an email you sent us; ask support@solstone.app from the same mailbox if you want that email exported or deleted.