Repository navigation
Release: develop -> main - #408
Merged
Merged
Conversation
* Bind reviews to CONTRIBUTING.md and REVIEW.md. A review reads both files and does not change them. A new mechanism is a defect when an existing element already does that job, unless the pull request says why it cannot. * 01a10b01 - Read review rules at the base and keep the prompt a reminder. Reuse covers visible surfaces only. A pull request that changes CONTRIBUTING.md or REVIEW.md does not replace the base text for the rest of its diff. * 01a10b01 - Keep a hard requirement a defect A pull-request sentence can explain a missed reuse. It cannot clear a hard requirement or a contradiction of CONTRIBUTING.md. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
* 01a10c6e - Keep a reply gift separate from sats received on it A reply keeps the amount sent with it in sats. Later zaps and a spend proof on that reply credit receivedSats and the received fiat columns. Top-level notes stay on sats and omit the new JSON keys. Boot moves indexed zap-receipt sums off reply sats once, and does not read spend invoices. * 01a10c6e - Document reply zaps as received, not added to sats The handbook still said a zap on a reply credits sats and that the long-poll only waits on sats. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
) * Proxy the daily payout roster for founder and initiator. Funding routes call the spend JSON API. A moderator is refused before the route checks whether spend is configured. * Document the daily roster gate, errors, and spend configuration. * Document the daily roster routes and the editor exception. * Name every forwarded daily-roster error. * Normalize the daily payment comment before it is stored. Newlines become spaces, then trim. Longer than 500 is rejected, not cut. A spend 400 stays 400. * List the daily roster files in the project tree. The funding route comment names the new daily-roster paths. * Treat a failed daily-roster body read as unavailable. A readable empty or non-JSON 400 stays an invalid change. A read that throws is the same 502 as a network failure. * Say a failed daily-roster body read is unavailable on every write. The five POST error lines match GET. A 400 whose body was read stays an invalid change. * Forward the unlisted grant default on the daily roster. * Reach the recipient check when a daily roster includes the default amount. * Align the env table after the daily roster notes. * Name the daily roster success body in the handbook. * Prove the daily roster mirrors reach the role gate. An anonymous 401 returns before the editor check and before the unconfigured spend client. A moderator is refused, and an initiator or the founder sees that the client is not configured. * Align the daily roster env table with the formatter. Prettier only widened the separator row. The variables are unchanged. * Give each parallel roster mirror its own account. The shared name kept only the first eight digits of the clock, so parallel mirrors could patch one account. The name now includes the random stamp, and the patched role is checked before the session is opened. * Clear founder role after the roster mirror. A unique roster account stays a founder on the shared server and shows up in the empty trust chain. The mirror sets that role back to basis once the call returns. * Format the route table in SPEC.md. --------- Co-authored-by: TaprootFreakAI <315477232+TaprootFreakAI@users.noreply.github.com>
TaprootFreak
approved these changes
Oct 7, 2026
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
2 participants
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.
Automatic Release PR
Commits: 1 new commit(s)