Bootstrap Python foundation and single-issue workflow #2

Merged
adrian.tkacz merged 4 commits from issue-1-bootstrap into develop 2026-10-01 20:33:52 +00:00
Member

Scope

Refs #1. Bootstrap only; no Model Intelligence product implementation or M0 proof execution.

  • Python 3.12+ uv src-layout package with shipped py.typed, existing Apache-2.0 license, no runtime dependencies and locked Ruff/basedpyright development tools.
  • Two deterministic standard-library tests for installed metadata, import and typing marker; Makefile owns final make check gates.
  • Short factual README, thin AGENTS, five scoped Kilo rules and /implement-issue and /review-pr commands.
  • Explicit owner-selected issue workflow, canonical Forgejo/Git vs MCP boundaries, isolated numbered worktrees, diagnosed retries, reuse/provenance/product boundaries and human merge gate.
  • Future A/B/C proof, temporal/provenance hypothesis and unbiased STOP/GO contract preserved in issue #1; not implemented here.

Exact Current Range

  • Recorded/fetched develop base: 033f82956bf5d56c0df0a9cf6472d11a3bf099b4
  • Previous head: b3b1b5e2adcfec222d8c09fc7602115dbc550ce5
  • Current pushed head: 3e1adc80920ea977a0d18b91167b4f9aeeb6e22d
  • Existing branch/worktree retained: issue-1-bootstrap; original delivery PR #2 remains open, targeting develop.
  • Normal additive remediation commits; commit count is not acceptance. No squash, amend, force-push or history rewrite. LICENSE unchanged; full original-base delta inspected; final checkout clean; local scratch excluded via shared .git/info/exclude.

Independent Interactive Review

The owner's current decision replaces the previous infrastructure-dependent review workflow. Any earlier operator-blocked review handoff is superseded and is not an acceptance prerequisite for this PR.

Current remediation changes only three files:

  • .kilo/command/review-pr.md: simple read-only independent review in a fresh Kilo session/context distinct from implementation. Fetch PR and linked issue through forgejo-mcp, freeze exact HEAD/base, read snapshot AGENTS/rules, inspect the entire PR and relevant source/tests/acceptance, perform safe local checks when useful, and report severity-ordered file/line findings with one verdict: APPROVE, REQUEST_CHANGES or COMMENT. Never merge or modify the reviewed branch. Changed HEAD/base invalidates review and requires a fresh whole-PR review.
  • AGENTS.md: current independent interactive review workflow; results may remain in chat and optional formal publication is not an acceptance gate.
  • .kilo/rules/20-forgejo-mcp.md: implementation authorship remains Adrian through Git; independence is a fresh review context, not a required platform identity. Forgejo MCP remains authoritative for platform operations and optional review publication.

No external reviewer service, routing infrastructure, production configuration/deployment, webhook or publisher/requester identity is required. No provider-specific infrastructure policy or automatic reviewer-subtask dispatch. A different model/provider may be used when useful.

The number-neutral commit rule remains intact. The M0 A/B/C product contract, STOP/GO, scope and acceptance requirements are unchanged. No other repository, dependency, packaging or product code changed in this remediation.

Validation

  • make check: passed locked sync, Ruff lint/format, basedpyright (0 errors/warnings/notes), two deterministic tests and staged/unstaged whitespace checks.
  • Ruby YAML.safe_load of both command frontmatters: passed, nonempty description and no subtask/agent fields.
  • Search of tracked AGENTS/rules/commands: no obsolete infrastructure-review references remain.
  • Full original-base delta, intended three-file delta, recent history and status inspected; git diff --check 033f82956bf5d56c0df0a9cf6472d11a3bf099b4..HEAD and base ancestry passed.
  • Configured/effective Git identity verified before commit; committed author/committer Adrian Tkacz <adrian.tkacz@creatidy.com>. Normal commit/push succeeded; local and canonical branch heads match; checkout clean.

Historical bootstrap validation passed uv build and isolated installed-wheel tests. Packaging is unchanged and was not rebuilt for this workflow-only remediation.

Editor command discovery remains unverified: automatic editor validator reports missing instance context. Explicit YAML parsing passed; repository runtime reload guidance remains. This does not authorize a substitute workflow.

Handoff

READY_FOR_REVIEW for exact HEAD 3e1adc80920ea977a0d18b91167b4f9aeeb6e22d by a fresh independent interactive reviewer. This implementation session has not independently reviewed or approved its own changes. Chat review is sufficient; formal Forgejo review is optional.

Keep issue #1 open and PR #2 unmerged. No merge/auto-merge, main change, release, deployment, secret output or GitHub mutation.

