Update dependencies and apply code formatting

- Updated swift-async-algorithms from 0.0.1 to 1.0.0
- Added swift-collections dependency (1.2.0)
- Applied consistent markdown formatting (bullet points, spacing)
- Updated badge syntax with alt text for accessibility
- Minor spacing and formatting improvements throughout README files

These are maintenance updates to keep dependencies current and formatting consistent.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: fatbobman

Package.resolved

@@ -22,7 +22,7 @@ let package = Package(
     dependencies: [
         // Dependencies declare other packages that this package depends on.
         // .package(url: /* package url */, from: "1.0.0"),
-        .package(url: "https://github.com/apple/swift-async-algorithms", from: "0.0.1"),
+        .package(url: "https://github.com/apple/swift-async-algorithms", from: "1.0.0"),
     ],
     targets: [
         // Targets are the basic building blocks of a package. A target can define a module or a test suite.

Package.swift

@@ -2,24 +2,26 @@
 
 Helps you easily handle Core Data's Persistent History Tracking
 
-![](https://img.shields.io/badge/Platform%20Compatibility-iOS%20|%20macOS%20|%20tvOS%20|%20watchOs-red) ![](https://img.shields.io/badge/Swift%20Compatibility-5.5-red)
+![os](https://img.shields.io/badge/Platform%20Compatibility-iOS%20|%20macOS%20|%20tvOS%20|%20watchOs-red) ![swift](https://img.shields.io/badge/Swift%20Compatibility-5.5-red)
 
 [中文版说明](https://github.com/fatbobman/PersistentHistoryTrackingKit/blob/main/READMECN.md)
 
-## 🚀 Swift 6 Branch Available!
+## 🚀 Swift 6 Branch Available
 
 > **🎯 New Swift 6 Compatible Version Available**
-> 
+>
 > We've created a comprehensive **Swift 6 adaptation** with full concurrency safety, true Sendable compliance, and memory leak fixes. The new version is available in the `swift6-adaptation` branch.
 >
 > **✨ Key Improvements:**
+>
 > - 🔒 **True Sendable Compliance** - Not just `@unchecked Sendable`
 > - 🧵 **Data Race Free** - Comprehensive concurrency testing
 > - 🛡️ **Memory Safe** - Zero retain cycles or memory leaks  
 > - 🧪 **Swift Testing Framework** - Modern testing infrastructure
 > - 📚 **Enhanced Documentation** - Comprehensive guides and examples
 >
 > **🔄 Try it out:**
+>
 > ```swift
 > dependencies: [
 >     .package(url: "https://github.com/fatbobman/PersistentHistoryTrackingKit.git", branch: "swift6-adaptation")
@@ -45,13 +47,13 @@ The **Persistent History Tracking Kit** will automate the above process for you.
 
 Upon receiving a remote notification of Persistent History Tracking from Core Data, Persistent History Tracking Kit will do the following:
 
-* Query the current author's (current author) last merge transaction time
-* Get new transactions created by other applications, application extensions, background contexts, etc. (all authors) in addition to this application since the date of the last merged transaction
-* Merge the new transaction into the specified context (usually the current application's view context)
-* Update the current application's merge transaction time
-* Clean up transactions that have been merged by all applications
+- Query the current author's (current author) last merge transaction time
+- Get new transactions created by other applications, application extensions, background contexts, etc. (all authors) in addition to this application since the date of the last merged transaction
+- Merge the new transaction into the specified context (usually the current application's view context)
+- Update the current application's merge transaction time
+- Clean up transactions that have been merged by all applications
 
-For more specific details on how this works, read [在 CoreData 中使用持久化历史跟踪](https://fatbobman.com/zh/posts/persistenthistorytracking/) or [Using Persistent History Tracking in CoreData ](https://fatbobman.com/en/posts/persistenthistorytracking/).
+For more specific details on how this works, read [在 CoreData 中使用持久化历史跟踪](https://fatbobman.com/zh/posts/persistenthistorytracking/) or [Using Persistent History Tracking in CoreData](https://fatbobman.com/en/posts/persistenthistorytracking/).
 
 ## Usage
 
@@ -114,15 +116,14 @@ allAuthors: ["appAuthor", "extensionAuthor", "appBatchAuthor"],
 
 Whether or not to merge network data imported by Core Data with CloudKit, is only used in scenarios where the Core Data cloud sync state needs to be switched in real time. See [Switching Core Data Cloud Sync Status in Real-Time](https://fatbobman.com/en/posts/real-time-switching-of-cloud-syncs-status/) for details on usage
 
-### batchAuthors 
+### batchAuthors
 
 Some authors (such as background contexts for batch changes) only create transactions and do not merge and clean up transactions generated by other authors. You can speed up the cleanup of such transactions by setting them in batchAuthors.
 
 ```swift
 batchAuthors: ["appBatchAuthor"],
 ```
 
-
 Even if not set, these transactions will be automatically cleared after reaching maximumDuration.
 
 ### maximumDuration
@@ -159,15 +160,15 @@ userDefaults: appGroupUserDefaults,
 
 Persistent History Tracking Kit currently supports three transaction cleanup strategies:
 
-* none
+- none
 
   Merge only, no cleanup
 
-* byDuration
+- byDuration
 
   Set a minimum time interval between cleanups
 
-* byNotification
+- byNotification
 
   Set the minimum number of notifications between cleanups
 
@@ -222,9 +223,9 @@ logger:MyLogger(),
 
 The output of log messages can be controlled by setting logLevel:
 
-* 0 Turn off log output
-* 1 Important status only
-* 2 Detail information
+- 0 Turn off log output
+- 1 Important status only
+- 2 Detail information
 
 ### autoStart
 

README.md

@@ -2,24 +2,26 @@
 
 帮助您轻松处理 Core Data 的持久性历史跟踪。
 
-![](https://img.shields.io/badge/Platform%20Compatibility-iOS%20|%20macOS%20|%20tvOS%20|%20watchOs-red) ![](https://img.shields.io/badge/Swift%20Compatibility-5.5-red)
+![os](https://img.shields.io/badge/Platform%20Compatibility-iOS%20|%20macOS%20|%20tvOS%20|%20watchOs-red) ![swift](https://img.shields.io/badge/Swift%20Compatibility-5.5-red)
 
 [English Version](https://github.com/fatbobman/PersistentHistoryTrackingKit/blob/main/README.md)
 
-## 🚀 Swift 6 分支现已可用！
+## 🚀 Swift 6 分支现已可用
 
 > **🎯 新的 Swift 6 兼容版本现已可用**
-> 
+>
 > 我们创建了一个全面的 **Swift 6 适配版本**，具备完整的并发安全性、真正的 Sendable 合规性和内存泄漏修复。新版本可在 `swift6-adaptation` 分支中使用。
 >
 > **✨ 主要改进：**
+>
 > - 🔒 **真正的 Sendable 合规** - 不仅仅是 `@unchecked Sendable`
 > - 🧵 **无数据竞争** - 全面的并发测试
 > - 🛡️ **内存安全** - 零保留循环或内存泄漏
 > - 🧪 **Swift Testing 框架** - 现代测试基础设施
 > - 📚 **增强文档** - 全面的指南和示例
 >
 > **🔄 试用方法：**
+>
 > ```swift
 > dependencies: [
 >     .package(url: "https://github.com/fatbobman/PersistentHistoryTrackingKit.git", branch: "swift6-adaptation")
@@ -45,13 +47,13 @@
 
 在接收到 Core Data 发送的持久历史记录跟踪远程通知后，Persistent History Tracking Kit 将进行如下工作：
 
-* 查询当前应用的（current author）上次合并事务的时间
-* 获取从上次合并事务日期后，除了本应用程序外，由其他应用程序、应用程序扩展、后台上下文等（all authors）新创建的事务
-* 将新的事务合并到指定的上下文中（通常是当前应用程序的视图上下文）
-* 更新当前应用程序的合并事务时间
-* 清理已被所有应用合并后的事务
+- 查询当前应用的（current author）上次合并事务的时间
+- 获取从上次合并事务日期后，除了本应用程序外，由其他应用程序、应用程序扩展、后台上下文等（all authors）新创建的事务
+- 将新的事务合并到指定的上下文中（通常是当前应用程序的视图上下文）
+- 更新当前应用程序的合并事务时间
+- 清理已被所有应用合并后的事务
 
-更具体的工作原理和细节，可以阅读 [在 CoreData 中使用持久化历史跟踪](https://fatbobman.com/zh/posts/persistenthistorytracking/) 或者 [Using Persistent History Tracking in CoreData ](https://fatbobman.com/en/posts/persistenthistorytracking/)。
+更具体的工作原理和细节，可以阅读 [在 CoreData 中使用持久化历史跟踪](https://fatbobman.com/zh/posts/persistenthistorytracking/) 或者 [Using Persistent History Tracking in CoreData](https://fatbobman.com/en/posts/persistenthistorytracking/)。
 
 ## 使用方法
 
@@ -114,7 +116,7 @@ allAuthors: ["appAuthor", "extensionAuthor", "appBatchAuthor"],
 
 是否合并由 Core Data with CloudKit 导入的网络数据，仅用于需要实时切换 Core Data 云同步状态的场景。具体用法请参阅 [实时切换 Core Data 的云同步状态](https://fatbobman.com/zh/posts/real-time-switching-of-cloud-syncs-status/)
 
-### batchAuthors 
+### batchAuthors
 
 某些 author（例如用于批量更改的后台上下文）只会创建事务，并不会对其他 author 的产生事务进行合并和清理。通过将其设置在 batchAuthors 中，可以加速该类事务的清理。
 
@@ -158,15 +160,15 @@ userDefaults: appGroupUserDefaults,
 
 Persistent History Tracking Kit 目前支持三种事务清理策略：
 
-* none
+- none
 
   只合并，不清理
 
-* byDuration
+- byDuration
 
   设定两次清理之间的最小时间间隔
 
-* byNotification
+- byNotification
 
   设定两次清理之间的最小通知次数间隔
 
@@ -221,9 +223,9 @@ logger:MyLogger(),
 
 通过设定 logLevel 可以控制日志信息的输出：
 
-* 0 关闭日志输出
-* 1 仅重要状态
-* 2 详细信息
+- 0 关闭日志输出
+- 1 仅重要状态
+- 2 详细信息
 
 ### autoStart
 
@@ -259,4 +261,3 @@ dependencies: [
 ## License
 
 This library is released under the MIT license. See [LICENSE](https://github.com/fatbobman/persistentHistoryTrackingKit/blob/main/LICENSE) for details.
-