simple-rcs 0.1.0__tar.gz

simple_rcs-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

simple_rcs-0.1.0/MANIFEST.in

@@ -0,0 +1,8 @@
+# Cython sources ship; the .c files it generates do not. They are build
+# byproducts, present only in a working tree that has already built once, so
+# including them would make the sdist differ between a local build and a clean
+# CI checkout -- and a stale .c silently shadowing an edited .pyx is worse.
+global-exclude *.c
+global-exclude *.so
+
+recursive-include tests *.py

simple_rcs-0.1.0/PKG-INFO

@@ -0,0 +1,261 @@
+Metadata-Version: 2.4
+Name: simple_rcs
+Version: 0.1.0
+Summary: Dependency-free reverse-delta version control for single files, with an RCS-inspired plain-text format, a hash chain, and optional GPG signatures
+Author-email: Won-Kyu Park <wkpark@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/wkpark/SimpleRCS
+Project-URL: Documentation, https://github.com/wkpark/SimpleRCS/wiki
+Project-URL: Issues, https://github.com/wkpark/SimpleRCS/issues
+Keywords: rcs,version-control,delta,diff,bsdiff,revision,history
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Version Control
+Classifier: Topic :: System :: Archiving
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# SimpleRCS
+
+**SimpleRCS** is a custom-designed, stream-based version control system for
+ultra-lightweight management of a single document. It borrows the reverse-delta
+storage idea from classic RCS and rebuilds it around modern performance
+considerations — stream-centric I/O, O(1) HEAD access, backward-scanning
+history traversal — for cases where Git's object model is overkill, or where
+direct file-system/database blob integration is preferred.
+
+It operates on a file-like object (`BinaryIO`): an on-disk path, an in-memory
+`BytesIO`, or an externally-owned handle all work the same way.
+
+## Key Features
+
+- **Reverse delta storage.** The latest version (HEAD) is always stored as
+  full text at the end of the stream; every older version is a reverse delta
+  (instructions to turn version *N+1* back into version *N*). HEAD reads are
+  O(1); historical reads are O(k), where k is the distance from HEAD.
+- **Append-dominant writes.** Committing overwrites only the previous HEAD
+  block (full text → delta) and appends the new HEAD. No full-history
+  rewrite, ever.
+- **Backward-scanning, stream-centric I/O.** History is located by scanning
+  from the end of the stream, without loading the whole file into memory —
+  scalable to long histories.
+- **Text and binary content, uniformly.** Text uses an RCS-style (`diff -n`)
+  line delta; binary content uses a BSDIFF40-compatible patch format
+  (interoperable with the native `bsdiff`/`bspatch` tools). `commit()` accepts
+  `str`, `bytes`, or `BinaryIO` directly.
+- **v2 hash chain & signatures.** Each block carries a hash of its logical
+  content plus the previous block's hash, making tampering with any past
+  version detectable. Optional GPG-based multi-signer signing/verification is
+  built in (`simple_rcs_gpg`).
+- **Intermediate snapshots.** `commit(..., snapshot=True)` stores the previous
+  HEAD as full text instead of a delta, breaking the delta chain at that point
+  for faster retrieval of that region of history.
+- **`log()` metadata-only path.** History listing parses block metadata
+  directly off the stream without decoding delta/binary payloads.
+
+## Architecture
+
+```
+[V1 Delta] [V2 Delta] ... [Vn-1 Delta] [Vn Full Text]
+                                         ^^^^^^^^^^^^^
+                                         HEAD (always full text)
+```
+
+Committing a new version:
+
+1. Read the current HEAD (full text).
+2. Compute a reverse delta (New → Old HEAD).
+3. Overwrite the on-disk HEAD block with that delta.
+4. Append the new content as the new HEAD block (full text).
+
+Checking out an old version walks backward from HEAD, applying each block's
+reverse delta (or jumping directly to a snapshot's full text) until the
+target version is reached.
+
+## Comparison
+
+Updated from the original design comparison (see [PR #2](https://github.com/wkpark/SimpleRCS/pull/2)) to reflect the current implementation:
+
+| Feature | SimpleRCS | RCS (Original) | Git | DB (Simple Snapshot) |
+| :--- | :--- | :--- | :--- | :--- |
+| Storage unit | Single file (stream) | Single file (`*,v`) | Object DB (`.git`) + working tree | DB row |
+| Delta direction | Reverse delta (HEAD = full text) | Reverse delta (HEAD = full text) | Snapshot (delta generated at pack time) | Full copy (no delta) |
+| Storage pattern | Append-dominant (tail rewrite + append) | Header update + insert | Content-addressable storage | Insert new row |
+| I/O pattern | Efficient tail write; single-pass backward scan (no re-read) for HEAD lookup | Random write (header/body) | Many small files / packfiles | DB transaction |
+| Content types | Text (RCS diff) **and** binary (BSDIFF40-compatible), same file format | Text only (binary needs external encoding) | Any (blob-based) | Any (column type) |
+| Integrity | v2: per-block hash chain + optional multi-signer GPG signatures | None | Content-addressable (SHA-1/256 of objects) | Depends on DB |
+| Intermediate snapshots | Optional, per-commit (`snapshot=True`) | Not supported | N/A (every commit is already a full snapshot object) | N/A |
+| HEAD lookup | **O(1)**, single-pass (read from end) | O(1) (read from start) | O(1) (ref → commit → tree) | O(1) (select by ID) |
+| History lookup | **O(k)**, backward scan (k = distance from HEAD) | O(N) forward scan | O(log N) DAG traversal | O(1) (select with limit) |
+| Diff engine | Greedy hash-matching (`StreamSequenceMatcher`, O(N)); Cython-accelerated Myers SES/DMP available for benchmarking | Standard `diff` | `xdiff` (Myers-based) | N/A |
+| Complexity | Low (single class, no object graph) | Medium (custom grammar) | High (complex object model) | Low (SQL) |
+
+**Note on the diff engine:** `commit()` picks its text-diff backend at import
+time. When the Cython Myers matchers were compiled — which happens
+automatically on install if a C toolchain is available — they are used, giving
+a shortest edit script. Otherwise it falls back to `StreamSequenceMatcher`, a
+greedy O(N) hash-matching algorithm that favors speed over minimal edit
+distance. Either way the install succeeds and histories stay compatible: block
+hashes cover logical content, not the stored delta bytes.
+
+Set `SIMPLE_RCS_MATCHER` to force a specific backend — `dmp_cython`,
+`ses_cython`, `stream`, `dmp_py`, `ses_py`. The names match the ids
+`tools/bench_diff.py` prints, so you can benchmark and then pin the winner.
+The `*_py` backends are first-cut reference implementations kept for
+comparison; they hit an O(ND) worst case on dissimilar inputs and are never
+chosen by fallback.
+
+## Usage
+
+```python
+from simple_rcs.simple_rcs import SimpleRCS
+
+# In-memory, or pass a file path to persist to disk
+rcs = SimpleRCS("my_document.srcs")
+
+v1 = rcs.commit("Hello\nWorld\n", author="alice", log="initial")
+v2 = rcs.commit("Hello\nSimpleRCS\n", author="bob", log="tweak line 2")
+
+rcs.checkout(v1)          # -> "Hello\nWorld\n"
+rcs.checkout()            # HEAD, i.e. v2
+
+rcs.log()                 # [{'ver': '1.1', 'author': 'bob', ...}, {'ver': '1.0', ...}]
+rcs.diff(v1, v2)           # unified diff between two versions
+rcs.blame()                 # per-line author/version attribution for HEAD
+rcs.verify()               # walks the v2 hash chain, returns True/False
+
+# Binary content works the same way
+rcs.commit(open("image.png", "rb").read(), author="alice")
+```
+
+Command-line helpers live in `tools/`: `srcs_log.py` (history/signature
+listing), `srcs_diff.py` (unified diff between versions or engines),
+`srcs_sign_head.py` (GPG-sign the current HEAD), and `bench_diff.py`
+(diff-engine benchmark harness).
+
+## Testing
+
+```
+uv run pytest tests/unit_tests/ -q
+```
+
+61 tests covering text/binary round-trips, hash-chain verification, snapshot
+handling, and `log()`'s metadata-only parsing path.
+
+## License
+
+Apache License 2.0 — see [LICENSE](LICENSE).
+
+---
+
+# SimpleRCS (한글)
+
+**SimpleRCS**는 단일 문서를 초경량으로 관리하기 위해 새로 설계한 스트림 기반
+버전 관리 시스템이다. 전통적인 RCS의 역방향 델타 저장 방식을 차용하되, 스트림
+중심 I/O, O(1) HEAD 접근, 백워드 스캔 기반 히스토리 순회 등 현대적인 성능
+고려사항으로 다시 설계했다. Git의 객체 모델이 과할 때, 혹은 파일시스템/DB
+블롭에 직접 통합하고 싶을 때 적합하다.
+
+파일과 유사한 객체(`BinaryIO`) 위에서 동작한다 — 디스크 경로, 인메모리
+`BytesIO`, 외부에서 넘겨받은 핸들 모두 동일하게 동작한다.
+
+## 핵심 특징
+
+- **역방향 델타 저장.** 최신 버전(HEAD)은 항상 스트림 끝에 전체 텍스트로
+  저장되고, 이전 버전들은 역방향 델타(버전 N+1을 N으로 되돌리는 명령)로
+  저장된다. HEAD 읽기는 O(1), 과거 버전 읽기는 O(k)(k = HEAD로부터의 거리).
+- **Append 위주 쓰기.** 커밋 시 기존 HEAD 블록만 덮어쓰고(전체 텍스트→델타),
+  새 HEAD는 끝에 추가(append)된다. 전체 히스토리를 다시 쓰는 일은 없다.
+- **백워드 스캔, 스트림 중심 I/O.** 히스토리는 스트림 끝에서부터 스캔해서
+  찾으며, 전체 파일을 메모리에 올리지 않는다 — 긴 히스토리에도 확장 가능.
+- **텍스트/바이너리 콘텐츠를 동일한 인터페이스로.** 텍스트는 RCS 스타일
+  (`diff -n`) 라인 델타, 바이너리는 BSDIFF40 호환 패치 포맷(네이티브
+  `bsdiff`/`bspatch`와 상호운용 가능)을 사용한다. `commit()`은 `str`,
+  `bytes`, `BinaryIO`를 그대로 받는다.
+- **v2 해시 체인 & 서명.** 각 블록은 논리적 콘텐츠의 해시와 이전 블록의
+  해시를 함께 가지므로, 과거 어느 버전이든 변조하면 감지된다. GPG 기반
+  다중 서명자 서명/검증도 내장(`simple_rcs_gpg`).
+- **중간 스냅샷.** `commit(..., snapshot=True)`로 커밋하면 직전 HEAD를
+  델타 대신 전체 텍스트로 저장해, 그 지점에서 델타 체인을 끊고 해당 구간의
+  과거 버전 조회를 빠르게 만든다.
+- **`log()` 메타데이터 전용 경로.** 히스토리 목록 조회 시 델타/바이너리
+  본문을 디코딩하지 않고 스트림에서 메타데이터만 직접 파싱한다.
+
+## 비교 분석
+
+[PR #2](https://github.com/wkpark/SimpleRCS/pull/2)의 최초 비교표를 현재
+구현 기준으로 갱신했다:
+
+| 항목 | SimpleRCS | RCS (원본) | Git | DB (단순 스냅샷) |
+| :--- | :--- | :--- | :--- | :--- |
+| 저장 단위 | 단일 파일(스트림) | 단일 파일(`*,v`) | 객체 DB(`.git`) + 작업 트리 | DB 레코드(Row) |
+| 델타 방향 | 역방향 델타(Head=전체 텍스트) | 역방향 델타(Head=전체 텍스트) | 스냅샷(패킹 시 델타 생성) | 전체 복사(델타 없음) |
+| 저장 구조 | Append 위주(꼬리 덮어쓰기 + append) | 헤더 갱신 + 삽입 | 콘텐츠 주소 기반 저장소 | 새 행 삽입 |
+| I/O 패턴 | 효율적인 꼬리 쓰기, HEAD 조회는 재읽기 없는 단일 패스 백워드 스캔 | 랜덤 쓰기(헤더/본문) | 많은 작은 파일 / packfile | DB 트랜잭션 |
+| 콘텐츠 종류 | 텍스트(RCS diff)와 바이너리(BSDIFF40 호환)를 같은 파일 포맷으로 지원 | 텍스트 전용(바이너리는 별도 인코딩 필요) | 모든 타입(blob 기반) | 모든 타입(컬럼 타입) |
+| 무결성 | v2: 블록별 해시 체인 + 선택적 다중 서명자 GPG 서명 | 없음 | 콘텐츠 주소 기반(객체 SHA-1/256) | DB에 따라 다름 |
+| 중간 스냅샷 | 커밋별 선택 가능(`snapshot=True`) | 미지원 | 해당 없음(모든 커밋이 이미 완전한 스냅샷 객체) | 해당 없음 |
+| HEAD 조회 | **O(1)**, 단일 패스(끝에서부터 읽기) | O(1)(처음부터 읽기) | O(1)(ref → commit → tree) | O(1)(ID로 select) |
+| 히스토리 조회 | **O(k)**, 백워드 스캔(k = HEAD로부터의 거리) | O(N) 순방향 스캔 | O(log N) DAG 순회 | O(1)(limit으로 select) |
+| Diff 엔진 | 그리디 해시 매칭(`StreamSequenceMatcher`, O(N)); Cython 가속 Myers SES/DMP는 벤치마크용으로 별도 제공 | 표준 `diff` | `xdiff`(Myers 기반) | 해당 없음 |
+| 복잡도 | 낮음(단일 클래스, 객체 그래프 없음) | 중간(전용 문법) | 높음(복잡한 객체 모델) | 낮음(SQL) |
+
+**Diff 엔진 관련 참고:** `commit()`은 import 시점에 텍스트 diff
+백엔드를 결정한다. Cython Myers 매처가 컴파일된 경우 — C 툴체인이
+있는 환경에서는 설치 시 자동으로 빌드된다 — 그걸 사용해 최단 편집
+스크립트를 얻고, 없으면 `StreamSequenceMatcher`(최소 편집 거리보다 속도를
+우선하는 그리디 O(N) 해시 매칭)로 폴백한다. 어느 쪽이든 설치는 성공하고
+기존 이력도 그대로 읽힌다 — 블록 해시는 저장된 델타 바이트가 아니라
+논리적 내용을 덮기 때문이다.
+
+`SIMPLE_RCS_MATCHER`로 백엔드를 직접 지정할 수 있다 — `dmp_cython`,
+`ses_cython`, `stream`, `dmp_py`, `ses_py`. 이름은 `tools/bench_diff.py`가
+출력하는 id와 같아서, 벤치를 돌린 뒤 승자를 그대로 고정하면 된다.
+`*_py` 백엔드는 초기 구현 레퍼런스로 비교용으로만 남겨둔 것이고,
+비유사 입력에서 O(ND) 최악을 밟아 폴백 대상이 되지는 않는다.
+
+## 사용법
+
+```python
+from simple_rcs.simple_rcs import SimpleRCS
+
+# 인메모리로 쓰거나, 경로를 넘기면 디스크에 저장됨
+rcs = SimpleRCS("my_document.srcs")
+
+v1 = rcs.commit("Hello\nWorld\n", author="alice", log="initial")
+v2 = rcs.commit("Hello\nSimpleRCS\n", author="bob", log="tweak line 2")
+
+rcs.checkout(v1)          # -> "Hello\nWorld\n"
+rcs.checkout()            # HEAD, 즉 v2
+
+rcs.log()                 # [{'ver': '1.1', 'author': 'bob', ...}, {'ver': '1.0', ...}]
+rcs.diff(v1, v2)           # 두 버전 간 unified diff
+rcs.blame()                 # HEAD의 라인별 저자/버전 귀속
+rcs.verify()               # v2 해시 체인 검증, True/False 반환
+
+# 바이너리 콘텐츠도 동일하게 동작
+rcs.commit(open("image.png", "rb").read(), author="alice")
+```
+
+명령줄 도구는 `tools/`에 있다: `srcs_log.py`(히스토리/서명 목록),
+`srcs_diff.py`(버전/엔진 간 unified diff), `srcs_sign_head.py`(현재
+HEAD를 GPG로 서명), `bench_diff.py`(diff 엔진 벤치마크).
+
+## 테스트
+
+```
+uv run pytest tests/unit_tests/ -q
+```
+
+텍스트/바이너리 라운드트립, 해시 체인 검증, 스냅샷 처리, `log()`의 메타데이터
+전용 파싱 경로까지 총 61개 테스트로 커버한다.
+
+## 라이선스
+
+Apache License 2.0 — [LICENSE](LICENSE) 참고.