git-finalizer 2.0.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,383 @@
1
+ Metadata-Version: 2.4
2
+ Name: git-finalizer
3
+ Version: 2.0.0
4
+ Summary: Fail-closed Git delivery gatekeeper and toolchain compatibility manager for autonomous coding agents
5
+ License-Expression: Apache-2.0
6
+ License-File: LICENSE
7
+ Requires-Python: >=3.12, <3.15
8
+ Project-URL: Repository, https://github.com/xuanheng-tech/git-finalizer
9
+ Project-URL: Issues, https://github.com/xuanheng-tech/git-finalizer/issues
10
+ Description-Content-Type: text/markdown
11
+
12
+ # Git Finalizer
13
+
14
+ Authorization-boundary Git delivery for developers and coding agents: stage exactly the files you
15
+ name, create the commit, push only when the remote provably accepts a non-force fast-forward, and
16
+ then verify the live remote instead of trusting the push exit status.
17
+
18
+ Git Finalizer does not run tests, review code, resolve conflicts, call a model, create releases, or
19
+ decide on your behalf. It performs one Git write you explicitly authorized and reports what actually
20
+ happened in machine-readable JSON. Authorization comes from the caller: an existing task grant can
21
+ cover consecutive deliveries within its stated scope; passing tests does not create a new grant.
22
+
23
+ Current source version: **2.0.0**.
24
+
25
+ 当前版本:`2.0.0`
26
+
27
+ This is the source version. Source delivery and local installation do not imply a GitHub tag,
28
+ release or downloadable asset.
29
+
30
+ Detailed rules for unified-diff artifacts, already reviewed merges and remote synchronization are
31
+ in [docs/advanced-modes.md](docs/advanced-modes.md); exact content reviews and scanner
32
+ classifications are in [docs/content-review.md](docs/content-review.md).
33
+
34
+ ## Why it exists
35
+
36
+ Ordinary `git commit && git push` does not check whether the staged files match the reviewed scope,
37
+ whether hooks changed that content, or whether earlier unpublished commits are safe to publish.
38
+ Git Finalizer turns these into explicit gates with precise blockers, so both a human in a
39
+ terminal and an automation layer can rely on "it stopped, and here is why".
40
+
41
+ - **Explicit scope.** Files are listed after `--`; `git add .` and `git add -A` are never used.
42
+ - **Explicit authorization.** Commit-only, verify-only and publication are separate requests, and a
43
+ commit authorization is never widened into a push authorization.
44
+ - **Non-force, branch-only publication** with tag following disabled, then live remote
45
+ post-verification (`HEAD = upstream = remote OID`, `ahead/behind = 0/0`).
46
+ - **Refusals, not repairs.** Diverged remote, protected branch, staged surprises, sensitive content,
47
+ unexplained deletions, oversized binaries and unknown authority state all block instead of being
48
+ auto-resolved.
49
+ - **Compare-and-set for governed writes.** Branch retirement and lease-bound integration publication
50
+ require exact expected OIDs and re-check authoritative state under a lock before touching a ref.
51
+ - **Auditable results.** One deterministic JSON object per run with a closed classification triple,
52
+ documented in [docs/agent-contract.md](docs/agent-contract.md).
53
+ - **Narrow, explicit reviews.** Exceptions to content checks name an exact path, blob and detector;
54
+ see [docs/content-review.md](docs/content-review.md).
55
+
56
+ ## Requirements
57
+
58
+ - Git and POSIX userland utilities; zero GNU-only extension dependencies (portable across Linux and macOS). Verified baseline:
59
+ **Ubuntu 24.04 LTS** with system Git. Plan-bound retirement also requires a Controller that
60
+ advertises the public verification and execution protocols. Integration publication requires
61
+ `integration_publication_execution_version` 1 and the public locked stdio session.
62
+ - Python **3.12–3.14** (`>=3.12,<3.15`), with the standard library only (zero runtime dependencies;
63
+ `pyproject.toml` exposes `git-finalize`, `tool-skill-sync`, and `tool-temp-dir` console scripts,
64
+ while repository-root thin wrappers remain executable directly offline). Verified baseline:
65
+ **Python 3.12**, including clean installation with no optional tools
66
+ or personal configuration.
67
+ - Run as an ordinary user. Git Finalizer has no privilege escalation and no daemon, database or
68
+ plugin framework.
69
+ - Nothing else. No remote hosting service, no Worktree Controller, no Snapshot Runner, no Context
70
+ Loader, no installed Skill and no agent runtime is required for the core lifecycle. See
71
+ [Standalone contract](#standalone-contract).
72
+
73
+ Core Git commands have a 120-second deadline followed by a five-second forced-stop grace period.
74
+ A timed-out push remains uncertain and retains its local commit for explicit recovery. Content
75
+ scanning accepts at most 64 MiB per raw file or Git blob, including clean-filter output; larger
76
+ inputs fail closed without excerpts. This bounds scanner input, not arbitrary hook/filter code
77
+ or its temporary object output. Existing 5 MiB/25 MiB binary rules remain separate.
78
+
79
+ The managed production installer coordinates activation and rollback with running Finalizer
80
+ invocations through a shared execution lock. Active invocations finish before production files
81
+ are replaced; new invocations wait up to 30 seconds. Source checkouts and manual tarball installs
82
+ without that lock retain their ordinary installation behavior. The first upgrade from a version
83
+ without the reader protocol cannot protect invocations already running that older version.
84
+
85
+ ## Installation
86
+
87
+ There is no package index. Releases are published as GitHub Release assets:
88
+ each one carries `git-finalizer-<version>.tar.gz` plus a `SHA256SUMS.txt` that names it, from
89
+ <https://github.com/xuanheng-tech/git-finalizer/releases>. GitHub carries every release from `v1.5.0`
90
+ onward; earlier versions were published on the governed delivery remote described in
91
+ [docs/release-governance.md](docs/release-governance.md), so they are not listed here. Fetch both,
92
+ verify the artifact, then install it. Select an actual published release from that page and set
93
+ `GF_RELEASE_VERSION` to its version number without the `v` prefix; it can differ from the source
94
+ version above.
95
+
96
+ ```bash
97
+ GF_RELEASE_VERSION='<published-version>'
98
+ curl -fsSLO "https://github.com/xuanheng-tech/git-finalizer/releases/download/v${GF_RELEASE_VERSION}/SHA256SUMS.txt"
99
+ curl -fsSLO "https://github.com/xuanheng-tech/git-finalizer/releases/download/v${GF_RELEASE_VERSION}/git-finalizer-${GF_RELEASE_VERSION}.tar.gz"
100
+ sha256sum --check SHA256SUMS.txt
101
+ ```
102
+
103
+ From the verified tarball (keep `src/` beside the entrypoints or install as a Python tool via `uv tool install --offline "./git-finalizer-${GF_RELEASE_VERSION}"`):
104
+
105
+ ```bash
106
+ tar -xzf "git-finalizer-${GF_RELEASE_VERSION}.tar.gz"
107
+ install -d -m 0755 "$HOME/.local/share/git-finalizer" "$HOME/.local/bin"
108
+ cp -R "git-finalizer-${GF_RELEASE_VERSION}/src" "$HOME/.local/share/git-finalizer/"
109
+ cp "git-finalizer-${GF_RELEASE_VERSION}/git-finalize" \
110
+ "git-finalizer-${GF_RELEASE_VERSION}/tool-skill-sync" \
111
+ "git-finalizer-${GF_RELEASE_VERSION}/tool-temp-dir" \
112
+ "$HOME/.local/share/git-finalizer/"
113
+ ln -sf "$HOME/.local/share/git-finalizer/git-finalize" "$HOME/.local/bin/git-finalize"
114
+ export PATH="$HOME/.local/bin:$PATH"
115
+ git-finalize --version
116
+ ```
117
+
118
+ The bundle ships the pure-Python `git-finalizer` package (`pyproject.toml`, `src/git_finalizer/`),
119
+ the root executable wrappers (`git-finalize`, `tool-skill-sync`, `tool-temp-dir`), and the shared Skill.
120
+ During packaging, `docs/…` links in
121
+ the shipped Markdown files become public source links pinned to the release tag. The documentation
122
+ stays outside the tarball; checkout links remain relative.
123
+
124
+ From a checkout:
125
+
126
+ ```bash
127
+ ./git-finalize --version
128
+ ```
129
+
130
+ The package also ships `tool-skill-sync` and `tool-temp-dir`, which manage the optional shared
131
+ `git-change-delivery` Skill, multi-client links, and registered `/tmp` task directories on this machine.
132
+ They are not required to use `git-finalize`; see [docs/tool-skill-sync.md](docs/tool-skill-sync.md).
133
+
134
+ ## Quick start
135
+
136
+ Read-only validation of an explicit candidate scope (no index, HEAD, worktree, ref or remote
137
+ mutation; requires no upstream):
138
+
139
+ ```bash
140
+ git-finalize --mode verify-only --repo /absolute/path/to/repo -- src/app.py tests/test_app.py
141
+ ```
142
+
143
+ Verification checks the candidate after Git's clean filters and encoding conversion, including
144
+ its content signatures and binary size. Its temporary object store is isolated from the repository
145
+ and removed when the check finishes; hooks and commit signing remain outside verification.
146
+ If that temporary directory is unavailable, verification reports the missing temporary-write
147
+ precondition and preserves repository state. Use an executor-authorised writable temporary
148
+ directory or native channel; permission refusal must not be bypassed.
149
+
150
+ Local commit only, no remote access at all:
151
+
152
+ ```bash
153
+ git-finalize --mode commit-only --repo /absolute/path/to/repo \
154
+ --message "fix: handle empty response bodies" -- src/app.py tests/test_app.py
155
+ ```
156
+
157
+ Commit and publish, when you have authorization for both and the branch has a configured upstream:
158
+
159
+ ```bash
160
+ git-finalize --repo /absolute/path/to/repo \
161
+ --message "fix: handle empty response bodies" -- src/app.py tests/test_app.py
162
+ ```
163
+
164
+ Publish commits that already exist locally, without creating one:
165
+
166
+ ```bash
167
+ git-finalize --resume-publish <full-head-oid> --repo /absolute/path/to/repo
168
+ ```
169
+
170
+ First publication of a committed feature branch that has no upstream and no remote counterpart:
171
+
172
+ ```bash
173
+ git-finalize --publish-existing-branch <full-head-oid> --remote origin \
174
+ --remote-branch feat/example --repo /absolute/path/to/repo
175
+ ```
176
+
177
+ Ask for machine-readable output by adding `--summary` to any of the above. The result is one JSON
178
+ object with `status`, `final_phase` and `next_action` even when the run is blocked.
179
+ Content refusals and dry-run content risks include an optional `diagnostics` object identifying
180
+ the actual entrypoint and scanner by path and SHA-256, plus the detector, file, scan stage and
181
+ exact scanned byte/blob digest. Add `--diagnostics` to core `--summary` to include runtime identity
182
+ without a content finding. It never includes the matched value or a source excerpt. The existing result triple and
183
+ scanner guards are unchanged; see [the diagnostics contract](docs/agent-contract.md#metadata-only-diagnostics).
184
+
185
+ ## Modes
186
+
187
+ | Goal | Interface | Touches the remote |
188
+ | --- | --- | --- |
189
+ | Validate only | `--mode verify-only` | no |
190
+ | One local commit only | `--mode commit-only` | no |
191
+ | Root commit in an unborn repository, local only | `--initial-commit-only` | no |
192
+ | Commit and publish (default) | no `--mode` | yes, non-force |
193
+ | First publication of an unborn repository into an empty remote | `--initial-publish` | yes |
194
+ | First publication of a new branch while creating the commit | `--initial-branch-publish` | yes |
195
+ | Publish existing commits on a branch with upstream | `--resume-publish <oid>` | yes |
196
+ | First publication of an existing clean branch | `--publish-existing-branch <oid>` | yes |
197
+ | Publish existing history into a verified-empty repository | `--publish-existing-history <oid>` | yes |
198
+ | Recover an interrupted existing-history publication | `--resume-existing-history-publish <oid>` | yes |
199
+ | Retire an integrated branch ref (local / remote), compare-and-set | `--retire-local-branch`, `--retire-remote-branch` | remote variant yes |
200
+ | Plan or create one empty Gitea repository | `--repo-plan`, `--repo-ensure` | repository API only, never commit/push |
201
+
202
+ The complete per-mode preconditions, guarantees and recovery rules are in
203
+ [docs/cli-guide.zh.md](docs/cli-guide.zh.md) (中文) and in
204
+ [`tool_cli_contract.json`](tool_cli_contract.json), which is the machine-readable public CLI
205
+ contract (`contract_version` 10).
206
+
207
+ ## Agent and automation usage
208
+
209
+ `--summary` emits a single deterministic JSON object per run. Classify on the
210
+ `(final_phase, status, next_action)` triple; `reason` is human-oriented prose that may be localized
211
+ and is truncated with the omitted character count reported separately. Exit codes are `0` for
212
+ success and `1` for everything else on the bash-owned commands.
213
+
214
+ - Full vocabulary tables, exit-code mapping and real captured examples:
215
+ [docs/agent-contract.md](docs/agent-contract.md)
216
+ - Optional-integration blockers and the adapter boundary matrix:
217
+ [docs/integration-boundaries.md](docs/integration-boundaries.md)
218
+ - Which operation class needs which approval, and who asks the human:
219
+ [docs/authorization-boundary.md](docs/authorization-boundary.md)
220
+ - Work deferred on purpose, each entry with the condition that unblocks it:
221
+ [docs/maintenance-backlog.md](docs/maintenance-backlog.md)
222
+
223
+ Never upgrade a result. A `push.result` of `uncertain` means "not confirmed", not "failed, try
224
+ harder": re-inspect the remote with a resume interface rather than force-pushing.
225
+
226
+ ## Optional integrations
227
+
228
+ Every integration below is request-triggered. None of them is a runtime dependency, and a missing
229
+ dependency produces a precise blocker instead of a degraded success. Worktree Controller in
230
+ particular is **optional**: ordinary commit and publication work needs only Bash, Git and Python.
231
+
232
+ | Integration | Enabled by | Without it |
233
+ | --- | --- | --- |
234
+ | Worktree Controller governance (branch retirement, integration publication lease, reviewed sensitive-source linkage) | `--retire-*`, `--publish-integration-candidate`, `--reviewed-sensitive-source` | exact blocker, fail closed |
235
+ | Snapshot Runner evidence binding (reads through `snapshot-runner read` on `PATH`) | `--initial-publish --snapshot <id>` | evidence-required blocker |
236
+ | Gitea repository bootstrap | `--repo-plan`, `--repo-ensure` with an explicit `--gitea-url` | usage error; there is no default host |
237
+ | Context Loader | not used at runtime — the CLI never invokes it | nothing |
238
+ | Shared `git-change-delivery` Skill | optional agent workflow documentation and helpers | not a dependency and not an authorization source |
239
+
240
+ Each integration's knowledge of another project's layout lives only in the adapter modules
241
+ under `src/git_finalizer/` that carry a single `# GF-INTEGRATION-ADAPTER` marker per file.
242
+ That confinement is machine-checked by `tests/test_integration_boundaries.sh`.
243
+
244
+ ## Coding agents
245
+
246
+ The CLI uses the same arguments and JSON results for every caller; it does not inspect a model
247
+ provider, an agent's private session state or its approval settings. A shell-capable agent can use
248
+ the standalone lifecycle without the optional four-tool workflow.
249
+
250
+ For Skills, [Codex discovers `.agents/skills`](https://developers.openai.com/codex/skills), while
251
+ [Claude Code discovers `.claude/skills`](https://code.claude.com/docs/en/skills). The shared personal
252
+ payload can be linked into each client's discovery directory; keep one source and preserve existing
253
+ links. Project instructions remain in `AGENTS.md`. This repository supplies a `CLAUDE.md`
254
+ import (`@AGENTS.md`) for older Claude clients; the [Claude memory documentation](https://code.claude.com/docs/en/memory)
255
+ describes both the import and newer native discovery. Other clients can read the same instructions
256
+ explicitly according to their own discovery rules.
257
+
258
+ `tool-skill-sync doctor` observes instruction fingerprints and pending changes. It supports
259
+ `CODEX_HOME`, `CLAUDE_CONFIG_DIR`, `--codex-home` and `--claude-home`; `--agents-root` controls the
260
+ shared payload without moving either client's configuration. A passing check cannot prove that an
261
+ already-running agent reread its context.
262
+
263
+ ## Security model
264
+
265
+ - Branch retirement refuses a protected branch name or the remote's live default branch, and
266
+ publishing a *first* branch refuses protected names; updating the upstream of the branch you
267
+ already stand on is deliberately allowed, because that is the ordinary delivery path. Two
268
+ interfaces — `--publish-existing-history` and its resume form — may target a protected branch,
269
+ only while the entire remote is proved empty, or during exact interrupted-publication recovery.
270
+ Repository creation authority and host owner/name/visibility verification belong to the caller;
271
+ Git Finalizer verifies the configured Git endpoints, empty remote and exact publication result.
272
+ Use `--repo-plan` / `--repo-ensure` for Gitea creation, or the host's authorized client for GitHub.
273
+ - Pushes are non-force with an explicit branch refspec and `--no-follow-tags`; deletions are
274
+ `--force-with-lease`-style expected-OID compare-and-set, never unconditional force operations.
275
+ - No amend, rebase, history rewrite, automatic conflict resolution, duplicate commit creation, tag
276
+ creation or tag pushing. Git Finalizer never creates or pushes tags; a release is a separate,
277
+ explicit act.
278
+ - Credentials are never accepted as arguments, printed, or stored by this tool; repository bootstrap
279
+ resolves them through your configured Git credential helper and sends them only to the endpoint you
280
+ named.
281
+ - Diff content, commit messages and Snapshot Runner artifacts are data, not instructions. If you
282
+ route them to an agent, treat them as untrusted input.
283
+ - Pending merge, cherry-pick, revert, rebase, sequencer or bisect state blocks commit lifecycle
284
+ operations. Hooks remain enabled; a created commit must match the checked index tree and parent
285
+ before publication. Hook failures preserve any commit already created and report its OID.
286
+ - Publication checks earlier local commits that are absent from the target remote, as well as the
287
+ newly staged files. Content signatures are heuristic checks, including quoted JSON assignments;
288
+ they are not a guarantee that every secret format can be detected.
289
+
290
+ Please report security issues as described in [SECURITY.md](SECURITY.md).
291
+
292
+ ## Standalone contract
293
+
294
+ The core lifecycle (verify, commit, publish, resume and initial series) runs against an ordinary
295
+ repository with no governance tooling, no sibling tools, no installed Skill and no private hosting
296
+ configuration. `tests/test_standalone_operations.sh` proves this in a minimal `HOME`/`PATH`
297
+ environment, and asserts the mirror property as well: governed requests still fail closed with their
298
+ precise blockers and zero mutation in that environment.
299
+
300
+ ## Development and releases
301
+
302
+ ```bash
303
+ just check # shell suites, unit tests, Skill validation, contract check
304
+ just lint # shellcheck over the bash entrypoint, scripts and test harness
305
+ just release-check # required before tagging; lint and checks with real Controller and Runner
306
+ bash tests/run.sh # shell test suites alone
307
+ ```
308
+
309
+ `just check` ends with a PASS/SKIP/FAIL table, including reasons for each skipped group or unit test.
310
+ Optional real-Controller retirement tests and real Snapshot Runner evidence tests are reported as
311
+ SKIP when `worktree-controller` or `snapshot-runner` is absent from `PATH` (the Runner suite also
312
+ skips as root, which Snapshot Runner refuses). A green check proves the listed executed groups passed; it does not imply skipped
313
+ integrations ran. Any executed group failure keeps the check nonzero and stops later groups.
314
+ Before creating a release tag, maintainers run `just release-check` in the clean candidate checkout.
315
+ It requires exactly one executed PASS result from each of the real-Controller retirement suite and
316
+ the real Snapshot Runner evidence suite; missing, skipped, duplicated or failed results stop release
317
+ preparation. Ordinary and hosted `just check`
318
+ keep the standalone contract and optional SKIP behavior.
319
+
320
+ Contributing guidance, including the hash-bound file rules you must respect when changing the
321
+ contract or the Skill payload: [CONTRIBUTING.md](CONTRIBUTING.md).
322
+
323
+ Version-relevant work updates, in one preparation batch: the `git-finalize` `VERSION`, the companion
324
+ `VERSION` literals, the two current-release declarations above, `tool_version` in
325
+ `tool_cli_contract.json` and `tool_skill_manifest.json`, and the matching `CHANGELOG.md` section.
326
+ Different gates own different parts of that list: `scripts/release.py preflight <tag>` binds the
327
+ version literals, the contract digest and the Skill-payload pins, while `just check` binds the README
328
+ declarations and the presence of the `CHANGELOG.md` section, which the release job then extracts as
329
+ the release notes. [docs/release-governance.md](docs/release-governance.md) is the authoritative
330
+ list. `CHANGELOG.md` is the authoritative record and the source of release notes. **Merging to the
331
+ default branch is not a release**: a release happens only when a separately created annotated tag is
332
+ pushed, which triggers the release workflow. That workflow re-verifies the version batch, builds a
333
+ deterministic tarball, rebuilds it to prove byte-identical output, checks the file set against the
334
+ installation contract, and publishes the artifact with `SHA256SUMS.txt`.
335
+
336
+ `just check` deliberately needs only Bash, Git, Python and `just`, so a clean clone runs the
337
+ contract gate without extra tooling; `just lint` (shellcheck) is a separate CI step. Both hosts —
338
+ Gitea Actions (`.gitea/workflows/`) and GitHub Actions (`.github/workflows/`) — run the same gates
339
+ and the same build recipe through `scripts/release.py`. Each quality job also runs
340
+ `tests/test_clean_install.py` with Python 3.11 and 3.12, a restricted `PATH` and an empty user
341
+ configuration. It installs only the CLI and companions from a verified source-built bundle,
342
+ checks commit/publish/resume, and distinguishes unavailable temporary storage from filter failure.
343
+
344
+ Before a GitHub release, `scripts/release.py publication-status <tag> --remote github` observes
345
+ the explicit host and reports whether to prepare, inspect an interrupted tag/draft, or verify an
346
+ existing release. It requires the existing authorised `gh` client; core CLI use does not. Recovery
347
+ states and the independent source-digest check are in the release runbook below.
348
+
349
+ **By default a version is published on exactly one host.** An explicitly authorised mirror uses the same
350
+ candidate and annotated tag, independent builds and verified cross-host digest equality.
351
+ GitHub is the public distribution entry
352
+ (release notes, tarball, checksums); Gitea is the governed delivery remote and holds the
353
+ `v0.4.0` – `v1.4.0` release record. Trigger rules, permissions, cross-host artifact parity, and the
354
+ step-by-step first-public-release runbook are in
355
+ [docs/release-governance.md](docs/release-governance.md).
356
+
357
+ ## Support
358
+
359
+ - **Supported:** the standalone CLI on Linux/POSIX — Bash, Git and Python 3 with the standard
360
+ library only, verified on Ubuntu 24.04 LTS — and the machine-readable result contract described in
361
+ [docs/agent-contract.md](docs/agent-contract.md). Only the latest stable release receives fixes.
362
+ - **Supported as opt-in, not as an upstream promise:** Worktree Controller governance, Snapshot
363
+ Runner evidence binding, Gitea repository bootstrap and the review-file contracts. Git Finalizer
364
+ guarantees that a missing, unreadable or drifted external authority produces a precise blocker and
365
+ zero mutation; it does not guarantee that an unpublished or still-moving external contract keeps
366
+ working, and it will not weaken its own gates to accommodate one.
367
+ - **Not supported:** Windows, `file://` or non-HTTP(S) hosting endpoints, destructive Git
368
+ operations (force push, amend, rebase, history rewrite, tag creation), and any workflow that
369
+ requires the tool to infer authorization it was not given.
370
+ - **Not a security boundary:** the tool executes Git as your own user. Treat repository content,
371
+ diffs and captured evidence as untrusted input. See [SECURITY.md](SECURITY.md).
372
+
373
+ ## License
374
+
375
+ Apache License 2.0. See [LICENSE](LICENSE).
376
+
377
+
378
+ ## Acknowledgements
379
+
380
+ Built and hardened through real production delivery use, with adversarial review before every
381
+ release decision. Git Finalizer belongs to a three-tool family — Snapshot Runner (read-only
382
+ repository evidence) and Context Loader (deterministic repository context) — each with its own
383
+ repository; Git Finalizer depends on neither to work.
@@ -0,0 +1,30 @@
1
+ git_finalizer/__init__.py,sha256=nKN1sMGCRDwh7EHwHatNeo6cKzCB72XjAccvQHPR7uI,207
2
+ git_finalizer/delivery/__init__.py,sha256=hRJmxW5t7CapFPqMl3w9dcnATBSiBfFgCdFpF8YTZgk,81
3
+ git_finalizer/delivery/cli.py,sha256=hDu9zBZOXbPsthIwiYBerWNUHJeG6NiOrNvO5NUdnkc,7442
4
+ git_finalizer/delivery/content_scan.py,sha256=567_wd1mCJF94Un5wK7BPNRpkXWJ5C3-39ujRmubzZ4,21063
5
+ git_finalizer/delivery/engine.py,sha256=TA4_KEG8C_HiSWNrqfX_lgTlFu5CmW4vG99twW-rq0o,118305
6
+ git_finalizer/delivery/integration_publish.py,sha256=3LIiz136zlc0f31aGy9QSnrSS6duVYgpCFltYGadg-4,21878
7
+ git_finalizer/delivery/parser.py,sha256=9k7428fQnKWSN1ruzTsjFR6r1X43QpkfQiWbqsFMQDM,24705
8
+ git_finalizer/delivery/patch_check.py,sha256=WN-2q-4seG7HJ4wXbR1bqSwU3TyegmwIcYsqALHOvG8,5353
9
+ git_finalizer/delivery/policy.py,sha256=yUg27elOj_4fu20jl3_NuPWtav6UmB7seAGKM0Bpu-w,11372
10
+ git_finalizer/delivery/repo_bootstrap.py,sha256=qP48YUNwIKVZYN4DiU1DnXKzFH0JqeBuqz1iTnfkd6g,24765
11
+ git_finalizer/delivery/repo_state.py,sha256=uuRJwuZpL79CadzjxsDSIfZh3Z2ksCKWoHiUDNhs7mI,25070
12
+ git_finalizer/delivery/retirement_plan.py,sha256=2RwRSgzdXy9NXSRfJRqf-ss_51AZgsQvRls-msCWuwY,30486
13
+ git_finalizer/delivery/runtime.py,sha256=vjWSj82dB7zNO07r2fwF3kK_LQK5uK7BTYWk2nepKag,22142
14
+ git_finalizer/delivery/scanners.py,sha256=YB7CHk04XbajzbmMmMCTKI-ftAirv3wlSBBTXZADynE,12941
15
+ git_finalizer/delivery/snapshot_verify.py,sha256=_6OpQ2q4PPN5eBq9Z3kUbsVfQCsYxiHiKv5YPo0MtRw,16353
16
+ git_finalizer/delivery/source_review.py,sha256=esizottzHEDXytxIB61kKB1gTQTyiOLg7s-BFbI-CqY,16614
17
+ git_finalizer/delivery/trailers.py,sha256=l5xmaxBc_vYeuZKvAUWO9YT5wjOdT70peGtU5isTLaI,5555
18
+ git_finalizer/delivery/validation.py,sha256=uU8V1xBkOGvozmNCPP83nsHzEPAmw-k-NDkSbobbpKg,50828
19
+ git_finalizer/errors.py,sha256=w0jQVxOCJKDQZfRudwqiV7YmNsLQPsjEyYRCwHqG2EM,4270
20
+ git_finalizer/git_io.py,sha256=Eu8IzWZw-bbYldJpI42wMLXp9WiODvgz9NnQL-4n11c,9520
21
+ git_finalizer/json_io.py,sha256=PP5FnDqgq0TdG_ghALmCH3Jk5v6MD8XyqISG0EPpPU4,1760
22
+ git_finalizer/toolchain/__init__.py,sha256=OxTb4k6LZXIWnrIVL2qbD1yG6KLwYU3ja1TCPK_3YZ0,99
23
+ git_finalizer/toolchain/tool_skill_sync.py,sha256=S9Q7DN1llqOQ7YXtkyTzwMnPyeZKXd-dWmtzVdklOVk,128188
24
+ git_finalizer/toolchain/tool_temp_dir.py,sha256=l3w0h6We7zwO823Awj0BkD2Hl45-jjT3ODX_7HN4bno,41917
25
+ git_finalizer/toolchain/workflow_health.py,sha256=-9AslcdkZxkjh1Yw-D0wzk0nDCWwtZwUvuiuSm7WuzY,22689
26
+ git_finalizer-2.0.0.dist-info/licenses/LICENSE,sha256=tcX_O4ZlirSJi6RjhD_xGS28x8uSwhZ4m465DFb-DRc,11321
27
+ git_finalizer-2.0.0.dist-info/WHEEL,sha256=e4_1dyBeezi8ZjfxrZ3bnVOxFDa3ksqVqH0jTHkUZ3k,81
28
+ git_finalizer-2.0.0.dist-info/entry_points.txt,sha256=n71gh0de1lJu1O7qWFcC3if-hQWGBCEeH1xI72nU7dQ,188
29
+ git_finalizer-2.0.0.dist-info/METADATA,sha256=SEcE0FDHVKvRw_zzoTRHAQS4DAG5vQ-HLIib69Ms5UQ,23677
30
+ git_finalizer-2.0.0.dist-info/RECORD,,
@@ -0,0 +1,4 @@
1
+ Wheel-Version: 1.0
2
+ Generator: uv 0.12.19
3
+ Root-Is-Purelib: true
4
+ Tag: py3-none-any
@@ -0,0 +1,5 @@
1
+ [console_scripts]
2
+ git-finalize = git_finalizer.delivery.cli:main
3
+ tool-skill-sync = git_finalizer.toolchain.tool_skill_sync:main
4
+ tool-temp-dir = git_finalizer.toolchain.tool_temp_dir:main
5
+
@@ -0,0 +1,202 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to source code, documentation source, and
28
+ configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the
44
+ purposes of this License, Derivative Works shall not include works
45
+ that remain separable from, or merely link (or bind by name) to the
46
+ interfaces of, the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright
52
+ owner or by an individual or Legal Entity authorized to submit on
53
+ behalf of the copyright owner. For the purposes of this definition,
54
+ "submitted" means any form of electronic, verbal, or written
55
+ communication sent to the Licensor or its representatives, including
56
+ but not limited to communication on electronic mailing lists, source
57
+ code control systems, and issue tracking systems that are managed by,
58
+ or on behalf of, the Licensor for the purpose of discussing and
59
+ improving the Work, but excluding communication that is conspicuously
60
+ marked or otherwise designated in writing by the copyright owner as
61
+ "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and do
118
+ not modify the License. You may add Your own attribution notices
119
+ within Derivative Works that you distribute, alongside or as an
120
+ addendum to the NOTICE text from the Work, provided that such
121
+ additional attribution notices cannot be construed as modifying
122
+ the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT
147
+ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied,
148
+ including, without limitation, any warranties or conditions of
149
+ TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor has
164
+ been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf of
172
+ any other Contributor, and only if You agree to indemnify, defend,
173
+ and hold each Contributor harmless for any liability incurred by,
174
+ or claims asserted against, such Contributor by reason of your
175
+ accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a file
186
+ or class name and description of purpose be included on the same
187
+ "printed page" as the copyright notice for easier identification.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
202
+