Release Git Tools 0.1.0

docs/ACCESSIBILITY.md

@@ -0,0 +1,3 @@
+# Accessibility
+
+The workbench uses semantic landmarks, headings and labelled native controls, supports keyboard operation, visible focus, reduced-width layouts, and system/light/dark themes through the Toolbox shell. Results do not rely on colour alone.

docs/ARCHITECTURE.md

@@ -0,0 +1,7 @@
+# Architecture
+
+Git Tools is a static React/Vite application wrapped in the shared Toolbox shell. `git/tools.ts` contains bounded, side-effect-free parsers and generators for each workspace. Imported content is projected into typed records and rendered through text nodes, code blocks and native controls.
+
+Patch authoring computes common prefix/suffix, then uses an LCS matrix only while its one-million-cell limit holds; larger changed middles become a bounded replace block. Hunk construction keeps selected context and records missing final newlines. Patch inspection validates observed old/new counts against every hunk header but never applies a patch.
+
+The ignore matcher models one root `.gitignore` and explains each matching rule plus ignored-parent behavior. It does not pretend to model repository index state. SemVer ranges intentionally cover common operators rather than npm's entire historical range grammar. Version 0.1 is synchronous, has no persistence or server API, and uses relative assets for nested portal paths.

docs/PRIVACY-SECURITY.md

@@ -0,0 +1,7 @@
+# Privacy and security
+
+Patch content, file paths, commit messages, ignore rules, versions, and changelogs stay in page memory. There is no telemetry, analytics, account, persistence or runtime network path. Imported paths and lines are rendered as inert text and never interpreted as HTML or shell commands.
+
+Patch inspection caps bytes, lines, files, and hunks. Authoring caps bytes and lines, and only allocates an LCS matrix below one million cells. Ignore and version candidate counts are capped. These limits reduce accidental resource exhaustion but do not make an authored patch safe to apply.
+
+Git Tools never opens a repository, runs Git, invokes a shell, follows file paths, or applies output. Review patches, ignore decisions, version policy, commit text and normalized changelogs in the target project's actual tooling before committing. Conventional Commit “valid” means structural validity under this app's documented common type set, not acceptance by a project's custom policy.