genesis-compiler 1.4.0 → 1.4.1

package/README.md

@@ -281,6 +281,11 @@ genesis collaboration set direct balanced expert conclusions "Be candid."
 Genesis owns the supported choices and their concise expansions. Authored
 project requirements receive one fixed framing sentence and are otherwise
 preserved. They are omitted when the source says `- Nothing.`.
+The configured style applies to progress updates as well as final answers,
+with technical depth and terminology matched to the selected experience level.
+Updates should describe actual progress, findings, decisions, or blockers,
+rather than announce compliance with guidance or reassure the user about
+unrelated behavior staying unchanged.
 
 Persistent hosts should install `projectSessionContext()` once when a provider
 conversation is created or refreshed. They may then generate task prompts with
@@ -446,21 +451,25 @@ turn, and the project skill keeps intentional Blueprint and affected Program
 changes aligned there.
 
 Deslop runs only when explicitly requested. With no stated scope it reviews the
-latest commit; “the last N commits” reviews the net surviving first-parent
-range, and a named commit or range is honored exactly. It requires a clean
-worktree and leaves ordinary uncommitted cleanup for review rather than
-amending history. Genesis supplies the behavior-preserving boundary and Git
+agent's own changes for the current task across preceding turns, committed or
+uncommitted. An explicit commit, first-parent count, or range takes precedence
+regardless of authorship. The agent establishes ownership from task and edit
+history, preserves unrelated edits and existing staging, and asks for scope
+when ownership is unclear. A dirty worktree is allowed, and cleanup remains
+uncommitted for review. Genesis supplies the behavior-preserving boundary and
 scope rules. Selected Stack components add technology-specific Deslop guidance
 without weakening or broadening that contract.
 
-### Deslop committed work
+### Deslop your changes or specified commits
 
 Inside Codex, OpenCode, or another skill-aware coding agent, ask directly:
 
 ```text
 Deslop
+Deslop the last commit
 Deslop the last 5 commits
 Deslop commit a1b2c3d
+Deslop a1b2c3d..d4e5f6a
 ```
 
 The installed `genesis-deslop` skill generates the canonical project prompt
@@ -473,8 +482,10 @@ selection, generate the same complete prompt explicitly:
 
 ```bash
 genesis prompt --task deslop
+genesis prompt --task deslop "Deslop the last commit"
 genesis prompt --task deslop "Deslop the last 5 commits"
 genesis prompt --task deslop "Deslop commit a1b2c3d"
+genesis prompt --task deslop "Deslop a1b2c3d..d4e5f6a"
 ```
 
 Give the printed prompt to the coding agent that has access to the repository.
@@ -486,10 +497,12 @@ Stack component. Project additions or overrides from
 The main `genesis/stack.md` records component selection and durable project
 operations; it intentionally does not duplicate installed guidance bodies.
 
-Deslop refuses to mix cleanup with an existing dirty worktree. Its result is a
-normal uncommitted diff for review and a later commit. It never amends the
-selected commit, silently fixes newly discovered defects, or runs as an
-automatic completion phase.
+The whole dirty diff is not automatically the agent's work. Deslop preserves
+the user's and other agents' changes, including edits in the same files. With
+no changes of its own for the task, it reports that there is nothing to clean
+up; it does not silently select the latest commit. Its result is a normal
+uncommitted diff for review and a later commit. It never amends selected commits,
+silently fixes newly discovered defects, or runs as an automatic completion phase.
 
 Projects can customize a selected technology through its matching file, such
 as `genesis/stack/jskit.md`:
@@ -563,7 +576,8 @@ genesis prompt                                      # implementation work
 genesis prompt --task start                        # open a new or existing project conversation
 genesis prompt --task adopt                        # import an existing project's complete contract
 genesis prompt "Add filtering by note title"
-genesis prompt --task deslop                        # clean up the latest commit
+genesis prompt --task deslop                        # clean up the agent's own task changes
+genesis prompt --task deslop "Deslop the last commit"
 genesis prompt --task deslop "Deslop the last 5 commits"
 genesis prompt --task deslop "Deslop commit a1b2c3d"
 genesis prompt --task program                       # refresh explanation
