[httpsphl]

Third part of the crew access work, stacked on #194 and #195: this diff includes their commits until they merge.

• ask_crew_access takes read and edit besides talk; edit includes read. Migration 0022 adds the two columns.
• New tools: crew_files {crew, bot?}, read_crew_file {crew, path} and write_crew_file {crew, path, content}, text up to 1 MB.
  • Access to one bot reaches that bot's folder and its crew's work folder. Access to the crew reaches the work folder and every bot's folder.
  • The bot's own file tools still cannot open these folders: the fences from fix(security): keep each crew apart from the others and from Botloft's data #193 stay.
  • At the top of either folder, CLAUDE.md, CLAUDE.local.md, .claude, .botloft and attachments are never readable or writable. So no crew can give another crew's bots instructions or read the owner's attachments.
  • A file the bot wrote outside its folders does not count.
  • A file out of reach and a missing one give the same error.
• App: the card shows what the bot asks for (talk, read files, edit files), and the details list says what each access allows.

Spec: 10 and 10.4.

Tests:

• tests/crew_files.rs: closed until allowed; read only; kept files refused; edit changes and adds files; the rules files stay untouched.
• Store and service unit tests, and the app tests.

Note: act_tests::an_option_is_chosen_and_a_long_list_scrolls (UIA, our own test window) failed twice locally. It passed alone once, and its code is unchanged since #189.

Manual with real Claude: give a bot read access to another crew, then ask it to summarize a file there.