Skip to content

feat(app): the card to let a bot reach another crew, and the list in its details - #195

Merged
httpsphl merged 2 commits into
mainfrom
feat/crew-access-card
Oct 5, 2026
Merged

httpsphl merged 2 commits into
mainfrom
feat/crew-access-card

Conversation

@httpsphl

@httpsphl httpsphl commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Follow-up to #194, stacked on it: this diff includes #194's commit until that merges.

  • Card for ask_crew_access:
    • The title is "Scout wants to reach Writer, of the crew Blog" or "Scout wants to reach the crew Blog".
    • It shows what the bot wants there and why.
    • Buttons: Only now, Always Writer (only for a one-bot request), Always the crew Blog, and Deny with a note.
    • The answer goes as input: {"scope": ...}. The daemon keeps the request with its scope, so the answered line says for how long.
  • Bot details, "Other crews":
    • Lists the access the bot has for good, each with a button to take it back.
    • Calls the new methods crewAccess.list {botId} and crewAccess.revoke {accessId}.
    • Reads the list again when one of these requests is answered.
  • Texts in en, pt-BR and es; a fake for the tests.

Spec: 10.4 (the app part) and the methods in 11.

Tests:

  • crewAccess.test.tsx: the one-bot request, the whole-crew request with a deny note, and the list with revoke.
  • tests/crew_access.rs: list and revoke, and the kept scope.

Manual: ask a bot to talk with a bot of another crew. Check the card, the answered line and the details list.

…wner's OK

Crews stay closed to each other. When the owner wants it, a bot asks with
ask_crew_access: the crew, one bot of it or the whole crew, what it
needs (talk) and why. The owner allows it only now (until the bot's turn
ends), always for that bot, always for the crew, or declines. With
access, crew_roster and send_message take crew; the other side can
answer, and tasks come back. Messages and tasks across crews belong to
the recipient's crew, so deleting a crew leaves nothing dangling.

Spec 9.3, 10, 10.4.
…its details

The request card says what the bot wants in the other crew and why, with
Only now, Always <bot>, Always the crew and Deny. The answer keeps the
request with its scope, so the answered line says for how long. The
bot's details list 'Other crews' it reaches for good, each with a button
to take it back (crewAccess.list and crewAccess.revoke). Spec 10.4, 11.
@httpsphl
httpsphl enabled auto-merge October 5, 2026 15:44
@httpsphl
httpsphl merged commit ec921be into main Oct 5, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant