docs: clarify implementation commit-history policy (#40) #41

Merged
adrian.tkacz merged 1 commit from issue-40-commit-policy into develop 2026-10-03 09:30:47 +00:00
Member

Scope

Refs #40. Clarifies only .kilo/rules/30-implementation-discipline.md and .kilo/command/implement-issue.md: commit count is not an acceptance criterion; use as many small, coherent, reviewable commits as needed; remediation commits are normal; do not squash, amend, force-push, or rewrite published history merely to reduce commit count. Overall scope remains focused and coherent.

No product/runtime, AGit, routing/reviewer, dependency, or single-issue/PR semantics changed.

Evidence

  • Base (fetched develop): eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baa
  • Head: bcd30e779d0eaaf5595df2116eac3c892b09ae29
  • make check: passed; locked dependencies, Ruff format/lint, basedpyright (0 errors/warnings), import boundary, 869 tests, secret scan and whitespace checks.
  • make package-check: passed; wheel metadata/license, sdist rebuild, isolated install and CLI replay/export.
  • git diff --check eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baa HEAD and staged whitespace check: passed.
  • Full base delta inspected: only two authorized Markdown files, 8 insertions/1 deletion. Base ancestry verified; final worktree clean.
  • Configured/effective author and committer verified as Adrian Tkacz adrian.tkacz@creatidy.com; normal Git commit/push succeeded.
  • make audit not run: documentation-only change, no dependency/tooling changes.

Ready for review, not independently reviewed or approved. No reviewer sessions, merge, history rewriting, release or deployment performed. Issue remains open. No unresolved blockers.

## Scope Refs #40. Clarifies only `.kilo/rules/30-implementation-discipline.md` and `.kilo/command/implement-issue.md`: commit count is not an acceptance criterion; use as many small, coherent, reviewable commits as needed; remediation commits are normal; do not squash, amend, force-push, or rewrite published history merely to reduce commit count. Overall scope remains focused and coherent. No product/runtime, AGit, routing/reviewer, dependency, or single-issue/PR semantics changed. ## Evidence - Base (fetched develop): `eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baa` - Head: `bcd30e779d0eaaf5595df2116eac3c892b09ae29` - `make check`: passed; locked dependencies, Ruff format/lint, basedpyright (0 errors/warnings), import boundary, 869 tests, secret scan and whitespace checks. - `make package-check`: passed; wheel metadata/license, sdist rebuild, isolated install and CLI replay/export. - `git diff --check eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baa HEAD` and staged whitespace check: passed. - Full base delta inspected: only two authorized Markdown files, 8 insertions/1 deletion. Base ancestry verified; final worktree clean. - Configured/effective author and committer verified as Adrian Tkacz <adrian.tkacz@creatidy.com>; normal Git commit/push succeeded. - `make audit` not run: documentation-only change, no dependency/tooling changes. Ready for review, not independently reviewed or approved. No reviewer sessions, merge, history rewriting, release or deployment performed. Issue remains open. No unresolved blockers.
docs: clarify implementation commit-history policy (#40)
All checks were successful
ci / check (pull_request) Successful in 1m1s
bcd30e779d
adrian.tkacz deleted branch issue-40-commit-policy 2026-10-03 09:30:47 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Creatidy/creatidy-kernel!41
No description provided.