hermes-task-framework 1.3.0__tar.gz → 1.5.0__tar.gz

{hermes_task_framework-1.3.0 → hermes_task_framework-1.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-task-framework
-Version: 1.3.0
+Version: 1.5.0
 Summary: Structured task management skills for Hermes Agent — task creation, decomposition, stage gates
 Project-URL: Source, https://github.com/nuffin/hermes-task-framework-pip
 Requires-Python: >=3.11

{hermes_task_framework-1.3.0 → hermes_task_framework-1.5.0}/README.md

@@ -12,12 +12,13 @@ pip install hermes-task-framework
 
 ## What's Inside
 
-6 skills bundled from [task-framework](https://github.com/nuffin/task-framework):
+The package bundles the task-framework skill library from
+[hermes-task-framework](https://github.com/nuffin/hermes-task-framework), including:
 
 | Skill | What it does |
 |-------|-------------|
 | `task-framework` | Structured task lifecycle: directory, checklist, logs, scripts |
-| `task-tracker` | Auto-update TASK.md checkboxes and TASK_MEMORY.md |
+| `task-tracker` | Auto-update TASK.md checkboxes, MEMORY.md, and CHANGELOG.md |
 | `task-timestamp-convention` | Naming rules for task directories |
 | `task-lifecycle-edge-cases` | Recover lost TASK.md from artifacts |
 | `task-lifecycle-portability` | Export/import tasks between machines |
@@ -41,7 +42,7 @@ Then in Hermes:
 > 创建一个任务来分析这个 PDF
 
 # The agent auto-detects task-framework, creates the directory,
-# writes TASK.md + TASK_MEMORY.md, and works through the checklist.
+# writes TASK.md + MEMORY.md + CHANGELOG.md, and works through the checklist.
 ```
 
 ## Task Structure
@@ -49,7 +50,8 @@ Then in Hermes:
 ```
 tasks/20260717-154154.task-framework-extract-standalone-fad328/
 ├── TASK.md              ← checklist with status + [ ] / [x]
-├── TASK_MEMORY.md        ← auto-appended decision log
+├── MEMORY.md             ← durable task context
+├── CHANGELOG.md          ← chronological decision and change log
 ├── README.md             ← goal, scope, key findings
 ├── .hermes-task.json     ← hash, outputs, dependencies
 ├── input/                ← source files (never deleted)
@@ -59,7 +61,7 @@ tasks/20260717-154154.task-framework-extract-standalone-fad328/
 ## Development
 
 ```bash
-git clone --recurse-submodules https://github.com/nuffin/hermes-task-framework.git
-cd hermes-task-framework
+git clone --recurse-submodules https://github.com/nuffin/hermes-task-framework-pip.git
+cd hermes-task-framework-pip
 pip install -e .
 ```

{hermes_task_framework-1.3.0 → hermes_task_framework-1.5.0}/hermes_task_framework/skills/task-artifact-integrity/SKILL.md

@@ -60,10 +60,23 @@ Report task hashes, roots, input/output inventories, manifest equality, context-
 
 See `references/task-root-relocation.md` for the checklist.
 
+## Symlink portability policy
+
+`symlinks` and task-scope `post-flight` apply one reusable policy:
+
+- allow only an existing relative target whose resolved path remains inside the same task root;
+- reject absolute, missing, or task-escaping targets;
+- reject a symlink at the task-root canonical files (`TASK.md`, `README.md`, `MEMORY.md`, `CHANGELOG.md`, `.hermes-task.json`);
+- reject a symlink at tasks-root generated indexes (`README.md`, `TASKS.md`).
+
+The commands are read-only and emit JSON. `post-flight` is the per-task integrity record used after task operations; it does not mutate a global task index.
+
 ## Permanent tooling
 
 ```bash
 python3 scripts/task_integrity.py audit <hash-or-dir>
+python3 scripts/task_integrity.py symlinks <hash-or-dir>
+python3 scripts/task_integrity.py post-flight <hash-or-dir>
 python3 scripts/task_integrity.py closure <hash-or-dir>
 python3 scripts/task_integrity.py manifest <hash-or-dir> --output <manifest.json>
 python3 scripts/task_integrity.py compare <source-dir> <destination-dir>

{hermes_task_framework-1.3.0 → hermes_task_framework-1.5.0}/hermes_task_framework/skills/task-artifact-integrity/scripts/task_integrity.py

@@ -13,6 +13,7 @@ from pathlib import Path
 TASK_SCRIPTS = Path(__file__).resolve().parents[2] / "task-framework" / "scripts"
 sys.path.insert(0, str(TASK_SCRIPTS))
 import task_api  # pyright: ignore[reportMissingImports]  # noqa: E402
+from task_symlink_policy import inspect_task  # pyright: ignore[reportMissingImports]  # noqa: E402
 
 CANONICAL = ("TASK.md", "README.md", "MEMORY.md", "CHANGELOG.md", ".hermes-task.json")
 RELATION_KEYS = ("dependencies", "related", "supersedes", "requires", "required_by")
@@ -93,6 +94,11 @@ def audit(identifier: str) -> dict:
     for dirname in ("input", "output", "scripts"):
         if not (root / dirname).is_dir():
             warnings.append(f"missing standard directory: {dirname}/")
+    symlinks = inspect_task(root)
+    errors.extend(
+        f"symlink policy: {entry['path']}: {entry['reason']}"
+        for entry in symlinks["rejected"]
+    )
     return {
         "task": description,
         "ok": not errors,
@@ -100,6 +106,7 @@ def audit(identifier: str) -> dict:
         "warnings": warnings,
         "subsystems": subsystems,
         "relations": relation_hashes(metadata),
+        "symlinks": symlinks,
         "manifest_entries": len(build_manifest(root)),
     }
 
@@ -123,6 +130,18 @@ def closure(identifier: str) -> dict:
     return {"root": root["hash"], "tasks": list(seen.values()), "unresolved": sorted(set(unresolved))}
 
 
+def post_flight(identifier: str) -> dict:
+    description = task_api.command_describe(identifier)
+    report = inspect_task(Path(description["path"]))
+    return {
+        "scope": "task",
+        "phase": "post-flight",
+        "task": {"hash": description["hash"], "path": description["path"]},
+        "ok": report["ok"],
+        "symlinks": report,
+    }
+
+
 def compare(source: Path, destination: Path) -> dict:
     source_manifest = build_manifest(source.resolve())
     destination_manifest = build_manifest(destination.resolve())
@@ -143,6 +162,10 @@ def main() -> int:
     audit_parser.add_argument("identifier")
     closure_parser = commands.add_parser("closure")
     closure_parser.add_argument("identifier")
+    symlinks_parser = commands.add_parser("symlinks")
+    symlinks_parser.add_argument("identifier")
+    post_flight_parser = commands.add_parser("post-flight")
+    post_flight_parser.add_argument("identifier")
     manifest_parser = commands.add_parser("manifest")
     manifest_parser.add_argument("identifier")
     manifest_parser.add_argument("--output", type=Path)
@@ -157,6 +180,13 @@ def main() -> int:
         elif args.command == "closure":
             result = closure(args.identifier)
             code = 0 if not result["unresolved"] else 1
+        elif args.command == "symlinks":
+            description = task_api.command_describe(args.identifier)
+            result = inspect_task(Path(description["path"]))
+            code = 0 if result["ok"] else 1
+        elif args.command == "post-flight":
+            result = post_flight(args.identifier)
+            code = 0 if result["ok"] else 1
         elif args.command == "manifest":
             root = Path(task_api.command_describe(args.identifier)["path"])
             result = build_manifest(root)

hermes_task_framework-1.5.0/hermes_task_framework/skills/task-cross-machine-sync/SKILL.md

@@ -0,0 +1,251 @@
+---
+author: Hermes Agent
+category: software-development
+description: Synchronize a configured task root across machines with Git while preserving task indexes and context integrity.
+license: MIT
+metadata:
+  hermes:
+    scenes: [hermes, coding, devops]
+    tags: [task-framework, git, cross-machine, synchronization, portability]
+    relations:
+    - type: depends_on
+      target: task-lifecycle-portability
+      properties: {reason: export/import remains the one-task fallback, strength: strong}
+    - type: complemented_by
+      target: task-artifact-integrity
+      properties: {reason: validates context after transport, strength: strong}
+name: task-cross-machine-sync
+platforms: [linux, macos]
+version: 2.1.0
+---
+
+# Task Cross-Machine Sync
+
+Synchronizes the configured `$HERMES_TASKS_ROOT` as a Git repository. It contains no private repository name, fixed machine role, credentials, or mandatory remote.
+
+## Configuration inputs
+
+- task root from task-framework resolution;
+- Git remote and branch supplied by the environment/user;
+- optional machine role and conflict policy supplied outside this skill;
+- optional Git LFS policy for large artifacts.
+
+## Remote execution model contract
+
+Every task that may be explicitly dispatched to another machine has one
+immutable-at-dispatch provider/model pair. Store it in canonical task metadata:
+
+```json
+{
+  "extensions": {
+    "remote_execution": {
+      "provider": "openai-codex",
+      "model": "gpt-5.6-terra-900k",
+      "provider_source": "explicit",
+      "model_source": "explicit"
+    }
+  }
+}
+```
+
+### Creation-time capture
+
+The task creation API resolves both fields once, independently but with the same
+source order:
+
+1. explicit `manage_task.py create --model <model> --provider <provider>`;
+2. Hermes launch-scoped `HERMES_MODEL` / `HERMES_INFERENCE_MODEL` and
+   `HERMES_TUI_PROVIDER` / `HERMES_INFERENCE_PROVIDER`;
+3. current profile configuration, then global configuration, `model.default`
+   and `model.provider`.
+
+The creating conversation must pass both `--model` and `--provider` when it has
+a temporary per-conversation override that is not exported into the process
+environment. Do not defer this decision until remote dispatch: the controller
+may later use a different provider/model pair.
+
+### Dispatch-time resolution
+
+An explicit dispatch provider/model pair may override the stored creation pair
+only when the controller records both values in the dispatch request. Otherwise
+dispatch uses `extensions.remote_execution.provider` and `.model`. The receipt,
+`LaunchSpec`, and result manifest must all record the same resolved pair. A
+missing provider or model is a blocked dispatch; never silently fall back to the
+executor's local provider or model defaults.
+
+The task-specific runtime overlay starts Hermes with its receipt-derived pair:
+
+```text
+hermes -p <executor-profile> -m <resolved-model> --provider <resolved-provider>
+```
+
+Generic SSH/tmux runtime remains model-agnostic and never reads task metadata.
+
+## Preconditions
+
+1. Confirm the exact task root and Git repository status.
+2. Ensure the remote/branch were explicitly configured.
+3. Regenerate `README.md` and `TASKS.md` before commit.
+4. Check for nested repositories and machine-specific artifacts.
+5. Never push unless the user explicitly requests it.
+
+## Track/ignore policy
+
+Track task metadata, context, inputs, outputs, and verification artifacts unless the task repository policy says otherwise. Ignore environment rebuild products such as `.venv/`, `node_modules/`, caches, editor files, and sync-conflict metadata. Nested external repositories require an explicit policy; do not accidentally stage their object databases.
+
+## Sync sequence
+
+1. Fetch and inspect divergence.
+2. Default to fast-forward only; stop on divergence for explicit reconciliation.
+3. Resolve append-only CHANGELOG conflicts by preserving both chronological entries.
+4. Resolve MEMORY conflicts semantically: retain current stable facts, remove stale duplicates.
+5. Run task index regeneration and directory-context verification.
+6. Commit task changes with task hash/name in the message.
+7. Push only after explicit authorization.
+
+## Fallbacks
+
+Use `task-lifecycle-portability` export/import for one-task transfer, offline movement, or when the task root is not a shared Git repository.
+
+## Permanent tooling
+
+```bash
+python3 scripts/task_git_sync.py status [--tasks-root <path>]
+python3 scripts/task_git_sync.py pull --tasks-root <path> --remote <remote> --branch <branch> --execute
+python3 scripts/task_git_sync.py push --tasks-root <path> --remote <remote> --branch <branch> --execute
+```
+
+Mutation commands `pull` and `push` refuse dirty worktrees, missing remotes/branches, absent `--execute`, non-fast-forward pulls, and pushes when the remote is ahead. These strict commands still never create commits or repositories.
+
+## Opt-in unattended checkpoint sync (Linux)
+
+The separate `sync` command is for a tasks-only Git root whose owner has authorized
+automatic commits and normal pushes. It never creates a repository, rewrites remote
+history, changes signing policy, starts an LLM, claims task completion, or installs a
+scheduler. Run it from outside the task root using an external hourly scheduler
+(for example a systemd user timer, independent of the Hermes gateway).
+
+```bash
+python3 scripts/task_git_sync.py sync --config /absolute/path/task-sync.json --execute
+```
+
+The JSON config has these exact fields (unknown fields are rejected):
+
+```json
+{
+  "tasks_root": "/absolute/path/to/tasks",
+  "remote": "origin",
+  "remote_url": "ssh://git@example.invalid/owner/tasks.git",
+  "branch": "main",
+  "node_id": "node-one",
+  "auto_push": true,
+  "cooperative_writers": true,
+  "max_blob_bytes": 10485760,
+  "command_timeout_seconds": 30,
+  "network_retries": 2
+}
+```
+
+All fields except the last three are required. `tasks_root` must resolve to the exact
+repository top-level and the current branch must be `main`. Both fetch and push URL
+lists must contain exactly the literal `remote_url`; SCP-style spellings are not
+normalized or repaired. `auto_push` and `cooperative_writers` must be JSON `true`.
+The latter is the owner's declaration that uncoordinated writers are excluded; it
+is **not evidence** that arbitrary applications have acquired a lock. No config
+or real tasks root is modified by installation of this implementation.
+
+### On-demand interactive task windows
+
+When an explicitly named task needs human GPG/MFA/login interaction on an executor,
+follow `references/on-demand-interactive-task-windows.md`. It defines the optional
+`hermes-runtime:task-<hash6>` convention. Ordinary checkpoint runs remain noninteractive
+and do not create a tmux window.
+
+### Transaction and history
+
+1. Acquire the nonblocking shared root writer lease; refuse known live Python/Hermes
+   processes whose `/proc/<pid>/cwd` is inside the task root, including idle sessions.
+   Shell CWD alone is not considered evidence of a writer. The process is never killed.
+2. Refuse interrupted merge/rebase/cherry-pick/revert and busy index operations.
+3. Snapshot the original index and then all working changes with a private index.
+   Git ignores are respected; tracked deletions are checkpointed. In an isolated
+   worktree, commit staged state first and remaining changes second. Normal `git commit`
+   honors hooks and configured signing; failure blocks sync, **never** falls back
+   unsigned. Checkpoint tree changes made by hooks also require review.
+4. Keep local `refs/task-sync/<node>-<transaction>/{before,staged,working,integrated}`.
+   Rebase actual checkpoint/user commits, not a squashed synthetic replacement.
+   Only conflicting root `README.md`/`TASKS.md` are mechanically discarded in favor
+   of the integrated version. Any task-content conflict stops for human recovery in
+   the isolated worktree; main is not put into rebase conflict.
+5. Reject absolute, missing, task-escaping, canonical-metadata, and root-index symlinks before generation; permit only an existing relative target whose resolved path stays within the same task root. Write root indexes by atomic regular-file replacement rather than opening existing targets for writing. Regenerate the root indexes **after** integration and commit only a changed tree. Each completed sync records a task-scope symlink post-flight in its transaction journal.
+   Repeated idle runs after first normalization do not create commits.
+6. Push without force. A rejected push retries bounded fetch/rebase from the original
+   checkpoint. Verify the exact remote head after push. Before promotion compare
+   the local content/index/HEAD snapshot again, check incoming ignored/untracked
+   obstructions, and use checked index/worktree transitions, never `reset --hard` or
+   `clean`. New edits cause a refusal; an already successful push may still remain
+   published when a later local promotion is refused.
+
+New/modified candidate blobs are size-limited; unchanged historical large blobs are
+not rejected. New/changed credential filenames, numbered `.git.N` backup content and
+nested gitlinks are refused. This filename denylist is **not a secret scanner**.
+Unchanged historical backups/gitlinks and ignored historical content are not scanned
+recursively. Snapshots hash tracked/eligible untracked regular files in chunks, with
+a deadline, rather than traversing ignored build trees or nested repository contents.
+
+### Writer coordination and limits
+
+`task-framework/scripts/task_write_lock.py` supplies `task_writer_lock(root)` and
+`child_lease(root)` for cooperating tools. The canonical `manage_task.cmd_*` commands,
+JSON API `command_*` functions, and direct index-generator CLI participate. The index
+subprocess receives a verified inherited lease descriptor to avoid self-deadlock.
+Imported low-level file-writing helpers, standalone todo-lifecycle operations,
+third-party plugins, editors, shell writes, and older deployed framework copies are
+**not universally covered**. They must be quiesced or explicitly wrapped in the same
+lease. An idle live Hermes task session can therefore block every hourly run until
+its owner moves/exits it; the scheduler must report that as skipped/blocked, not
+success. There is no bypass flag for the live-process guard.
+
+Git/filesystem promotion is not an atomic operation against arbitrary writers.
+Fingerprints reduce the race window but cannot eliminate edits between checking and
+writing. Do not enable automatic promotion where the cooperative-writer assumption
+cannot be enforced. Mount failures, special files, malicious hooks, or processes that
+escape their process group are outside the safe operating contract.
+
+Each Git command/network operation is bounded (default 30 seconds, maximum 60),
+with at most `network_retries + 1` push attempts (maximum 6) and an approximately
+180-second transaction budget. Timed-out Git commands kill only their owned process
+group, including ordinary SSH/GPG/hook descendants. An external systemd service
+should additionally use `TimeoutStartSec=180` and `KillMode=control-group` as the
+whole-process-tree backstop. No global process kill is used.
+
+### Recovery and deployment
+
+The shared Git common directory holds untracked `task-sync/` state: `writer.lock`,
+`journal.json` (latest state), append-only per-transaction event JSON, original index
+backup during promotion, and retained isolated recovery worktrees. Conflict,
+interrupted promotion, or dirty recovery worktree phases block later automatic runs.
+Do not delete recovery data to make a timer green. Inspect the recorded refs/index,
+resolve in the isolated worktree, and verify local and remote contents before an
+operator archives the latest journal to acknowledge recovery. Immutable event
+records and backup refs should remain available; there is no automatic retention
+pruning. Clean failed-push worktrees are removed and the next run may retry while
+checkpoint refs and event records remain.
+
+Deploy a versioned full release snapshot without overwriting existing checkout or
+remote repositories. All writers requiring coordination need the corresponding new
+writer implementation; a standalone scheduler-only update is not full coordination.
+Unattended GPG/pinentry or authentication failure is a **blocked signing/authentication
+result**, not a reason to disable signing or alter remote URLs. Report scheduler
+installation, fixture tests, real-node signing, and real-node synchronization as
+separate evidence; none implies the others.
+
+For older deployed framework revisions, a minimal adoption backport is the new
+`task_write_lock.py`, the `manage_task.py` command wrappers plus inherited-lease
+subprocess change, equivalent `task_api.py` wrappers **only where that file already
+exists**, and the index-generator lease/atomic-write safety changes. Apply that diff
+against the exact preserved deployed revision after a clean applicability check;
+do not replace unrelated receipt APIs or entire source files with newer versions.
+Revalidate that revision's own suite and an external lock-contention test before
+enabling `cooperative_writers`. Existing in-memory Python imports require session
+restart or remain unguarded; their live task CWD continues to block sync safely.

hermes_task_framework-1.5.0/hermes_task_framework/skills/task-cross-machine-sync/references/on-demand-interactive-task-windows.md

@@ -0,0 +1,33 @@
+# On-Demand Interactive Task Windows
+
+Use this convention only when an explicitly named remote task needs a human to
+complete an interactive prerequisite, such as GPG pinentry, MFA, browser login,
+or a hardware confirmation.
+
+## Creation rule
+
+Do not create an interactive window for ordinary automated work. Create or reuse
+one only after the task identifies a concrete interaction requirement.
+
+A remote runtime adapter owns SSH and tmux lifecycle. This task-framework
+reference defines task-operation requirements only; it does not create sessions
+itself and does not prescribe a role, suite, or external coordinator.
+
+## Window identity
+
+The task overlay derives one deterministic window identity from the canonical
+task hash. Reuse the existing window for the same task. Never substitute a
+generic shell window or create a second window for a different task identity.
+
+## Operator handoff
+
+1. Verify the selected executor, canonical task hash, and reason for interaction.
+2. Resolve or reuse the receipt-derived task window.
+3. Start an interactive shell or the minimal required command in that window.
+4. Tell the operator the exact SSH attach command and the exact prompt they should
+   expect. Never request, capture, or transmit a secret.
+5. After the operator completes the interaction, run a noninteractive readiness
+   probe from the same executor. For GPG, use cache-only signing so an absent cache
+   fails rather than opening an unattended pinentry.
+6. Preserve the window for task audit and later operator attachment until the task
+   reaches a terminal state or the operator explicitly asks to close it.