## Scope Refs #1. Bootstrap only; no Model Intelligence product implementation or M0 proof execution. - Python 3.12+ uv src-layout package with shipped py.typed, existing Apache-2.0 license, no runtime dependencies and locked Ruff/basedpyright development tools. - Two deterministic standard-library tests for installed metadata, import and typing marker; Makefile owns final `make check` gates. - Short factual README, thin AGENTS, five scoped Kilo rules and `/implement-issue` and `/review-pr` commands. - Explicit owner-selected issue workflow, canonical Forgejo/Git vs MCP boundaries, isolated numbered worktrees, diagnosed retries, reuse/provenance/product boundaries and human merge gate. - Future A/B/C proof, temporal/provenance hypothesis and unbiased STOP/GO contract preserved in issue #1; not implemented here. ## Exact Current Range - Recorded/fetched develop base: `033f82956bf5d56c0df0a9cf6472d11a3bf099b4` - Previous head: `b3b1b5e2adcfec222d8c09fc7602115dbc550ce5` - Current pushed head: `3e1adc80920ea977a0d18b91167b4f9aeeb6e22d` - Existing branch/worktree retained: `issue-1-bootstrap`; original delivery PR #2 remains open, targeting develop. - Normal additive remediation commits; commit count is not acceptance. No squash, amend, force-push or history rewrite. LICENSE unchanged; full original-base delta inspected; final checkout clean; local scratch excluded via shared `.git/info/exclude`. ## Independent Interactive Review The owner's current decision replaces the previous infrastructure-dependent review workflow. Any earlier operator-blocked review handoff is superseded and is not an acceptance prerequisite for this PR. Current remediation changes only three files: - `.kilo/command/review-pr.md`: simple read-only independent review in a fresh Kilo session/context distinct from implementation. Fetch PR and linked issue through forgejo-mcp, freeze exact HEAD/base, read snapshot AGENTS/rules, inspect the entire PR and relevant source/tests/acceptance, perform safe local checks when useful, and report severity-ordered file/line findings with one verdict: APPROVE, REQUEST_CHANGES or COMMENT. Never merge or modify the reviewed branch. Changed HEAD/base invalidates review and requires a fresh whole-PR review. - `AGENTS.md`: current independent interactive review workflow; results may remain in chat and optional formal publication is not an acceptance gate. - `.kilo/rules/20-forgejo-mcp.md`: implementation authorship remains Adrian through Git; independence is a fresh review context, not a required platform identity. Forgejo MCP remains authoritative for platform operations and optional review publication. No external reviewer service, routing infrastructure, production configuration/deployment, webhook or publisher/requester identity is required. No provider-specific infrastructure policy or automatic reviewer-subtask dispatch. A different model/provider may be used when useful. The number-neutral commit rule remains intact. The M0 A/B/C product contract, STOP/GO, scope and acceptance requirements are unchanged. No other repository, dependency, packaging or product code changed in this remediation. ## Validation - `make check`: passed locked sync, Ruff lint/format, basedpyright (0 errors/warnings/notes), two deterministic tests and staged/unstaged whitespace checks. - Ruby `YAML.safe_load` of both command frontmatters: passed, nonempty description and no subtask/agent fields. - Search of tracked AGENTS/rules/commands: no obsolete infrastructure-review references remain. - Full original-base delta, intended three-file delta, recent history and status inspected; `git diff --check 033f82956bf5d56c0df0a9cf6472d11a3bf099b4..HEAD` and base ancestry passed. - Configured/effective Git identity verified before commit; committed author/committer `Adrian Tkacz <adrian.tkacz@creatidy.com>`. Normal commit/push succeeded; local and canonical branch heads match; checkout clean. Historical bootstrap validation passed `uv build` and isolated installed-wheel tests. Packaging is unchanged and was not rebuilt for this workflow-only remediation. Editor command discovery remains unverified: automatic editor validator reports missing instance context. Explicit YAML parsing passed; repository runtime reload guidance remains. This does not authorize a substitute workflow. ## Handoff READY_FOR_REVIEW for exact HEAD `3e1adc80920ea977a0d18b91167b4f9aeeb6e22d` by a fresh independent interactive reviewer. This implementation session has not independently reviewed or approved its own changes. Chat review is sufficient; formal Forgejo review is optional. Keep issue #1 open and PR #2 unmerged. No merge/auto-merge, main change, release, deployment, secret output or GitHub mutation.
adrian.tkacz deleted branch issue-1-bootstrap 2026-10-01 20:33:52 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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/model-intelligence!2
No description provided.