story-kit: remove 256_story_bot_must_verify_other_users_cross_signing_identity_before_checking_device_verification

This commit is contained in:
Dave
2026-03-17 13:07:03 +00:00
parent e9879ce1c7
commit 3b66b89c90

View File

@@ -1,35 +0,0 @@
---
name: "Bot must verify other users' cross-signing identity before checking device verification"
agent: coder-opus
merge_failure: "Rename/rename conflict on the story file: master has it in work/4_merge/ while the feature branch has it in work/2_current/. The auto-resolver cannot handle rename/rename conflicts (it expects the file at work/1_upcoming/ which no longer exists). A human needs to resolve the story file location conflict before re-triggering the merge."
---
# Story 256: Bot must verify other users' cross-signing identity before checking device verification
## User Story
As a Matrix user messaging the bot, I want the bot to correctly recognize my cross-signing-verified devices, so that my messages are not rejected when I have a valid verified identity.
## Acceptance Criteria
- [ ] The bot's `check_sender_verified` function (or equivalent) verifies the sender's identity trust status, not just individual device verification
- [ ] When @yossarian:crashlabs.io (who has valid cross-signing keys) sends a message in an encrypted room, the bot accepts it instead of rejecting with 'no cross-signing-verified device found'
- [ ] The bot still rejects messages from users who genuinely have no cross-signing setup
- [ ] Existing tests (if any) continue to pass after the change
## Out of Scope
- TBD
## Test Results
<!-- story-kit-test-results: {"unit":[{"name":"sender_with_cross_signing_identity_is_accepted","status":"pass","details":"Verifies get_user_identity Some(_) → accepted"},{"name":"sender_without_cross_signing_identity_is_rejected","status":"pass","details":"Verifies get_user_identity None → rejected"}],"integration":[]} -->
### Unit Tests (2 passed, 0 failed)
- ✅ sender_with_cross_signing_identity_is_accepted — Verifies get_user_identity Some(_) → accepted
- ✅ sender_without_cross_signing_identity_is_rejected — Verifies get_user_identity None → rejected
### Integration Tests (0 passed, 0 failed)
*No integration tests recorded.*