feat(kinesis): implement all remaining operations for 100% conformance

[vieiralucas]

Summary

• Implement all 25 remaining Kinesis operations, bringing conformance from 38.2% to 100%
• 39/39 operations handled, 39/39 fully passing, 1611/1611 variants pass
• Tags v2 (TagResource, UntagResource, ListTagsForResource) + Resource Policy (Get/Put/Delete)
• Encryption (StartStreamEncryption, StopStreamEncryption) + Enhanced Monitoring (Enable/Disable)
• Account settings (DescribeAccountSettings, UpdateAccountSettings, DescribeLimits)
• Stream config (UpdateStreamMode, UpdateStreamWarmThroughput, UpdateMaxRecordSize)
• Consumer management (Register, Deregister, Describe, ListStreamConsumers)
• Shard management (ListShards, MergeShards, SplitShard, UpdateShardCount)
• SubscribeToShard (input validation; HTTP/2 event-stream not supported)
• Extended KinesisShard with real hash key ranges, parent tracking, open/closed state
• Added KinesisConsumer state, resource policies, account-level settings
• Write routing respects open/closed shard state after resharding
• Stream deletion cleans up associated consumers

Test plan

• cargo test -p fakecloud-kinesis — all 8 unit tests pass
• cargo clippy -p fakecloud-kinesis -- -D warnings — clean
• cargo test -p fakecloud-conformance --test kinesis — all 5 handwritten tests pass
• Conformance probes: 1611/1611 variants pass (100.0%)

---

Summary by cubic

Implements all remaining 25 Kinesis operations to reach 100% conformance (39/39 ops, 1611/1611 variants), with full tagging, resource policies, encryption, monitoring, consumers, and shard management. Adds pagination and safety checks from review feedback.

• New Features

  • Tags v2 and resource policies: TagResource, UntagResource, ListTagsForResource; Get/Put/DeleteResourcePolicy.
  • Encryption and monitoring: Start/StopStreamEncryption (KMS), Enable/DisableEnhancedMonitoring.
  • Account and limits: DescribeAccountSettings/UpdateAccountSettings; DescribeLimits.
  • Stream config: UpdateStreamMode, UpdateStreamWarmThroughput, UpdateMaxRecordSize.
  • Consumers: Register/Deregister/Describe/ListStreamConsumers (pagination).
  • Shards: ListShards (with NextToken), MergeShards, SplitShard, UpdateShardCount with hash-range validation.
  • SubscribeToShard: input validation only; returns ResourceNotFound (event-stream not supported).

• Refactors

  • KinesisShard now has real hash key ranges, parent links, open/closed state; writes target open shards; next shard index tracked; adjacency checks use checked_add to avoid overflow.
  • Added KinesisConsumer state, resource policies, and account-level settings; consumers cleaned up on stream deletion; UpdateShardCount enforces TargetShardCount <= 10000.

^{Written for commit 49ea9d2. Summary will update on new commits.}

[cubic-dev-ai]

3 issues found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="crates/fakecloud-kinesis/src/service.rs">

<violation number="1" location="crates/fakecloud-kinesis/src/service.rs:1197">
P2: `ListShards` truncates by `MaxResults` but never returns/consumes `NextToken`, breaking pagination.</violation>

<violation number="2" location="crates/fakecloud-kinesis/src/service.rs:1257">
P1: Avoid `u128` overflow in shard adjacency validation by using checked addition.</violation>

<violation number="3" location="crates/fakecloud-kinesis/src/service.rs:1374">
P1: Validate `TargetShardCount` upper bound before looping/casting to prevent overflow and state corruption.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}