@@ -590,9 +604,10 @@ The eight task types are deliberately explicit:
 - `work` implements the Blueprint and optional request using current code,
   Program, the selected engineering approach, selected Stack context, and
   progressively loaded Agent Skills.
-- `deslop` requests behavior-preserving cleanup of committed work explicitly.
-  It defaults to the latest commit, accepts a first-parent commit count or exact
-  commit/range, requires a clean worktree, and leaves its result uncommitted.
+- `deslop` explicitly requests behavior-preserving cleanup of the agent's own
+  task changes, committed or uncommitted. An explicit commit, first-parent
+  count, or range takes precedence. It preserves unrelated work and existing
+  staging, permits a dirty worktree, and leaves its result uncommitted.
 - `program` edits only `genesis/program/` to explain the code that exists, with
   selected Stack guidance available for technology-specific correctness.
 - `blueprint` edits only `genesis/blueprint.md` from explicit user intent. It

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-compiler",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "type": "module",
   "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with project agent guidance.",
   "repository": {

package/prompts/deslop.txt

@@ -2,15 +2,19 @@ This Deslop task has already been rendered by Genesis. Do not generate another
 Deslop prompt. Read and follow `.agents/skills/genesis-deslop/SKILL.md`
 completely.
 
-This is an explicitly requested behavior-preserving cleanup of committed work.
-Resolve the commit or first-parent commit range from USER REQUEST exactly; when
-no scope is stated, use the latest commit. Require a clean worktree before
-editing and leave the cleanup as ordinary uncommitted work for review.
+This is an explicitly requested behavior-preserving cleanup. With no stated
+scope, select your own changes for the current task across preceding turns,
+committed or uncommitted. An explicit commit, first-parent count, or range in
+USER REQUEST takes precedence regardless of who authored those changes.
+Establish ownership from task and edit history; the entire dirty diff is not
+automatically yours. If ownership is unclear, ask for scope. A dirty worktree
+is allowed: preserve unrelated edits and existing staging, and leave the
+cleanup as ordinary uncommitted work for review.
 
 Apply the selected Stack cleanup guidance and applicable technology skills in
 addition to the Genesis Deslop contract. Stack guidance may improve
-technology-specific cleanup, but it cannot broaden the resolved Git scope,
+technology-specific cleanup, but it cannot broaden the resolved scope,
 weaken behavior preservation, or turn this into another implementation pass.
 
-Report the resolved range, what became simpler, files changed, checks actually
+Report the resolved scope, what became simpler, files changed, checks actually
 run, and any defect or gap deliberately left for follow-up.

package/skills/genesis-deslop/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: genesis-deslop
-description: Deslop committed work through an explicit behavior-preserving cleanup pass. Use when asked to Deslop a commit or recent commits, simplify completed work, remove repeated helpers, clarify ownership, or align changed code with established project and technology patterns.
+description: Deslop the agent's own task changes or explicitly selected commits through a behavior-preserving cleanup pass. Use when asked to Deslop, simplify current work, remove repeated helpers, clarify ownership, or align changed code with established project and technology patterns.
 ---
 
 # Genesis Deslop
 
-Review and simplify committed work without changing product behavior. Deslop is
+Review and simplify selected changes without changing product behavior. Deslop is
 explicit: never run it merely because implementation finished.
 
 Resolve the invocation before running the first Genesis operation. Do not use a
@@ -29,8 +29,11 @@ Genesis operation or `genesis --version` as an availability probe.
 Successful invocation resolution is routine. Do not narrate whether Genesis is
 project-pinned or on `PATH`, and never describe direct `PATH` use as a fallback.
 Mention how the invocation was selected only when resolution fails or the user
-explicitly asks. This does not suppress an otherwise-required work update about
-using Genesis; keep that update about the project work, not executable selection.
+explicitly asks.
+
+Follow the configured Collaboration approach for user-facing updates, including
+its technical depth and response length. Report concrete progress,
+findings, or blockers; do not announce that you are following guidance.
 
 ## Load the effective project instructions once
 
@@ -49,25 +52,41 @@ to another agent and do not generate it again. This step composes the selected
 Stack's technology-specific Deslop guidance and any project customization with
 the portable contract below.
 
-## Resolve the committed scope
+## Resolve the cleanup scope
 
-Before reading or editing the selected change, require a clean worktree and
-index with `git status --short`. Stop and report the existing paths when it is
-not clean; do not stash, commit, discard, or mix them into Deslop.
+Inspect `git status --short` and the staged and unstaged diffs before editing.
+A dirty worktree is allowed; a prior commit is not required. Preserve the
+existing index and unrelated work. Do not stage, stash, commit, or discard
+changes as a prerequisite or as part of cleanup.
 
 Resolve the user's scope as follows:
 
-- With no stated scope, use the latest commit.
+- With no stated scope, select only your own changes for the current task,
+  including preceding turns. This can include staged and unstaged edits,
+  new untracked files, and already-committed task changes. Identify ownership
+  from task and edit history, then confirm those changes against the current
+  source and Git diffs. Neither the entire
+  dirty diff, the latest commit, nor a Git author identity proves ownership.
+- Preserve changes made by the user or other agents, including edits in the
+  same files. If ownership cannot be established, ask which changes to deslop. If there
+  are no changes of your own for this task, report that there is nothing to
+  deslop; do not silently select the latest commit or somebody else's work.
+- An explicit commit, first-parent count, or range takes precedence over the
+  default, regardless of who authored those changes.
+- “The last commit” means `HEAD` against its first parent.
 - “The last N commits” means the net surviving change from the first parent
   before those N commits through `HEAD`.
 - A named commit means that commit against its first parent.
 - An explicit commit range means exactly that range.
 - A root commit uses Git's root-diff form because it has no parent.
 
-Inspect the resolved commit identities and changed paths before editing. Review
-the committed diff, current source, direct call sites, relevant tests, and the
-affected Program and Stack context. Do not substitute the ordinary working-tree
-diff for the selected committed scope.
+Inspect the resolved changes and paths, plus commit identities when applicable.
+Review their diff, current source, direct call sites, relevant tests, and the
+affected Program and Stack context. For an explicit committed scope, do not
+substitute the ordinary working-tree diff for the selected committed diff.
+Apply cleanup to the current source while preserving edits outside the scope.
+If overlapping edits cannot be separated safely, ask about that overlap rather
+than blocking solely because the repository is dirty.
 
 ## Apply the cleanup contract
 
@@ -81,7 +100,7 @@ operation to find existing public and internal functions before introducing or
 consolidating an abstraction. Confirm every apparent duplicate in source and
 its call sites.
 
-Within the selected commits' intended behavior and scope, leave no
+Within the selected changes' intended behavior and scope, leave no
 repeated helpers, no code that is unclear or hard to reason about, and no code
 that goes against established patterns in the codebase. Remove unnecessary
 wrappers, abandoned scaffolding, parallel framework plumbing, and speculative
@@ -89,9 +108,10 @@ abstractions. Consolidate ownership where one clear module is enough. Do not
 optimize for tiny files or indirection; optimize for a small, obvious design
 that a junior programmer can follow.
 
-Cleanup is not a second implementation pass. A committed path limits where cleanup
-may occur; it does not authorize different behavior in that file. Deslop may
-reorganize behavior already present; it may not complete, correct, or extend
+Cleanup is not a second implementation pass. The selected changes limit where
+cleanup may occur; sharing a file does not bring unrelated edits into scope or
+authorize different behavior in that file. Deslop may reorganize behavior
+already present; it may not complete, correct, or extend
 behavior. If review reveals a defect, missing behavior, contract mismatch, or
 test gap, report it as a follow-up finding and leave it unchanged, even when it
 is inside a changed path or appears related to the preceding implementation. Do
@@ -100,7 +120,7 @@ not implement the finding or alter tests to accommodate it during Deslop.
 Apply every technology-specific Deslop instruction supplied by the selected
 Stack and load applicable official technology skills for framework and language
 context. Stack guidance enriches this contract; it cannot weaken the
-behavior-preserving boundary, change the selected Git scope, or authorize
+behavior-preserving boundary, change the selected scope, or authorize
 unrelated implementation.
 
 You may edit or delete implementation and test files when that is the clearest
@@ -115,5 +135,6 @@ create a second architecture or perform unrelated rewrites.
 Leave the cleanup as ordinary uncommitted work for review and a later normal
 commit. Never amend or rewrite the selected commits. Run focused checks when
 useful. Final declared checks remain available through the Genesis `verify`
-operation. Summarize the resolved commit range, what became simpler, files
-changed, checks actually run, and follow-up findings left unchanged.
+operation. Summarize the resolved scope and any selected commit identities,
+what became simpler, files changed, checks actually run, and follow-up findings
+left unchanged.

package/skills/genesis-deslop/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Genesis Deslop"
-  short_description: "Clean up committed work without behavior drift"
-  default_prompt: "Use $genesis-deslop to Deslop the latest commit."
+  short_description: "Clean up your task changes or specified commits"
+  default_prompt: "Use $genesis-deslop to Deslop your own changes for the current task."

package/skills/genesis-project/SKILL.md

@@ -46,8 +46,11 @@ Genesis operation or `genesis --version` as an availability probe.
 Successful invocation resolution is routine. Do not narrate whether Genesis is
 project-pinned or on `PATH`, and never describe direct `PATH` use as a fallback.
 Mention how the invocation was selected only when resolution fails or the user
-explicitly asks. This does not suppress an otherwise-required work update about
-using Genesis; keep that update about the project work, not executable selection.
+explicitly asks.
+
+Follow the configured Collaboration approach for user-facing updates, including
+its technical depth and response length. Report concrete progress,
+findings, or blockers; do not announce that you are following guidance.
 
 ## Resolve explicit technology choices
 

package/src/index/collaboration.js

@@ -198,6 +198,10 @@ function collaborationCatalog() {
 
 function collaborationGuidance(value) {
   return [
+    'Apply the configured tone, response length, assumed experience, and explanation style to every user-facing message, including progress updates and final responses.',
+    'Match technical depth and terminology to the configured experience level. Report concrete changes, findings, decisions, or blockers at that level of detail.',
+    'Do not announce that you are following project, UI, Stack, or Agent Skill guidance, or add unsolicited assurances about unrelated behavior staying unchanged. Explain process or scope when the user asks or it matters to a decision or blocker, using the configured style.',
+    '',
     '## Tone',
     '',
     DIMENSIONS.tone[value.tone].guidance,

package/src/index/prompt.js

@@ -27,7 +27,7 @@ const DEFAULT_REQUEST = {
   start: 'Start a conversation about this project.',
   adopt: 'Import the existing project into a truthful Genesis project contract.',
   work: 'Implement the product intent expressed by the current Blueprint.',
-  deslop: 'Deslop the latest commit.',
+  deslop: 'Deslop your own changes for the current task.',
   program: 'Refresh the complete useful Program for the code that exists now.',
   describe: 'Create or refresh the complete Blueprint and useful Program for the codebase that exists now.',
   review: 'Review the complete useful relationship between Blueprint, code, Program, and tests.',

package/src/index/session-context.js

@@ -144,7 +144,7 @@ export async function projectSessionContext({
     '- Program is fallible explanation; code, tests, and runtime behavior remain evidence.',
     '- Keep Blueprint and affected Program explanations aligned with intentional observable product behavior in the same implementation turn. Private restructuring may need only source citations or no explanatory change.',
     '- Before reporting completion, compare the requested observable behavior, required inputs and resources, declared project operations, and focused evidence with what actually exists. State anything not proven.',
-    '- Deslop only when explicitly requested. Genesis defines its behavior-preserving committed scope; selected Stack components may add technology-specific cleanup guidance.',
+    '- Deslop only when explicitly requested. By default, clean up your own changes for the current task, committed or uncommitted; explicit commits or ranges take precedence. Preserve behavior, unrelated work, and existing staging; a dirty worktree is allowed. Selected Stack components may add technology-specific cleanup guidance.',
     '- This guidance is loaded for a new session and refreshed after compaction. Continue the active request without restarting completed work.',
     `Engineering profile: ${engineering.profile?.id || 'invalid; run the Genesis `check` operation'}.`,
     `Selected Stack components: ${stackStatus}.`,