cc-session-tools 3.0.0__tar.gz → 3.2.0__tar.gz

{cc_session_tools-3.0.0/src/cc_session_tools.egg-info → cc_session_tools-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 3.0.0
+Version: 3.2.0
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)
 Author: raffishquartan
 License: MIT License
@@ -575,6 +575,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/README.md

@@ -518,6 +518,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "cc-session-tools"
-version = "3.0.0"
+version = "3.2.0"
 description = "Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)"
 readme = "README.md"
 license = { file = "LICENSE" }

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools/cli/ccmsg.py

@@ -206,8 +206,10 @@ def _cmd_list(args: argparse.Namespace) -> int:
         partition=args.partition,
         from_uuid=args.from_uuid,
     )
+    now = datetime.now(timezone.utc)
     for r in rows:
-        print(f"[{r.id}] {r.status:8} {r.to_kind}={r.to_value} · {r.subject}")
+        age = service.relative_age(r.sent_at, now)
+        print(f"[{r.id}] {r.status:8} {r.to_kind}={r.to_value} · {r.subject} · {age}")
     return 0
 
 

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools/cli/ccst.py

@@ -2921,7 +2921,16 @@ def _build_parser() -> argparse.ArgumentParser:
     pdata_schema_sub.required = True
 
     pdata_schema_add_field_parser = pdata_schema_sub.add_parser(
-        "add-field", help="Add/describe an extension-table field (idempotent)",
+        "add-field",
+        help="Add/describe an extension-table field (idempotent; re-run to edit its description)",
+        description=(
+            "Add an extension-table field, or edit an existing field's description. "
+            "Idempotent: re-running this command against a field name that already exists "
+            "updates its --description in place rather than erroring or duplicating the "
+            "column - there is no separate 'edit-description' command, this is it. "
+            "Re-running with a DIFFERENT --field TYPE than the field already has is "
+            "rejected with an error; add-field never changes an existing column's type."
+        ),
     )
     pdata_schema_add_field_parser.add_argument("--project", required=True, metavar="NAME")
     pdata_schema_add_field_parser.add_argument("--group", required=True, metavar="RECORD_GROUP")

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools/lib/doctor.py

@@ -205,6 +205,51 @@ def check_no_stale_hooks(settings: dict[str, Any]) -> list[CheckResult]:
     ]
 
 
+def check_no_stale_skill_symlinks(skills_target_dir: Path) -> list[CheckResult]:
+    """WARN for every symlink under the installed skills directory whose target no longer
+    exists - the case a bundled skill's rename or removal leaves behind
+    (``ccst skills install`` only ever creates symlinks for skills currently in the bundled
+    source; it never removes one for a name that stopped being bundled, and
+    :func:`check_skill_symlink` only checks skills that ARE still bundled, so nothing else
+    catches this). Mirrors :func:`check_no_stale_hooks`'s shape for the same underlying
+    problem (a rename/removal leaving a stale registration behind), but WARN rather than
+    FAIL: a broken skill symlink degrades a feature, it does not break every matching event
+    of a running session the way a stale hook registration does.
+
+    OK (no findings) if the directory doesn't exist yet - nothing to check, not an error."""
+    if not skills_target_dir.is_dir():
+        return [CheckResult(
+            name="skills:no-stale",
+            status=Status.OK,
+            reason="skills directory does not exist yet",
+        )]
+
+    stale = [
+        entry for entry in sorted(skills_target_dir.iterdir())
+        if entry.is_symlink() and not entry.exists()
+    ]
+
+    if not stale:
+        return [CheckResult(
+            name="skills:no-stale",
+            status=Status.OK,
+            reason="no symlinks for removed/renamed skills",
+        )]
+
+    return [
+        CheckResult(
+            name=f"skills:stale:{entry.name}",
+            status=Status.WARN,
+            reason=(
+                f"{entry} points to {os.readlink(entry)}, which no longer exists - the "
+                f"bundled skill it named was likely renamed or removed. Safe to remove: "
+                f"rm {entry}"
+            ),
+        )
+        for entry in stale
+    ]
+
+
 def check_skill_symlink(skill_name: str, skill_src: Path, skills_dir: Path) -> CheckResult:
     """Check that skills_dir/<skill_name> is a valid CCST skill symlink.
 
@@ -1031,6 +1076,11 @@ def run_all_checks(
             )
         )
 
+    # ...and the reverse direction: symlinks for skills that no longer exist (renamed/removed).
+    # Runs regardless of whether skills_source_dir resolved above - an orphaned symlink can be
+    # reported even if source discovery failed for an unrelated reason.
+    results.extend(check_no_stale_skill_symlinks(skills_target_dir))
+
     # Bundled ccsched jobs
     from cc_session_tools.lib.scheduler import bundled_jobs
 

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools/lib/messaging/service.py

@@ -116,6 +116,7 @@ class MessageRow:
     to_value: str
     from_session: str
     subject: str
+    sent_at: str
 
 
 def list_messages(
@@ -128,13 +129,15 @@ def list_messages(
     return [
         MessageRow(
             id=m.id, status=m.status, to_kind=m.to_kind, to_value=m.to_value,
-            from_session=m.from_session, subject=m.subject,
+            from_session=m.from_session, subject=m.subject, sent_at=m.sent_at,
         )
         for m in repository.list_rows(status=status, partition=partition, from_uuid=from_uuid)
     ]
 
 
-def _relative_age(sent_at: str, now: datetime) -> str:
+def relative_age(sent_at: str, now: datetime) -> str:
+    """Public: used by both this module's own digest formatting and ccmsg.py's `list`
+    output - a genuine cross-module utility, not internal-only."""
     sent = datetime.strptime(sent_at, "%Y-%m-%dT%H:%M:%SZ").replace(tzinfo=timezone.utc)
     minutes = int((now - sent).total_seconds() // 60)
     if minutes < 1:
@@ -150,7 +153,7 @@ def _relative_age(sent_at: str, now: datetime) -> str:
 def _digest_line(message: Message, now: datetime) -> str:
     return (
         f"[{message.id}] from {message.from_session} ({message.from_project}) · "
-        f"{message.subject} · {_relative_age(message.sent_at, now)}"
+        f"{message.subject} · {relative_age(message.sent_at, now)}"
     )
 
 
@@ -213,7 +216,7 @@ def _collect_receipts(ctx: SessionContext, now: datetime) -> list[str]:
         who = message.read_by_session or "a session"
         lines.append(
             f'✓ read: "{message.subject}" by {who} '
-            f"({_relative_age(message.sent_at, now)}) [{message.id}]"
+            f"({relative_age(message.sent_at, now)}) [{message.id}]"
         )
         shown.append(message.id)
     repository.mark_receipts_shown(shown)

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools/lib/pdata/repository.py

@@ -169,6 +169,14 @@ def list_extension_columns(conn: sqlite3.Connection, record_group: str) -> list[
     ]
 
 
+def _extension_column_type(conn: sqlite3.Connection, table: str, field_name: str) -> str | None:
+    """The stored SQL type of an existing extension column, or None if it doesn't exist."""
+    for r in conn.execute(f'PRAGMA table_info("{table}")'):
+        if r["name"] == field_name:
+            return str(r["type"])
+    return None
+
+
 def add_extension_column(
     conn: sqlite3.Connection,
     record_group: str,
@@ -179,16 +187,32 @@ def add_extension_column(
 ) -> bool:
     """Idempotent: creates ext_<group> if missing (backfilling existing rows — see
     ensure_extension_table), then ADD COLUMN if field_name isn't already a column (no-op if it
-    already exists — spec §5's schema add-field idempotency). Returns True iff a column was
-    actually added, False on the no-op path — a caller gating a side effect (e.g. a
-    vector-clock bump) on whether this call changed anything needs that distinction, not just
-    "did it run without erroring". Caller owns the transaction."""
+    already exists with the SAME type — spec §5's schema add-field idempotency). Returns True
+    iff a column was actually added, False on the no-op path — a caller gating a side effect
+    (e.g. a vector-clock bump) on whether this call changed anything needs that distinction,
+    not just "did it run without erroring". Caller owns the transaction.
+
+    Raises ValueError if field_name already exists with a DIFFERENT sql_type than requested -
+    rather than silently keeping the original type with no error, which is what this function
+    used to do (a rerun could look successful while dropping the type change entirely). An
+    actual column-type change is a real ALTER-TABLE-cannot-do-this rebuild, the same complexity
+    class as a primary-key change - disproportionate for this metadata-editing command; the
+    remediation text below is the deliberate manual escape hatch instead of building one."""
     naming.validate_field_name(field_name)
     normalized_type = _normalize_column_type(sql_type)
     ensure_extension_table(conn, record_group)
     table = naming.extension_table_name(record_group)
     existing = set(list_extension_columns(conn, record_group))
     if field_name in existing:
+        current_type = _extension_column_type(conn, table, field_name)
+        if current_type is not None and current_type != normalized_type:
+            raise ValueError(
+                f"field {field_name!r} in record_group {record_group!r} already has type "
+                f"{current_type!r}; you requested {normalized_type!r}. add-field never changes "
+                f"an existing column's type in place. To actually change it, drop and recreate "
+                f"the extension column by hand (this loses existing data in that column), or "
+                f"open an issue if this needs first-class support."
+            )
         return False
     if default is None:
         conn.execute(f'ALTER TABLE "{table}" ADD COLUMN "{field_name}" {normalized_type}')

cc_session_tools-3.2.0/src/cc_session_tools/skills/compact-smart/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: compact-smart
+description: Draft a compaction-preservation paragraph from the current session and hand back the exact /compact command to run - automates what the user otherwise asks for by hand ("give me a paragraph to pass to /compact"). Use when the user runs /compact-smart, or says "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session", "what should I tell compact to keep", or is about to /compact and wants to be sure nothing important gets lost.
+---
+
+# compact-smart
+
+Drafts the instructions `/compact [instructions]` should carry, then hands back the exact
+command to run. Does **not** invoke `/compact` itself - Claude Code's own docs explicitly
+exclude `/compact` from the set of built-in commands a skill can invoke, so the deliverable
+here is a ready-to-run command, not a compaction event.
+
+## Why this exists
+
+Real usage (a week of transcripts across every project) shows the user asking, by hand, for
+"a paragraph to pass to /compact" roughly 3 times for every bare `/compact` call - and
+re-explaining what counts as "relevant" nearly every time. What already survives compaction
+automatically (project-root `CLAUDE.md`, memory files, system/environment info) is re-loaded
+fresh from disk; what does **not** reliably survive is anything that only ever existed in
+the conversation itself - decisions, corrections, standing agreements, outstanding to-dos.
+A `/compact` instruction protects those for the *next* compaction only; the resulting
+summary is itself just conversation text again and can be trimmed by a *later* one - so this
+skill also refreshes the session's `WORKLOG.md`, if it has one, as a second, more durable
+safeguard.
+
+## What to draft
+
+Review the conversation so far (you already have it loaded - no need to re-read the
+transcript file from disk) and produce a paragraph covering, in this order:
+
+1. **Decisions and their rationale** - especially any point where the initial plan or
+   approach was found wrong and corrected mid-session. State the corrected approach and WHY
+   it changed, not just what the original plan was.
+2. **Concrete artifact pointers** - file paths, PR numbers, branch names, commit hashes,
+   OpenSpec change names, or anything else someone would need to go find the actual work.
+3. **Standing constraints or policies** established or confirmed during this session that
+   must carry forward (e.g. "no attribution lines in commits", "confirm before opening a
+   PR", a data-handling rule agreed mid-session). These are easy for a generic summary to
+   drop silently because they're usually stated once, early, and never repeated.
+4. **Outstanding tasks, split into two distinct groups**: what you (Claude) will do next,
+   and - separately and explicitly labeled - anything that is the *user's own* action to
+   take (e.g. "you still need to delete branch X yourself", "review the PR before merging").
+   Do not fold these two categories together.
+5. **An explicit "what happens next" statement.** Never leave this implicit.
+
+Keep it dense and concrete - file paths and specific facts, not vague summary language.
+
+## Handling `working/WORKLOG.md`
+
+Check whether the current session has one: `$CLD_SESSION_DIR/working/WORKLOG.md`.
+
+- **If it exists**: update it with the same substance as the draft above (append or rewrite
+  its "current state" section - match whatever structure the file already uses). This
+  repo's own `worklog-guard` PreCompact hook blocks a manual `/compact` if this file is more
+  than an hour stale, so refreshing it here also clears that gate for the command you're
+  about to hand back.
+- **If it does not exist**: do not create one. `ccd`/`ccr` never create a WORKLOG.md
+  automatically - it is opt-in scratch content the user or Claude may choose to keep during
+  a session, not mandatory state. Creating one here for the first time would be the skill
+  inventing a convention that has never applied to this session.
+
+## Confirmation step
+
+Show the drafted paragraph to the user before finalizing anything. Do not skip this even if
+the draft feels obviously complete - the point is to catch a miss before compaction discards
+the detail, not after. Accept:
+
+- Approval as-is, or
+- Free-form edits, or
+- An explicit exclusion ("drop the X thread, keep everything else") - a stale, unrelated
+  tangent that happened to occur in the same session is a real, recurring case; when asked,
+  remove that content from the paragraph rather than trying to talk the user out of it.
+
+This is a single review-and-edit round, not a multi-question interview - draft first, then
+let the user correct it in one pass. Asking a series of clarifying questions before drafting
+anything reintroduces exactly the friction this skill exists to remove.
+
+## Final output
+
+Once confirmed, present the exact command on its own line, ready to copy or type verbatim:
+
+```
+/compact <finalized paragraph>
+```
+
+Do not summarize what you're about to do instead of showing the literal command - the
+command itself is the deliverable.

{cc_session_tools-3.0.0/src/cc_session_tools/skills/pm-pdata-audit → cc_session_tools-3.2.0/src/cc_session_tools/skills/pm-pdata-do-audit-and-prepare-to-migrate}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: pm-pdata-audit
-description: Full consistency/completeness audit of a project's central and recordkeeping files - OneDrive sync-conflict cleanup, cross-checking every index/register/log against what it claims to describe, and a pdata-migration readiness pass. Ends by writing a readiness manifest file that the companion `pm-pdata-migrate` skill consumes to actually run the migration. Triggers on "review all my central files", "audit the project files", "check everything is up to date and consistent", "get this project ready for pdata", "/pm-pdata-audit", or any request for a thorough review/health-check of a project's index/log/register files (as opposed to a single-session wrap-up, which is pm-update-central-files). Especially relevant when a project is scheduled to migrate to pdata - this audit is the recommended prerequisite pass, since a schema design should not be built against files that still have unresolved sync-conflict duplicates or known dangling rows.
+name: pm-pdata-do-audit-and-prepare-to-migrate
+description: Full consistency/completeness audit of a project's central and recordkeeping files - OneDrive sync-conflict cleanup, cross-checking every index/register/log against what it claims to describe, and a pdata-migration readiness pass. Ends by writing a readiness manifest file that the companion `pm-pdata-do-migrate` skill consumes to actually run the migration. Triggers on "review all my central files", "audit the project files", "check everything is up to date and consistent", "get this project ready for pdata", "/pm-pdata-do-audit-and-prepare-to-migrate", or any request for a thorough review/health-check of a project's index/log/register files (as opposed to a single-session wrap-up, which is pm-update-central-files). Especially relevant when a project is scheduled to migrate to pdata - this audit is the recommended prerequisite pass, since a schema design should not be built against files that still have unresolved sync-conflict duplicates or known dangling rows.
 ---
 
 # Audit central files
@@ -11,7 +11,7 @@ description: Full consistency/completeness audit of a project's central and reco
 memory rules, register new `out/` files, and surface a handful of session-specific checkpoint
 items before the user exits.
 
-`pm-pdata-audit` is a much bigger, standalone task: a project-wide sweep of every
+`pm-pdata-do-audit-and-prepare-to-migrate` is a much bigger, standalone task: a project-wide sweep of every
 central file (indexes, logs, registers, CSVs) that could span an entire session or more, run on
 demand rather than at every session's end. Use it when the user wants the whole project's
 recordkeeping health-checked, not just today's session tidied up. It is squarely a
@@ -134,7 +134,7 @@ This file is deliberately NOT a migration plan - it's a findings list for whoeve
 `pm-pdata-schema-design` session next, so that work isn't designed against a still-messy
 substrate.
 
-## Phase 5: write the readiness manifest (for `pm-pdata-migrate` to consume)
+## Phase 5: write the readiness manifest (for `pm-pdata-do-migrate` to consume)
 
 Once the audit reaches a settled state (per your own stopping rule - typically two consecutive
 clean verification rounds, or a documented pragmatic stop), write one machine-and-human-readable
@@ -145,7 +145,7 @@ otherwise the project's own top-level docs location. Its existence and location
 recorded in the project's own instructions file (`CLAUDE.md`/`AGENTS.md`/equivalent) so a future
 session doesn't have to search for it.
 
-The manifest must have, in this order, so `pm-pdata-migrate` can parse it deterministically:
+The manifest must have, in this order, so `pm-pdata-do-migrate` can parse it deterministically:
 
 1. **Header**: audit date, session/agent identifier, and an explicit "STALE IF" note - state the
    condition that would invalidate this manifest (e.g. "stale if any of the files below have
@@ -154,7 +154,7 @@ The manifest must have, in this order, so `pm-pdata-migrate` can parse it determ
    row/entry count, last-verified-clean date, and its role (`index`, `register`, `log`,
    `narrative`, `derived-artefact`).
 3. **Per-file migration blockers**, in the exact shape `pm-pdata-schema-design` and
-   `pm-pdata-migrate` expect to consume - this is the same content this skill's own Phase 4
+   `pm-pdata-do-migrate` expect to consume - this is the same content this skill's own Phase 4
    already produces, just formalised into the manifest rather than a standalone prose report:
    inconsistent separators, unstable/non-existent natural keys, mixed date formats, multi-schema
    single files, machine-specific paths, null-value conventions that aren't real nulls.
@@ -165,7 +165,7 @@ The manifest must have, in this order, so `pm-pdata-migrate` can parse it determ
    a migration pass doesn't waste time re-flagging it or, worse, silently drops one copy.
 6. **Open decisions** - anything the audit found but explicitly did NOT resolve because it needed
    the project owner's judgement (scope calls, curation completeness, which of two forks is
-   canonical). List these plainly; `pm-pdata-migrate` must not treat an unresolved item as settled.
+   canonical). List these plainly; `pm-pdata-do-migrate` must not treat an unresolved item as settled.
 
 ## Common mistakes
 

{cc_session_tools-3.0.0/src/cc_session_tools/skills/pm-pdata-migrate → cc_session_tools-3.2.0/src/cc_session_tools/skills/pm-pdata-do-migrate}/SKILL.md

@@ -1,21 +1,21 @@
 ---
-name: pm-pdata-migrate
-description: Execute a project's actual migration from flat central/index files to a ccst pdata record store - build a migration plan, adversarially verify the plan itself, present it for the user's confirmation, then execute it and write a results file. Consumes the readiness manifest pm-pdata-audit produces if one exists, but always explores the project independently too, so it works even without that manifest. Triggers on "migrate this project to pdata", "run the pdata migration", "/pm-pdata-migrate", or any request to actually move a project's CSV/index/log files into pdata (as opposed to just auditing readiness, which is pm-pdata-audit, or designing the target schema in the abstract, which is pm-pdata-schema-design).
+name: pm-pdata-do-migrate
+description: Execute a project's actual migration from flat central/index files to a ccst pdata record store - build a migration plan, adversarially verify the plan itself, present it for the user's confirmation, then execute it and write a results file. Consumes the readiness manifest pm-pdata-do-audit-and-prepare-to-migrate produces if one exists, but always explores the project independently too, so it works even without that manifest. Triggers on "migrate this project to pdata", "run the pdata migration", "/pm-pdata-do-migrate", or any request to actually move a project's CSV/index/log files into pdata (as opposed to just auditing readiness, which is pm-pdata-do-audit-and-prepare-to-migrate, or designing the target schema in the abstract, which is pm-pdata-schema-design).
 ---
 
 # Migrate a project to pdata
 
 ## When to use this vs. the other pm-pdata-* skills
 
-- `pm-pdata-audit` - readiness audit. Finds and fixes problems in the CURRENT flat files.
+- `pm-pdata-do-audit-and-prepare-to-migrate` - readiness audit. Finds and fixes problems in the CURRENT flat files.
   Produces a readiness manifest. Does not touch pdata at all.
 - `pm-pdata-schema-design` - designs the TARGET record-group schema in the abstract (field names,
   types, groupings) before any data moves.
-- `pm-pdata-migrate` (this skill) - takes whatever schema exists (designed via the skill above,
+- `pm-pdata-do-migrate` (this skill) - takes whatever schema exists (designed via the skill above,
   or designed inline as part of this skill's own plan if no separate design session happened) and
   actually moves the data: `ccst pdata add`/`batch` calls, verification, and a results record.
 
-Run `pm-pdata-audit` first if the project hasn't been through it recently - a migration
+Run `pm-pdata-do-audit-and-prepare-to-migrate` first if the project hasn't been through it recently - a migration
 plan built against files with known unresolved duplicates or dangling rows just bakes the mess
 into pdata. This skill doesn't refuse to run without that prerequisite (see below), but it will
 re-derive the same checks itself if skipped, which costs more and finds less than a dedicated
@@ -23,7 +23,7 @@ audit pass would.
 
 ## Step 1: gather readiness information (works with or without a manifest)
 
-1. Look for a readiness manifest from `pm-pdata-audit` (check the project's own
+1. Look for a readiness manifest from `pm-pdata-do-audit-and-prepare-to-migrate` (check the project's own
    instructions file for where it said one was written, typically `analysis/pdata-readiness.md`
    or similar). If found: read it, and check its own "STALE IF" condition - if any listed file
    has been edited more recently than the manifest's audit date, treat the manifest as a starting
@@ -32,7 +32,7 @@ audit pass would.
    project's central/index/recordkeeping files: read the project's own instructions file in full,
    list every central file it documents, and for each one note its row/entry count, its apparent
    natural key (if any), and any obvious structural issue (multi-schema single files, inconsistent
-   separators, machine-specific paths) - the same categories `pm-pdata-audit` Phase 4
+   separators, machine-specific paths) - the same categories `pm-pdata-do-audit-and-prepare-to-migrate` Phase 4
    checks for. If a manifest exists, use this pass to spot-check a sample of its claims rather
    than skipping it entirely - a stale or partially-wrong manifest is worse than no manifest if
    trusted blindly.
@@ -50,7 +50,7 @@ ran):
   `filings-index`), not its filename.
 - **Natural key** - prefer a field that's already unique, stable, and won't be reassigned by a
   future session (a project-prefixed sequential id like `FIL-001` is a good sign; a per-session
-  independently-renumbered `row_id` is not - see `pm-pdata-audit`'s own warnings about
+  independently-renumbered `row_id` is not - see `pm-pdata-do-audit-and-prepare-to-migrate`'s own warnings about
   this exact failure mode, which shows up often). If nothing qualifies, mint a synthetic id
   at migration time and record the mapping.
 - **Field types and normalisation** - fix the specific blockers the manifest/your own audit
@@ -127,13 +127,13 @@ have N records instead of the source file's row count" without re-deriving the r
 
 ## Common mistakes
 
-- Refusing to run without a `pm-pdata-audit` manifest present - always fall back to your
+- Refusing to run without a `pm-pdata-do-audit-and-prepare-to-migrate` manifest present - always fall back to your
   own exploration instead; the manifest is an optimisation, not a hard dependency.
 - Trusting a present manifest without checking its staleness condition against current file
   states - a manifest from a project that's had further edits since is actively dangerous if
   taken at face value.
 - Migrating a session-relative or otherwise unstable field as if it were a durable natural key -
-  this is the single most common blocker `pm-pdata-audit` finds in practice; take its
+  this is the single most common blocker `pm-pdata-do-audit-and-prepare-to-migrate` finds in practice; take its
   warnings about this seriously rather than assuming "it looks like an id column" is enough.
 - Executing before the user has explicitly confirmed the plan summary in step 5 - a bulk pdata
   write is exactly the kind of hard-to-reverse, outward-facing action that needs confirmation

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0/src/cc_session_tools.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 3.0.0
+Version: 3.2.0
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)
 Author: raffishquartan
 License: MIT License
@@ -575,6 +575,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/cc_session_tools.egg-info/SOURCES.txt

@@ -108,6 +108,7 @@ src/cc_session_tools/prompts/pdata-migration-skills-update.md
 src/cc_session_tools/skills/analyse-cc-usage/SKILL.md
 src/cc_session_tools/skills/clean-hook-sessions/SKILL.md
 src/cc_session_tools/skills/clean-hook-sessions/scripts/clean-hook-sessions.py
+src/cc_session_tools/skills/compact-smart/SKILL.md
 src/cc_session_tools/skills/context-override/SKILL.md
 src/cc_session_tools/skills/delete-sessions/SKILL.md
 src/cc_session_tools/skills/delete-sessions/scripts/delete_sessions.py
@@ -122,9 +123,9 @@ src/cc_session_tools/skills/move-session/SKILL.md
 src/cc_session_tools/skills/move-session/hooks/sessionstart-pending-rename.sh
 src/cc_session_tools/skills/move-session/scripts/cc_session_rules.py
 src/cc_session_tools/skills/move-session/scripts/move_session.py
-src/cc_session_tools/skills/pm-pdata-audit/SKILL.md
 src/cc_session_tools/skills/pm-pdata-conflict-resolution/SKILL.md
-src/cc_session_tools/skills/pm-pdata-migrate/SKILL.md
+src/cc_session_tools/skills/pm-pdata-do-audit-and-prepare-to-migrate/SKILL.md
+src/cc_session_tools/skills/pm-pdata-do-migrate/SKILL.md
 src/cc_session_tools/skills/pm-pdata-schema-design/SKILL.md
 src/cc_session_tools/skills/pm-project-init/SKILL.md
 src/cc_session_tools/skills/pm-project-layout-reference/SKILL.md

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/src/hooks/confirm_8digit.py

@@ -11,7 +11,11 @@ checks (skill-marker exceptions short-circuit them):
 
 If all three hold and the assistant-to-user reply gap is under 30 minutes,
 the call is allowed. Otherwise the hook either prints a warning (default,
-``CCCS_ENFORCE_8DIGIT=warn``) or blocks with exit 2 (``=block``).
+``CCCS_ENFORCE_8DIGIT=warn``) or blocks with exit 2 (``=block``) - and, either
+way, pushes the same message as a Telegram notification via
+``lib.scheduler.notify.send_telegram`` (best-effort; never changes the exit
+code or stderr message on its own failure), so the block/warn reaches the
+user even when they are away from the terminal.
 
 Skill-marker exceptions live under ``~/.cache/claude/markers/`` (override with
 the ``CCCS_MARKERS_DIR`` env var) and have a 1-hour TTL based on file mtime.
@@ -31,6 +35,7 @@ import sys
 import time
 from typing import Literal
 
+from cc_session_tools.lib.scheduler.notify import send_telegram
 from hooks.markers import markers_dir
 from hooks.transcript import (
     TranscriptNotFound,
@@ -209,14 +214,13 @@ def verify(
     try:
         turns = load_transcript(session_id=session_id, cwd=cwd)
     except TranscriptNotFound as e:
-        return VerificationResult(
-            exit_code=2,
-            message=(
-                f"[8digit-block] cannot verify 8-digit confirmation for "
-                f"{tool_name}: transcript not found ({e}). Re-run from a real "
-                f"Claude Code session, or set the appropriate skill marker."
-            ),
+        message = (
+            f"[8digit-block] cannot verify 8-digit confirmation for "
+            f"{tool_name}: transcript not found ({e}). Re-run from a real "
+            f"Claude Code session, or set the appropriate skill marker."
         )
+        send_telegram(message)
+        return VerificationResult(exit_code=2, message=message)
 
     # 3. Three-part verification.
     failures: list[str] = []
@@ -251,21 +255,19 @@ def verify(
 
     detail = "; ".join(failures) if failures else "verification failed"
     if enforce == "block":
-        return VerificationResult(
-            exit_code=2,
-            message=(
-                f"[8digit-block] {tool_name}: {detail}. Generate a fresh "
-                f"8-digit code, share it as 'Respond with NNNNNNNN ...', and "
-                f"only proceed if the user replies with exactly that string."
-            ),
+        message = (
+            f"[8digit-block] {tool_name}: {detail}. Generate a fresh "
+            f"8-digit code, share it as 'Respond with NNNNNNNN ...', and "
+            f"only proceed if the user replies with exactly that string."
         )
-    return VerificationResult(
-        exit_code=0,
-        message=(
-            f"[8digit-warn] {tool_name}: {detail}. "
-            f"(Set CCCS_ENFORCE_8DIGIT=block to enforce.)"
-        ),
+        send_telegram(message)
+        return VerificationResult(exit_code=2, message=message)
+    message = (
+        f"[8digit-warn] {tool_name}: {detail}. "
+        f"(Set CCCS_ENFORCE_8DIGIT=block to enforce.)"
     )
+    send_telegram(message)
+    return VerificationResult(exit_code=0, message=message)
 
 
 def main(argv: list[str] | None = None) -> int:

{cc_session_tools-3.0.0 → cc_session_tools-3.2.0}/tests/test_ccst_bundle_discovery.py

@@ -141,12 +141,25 @@ def test_bundled_prompts_are_no_longer_placeholders():
 
 
 def test_pm_pdata_audit_and_migrate_are_bundled_skills():
-    """pm-pdata-audit and pm-pdata-migrate were built directly under ~/.claude/skills/ in an
-    earlier session - moved into this repo's bundled skills/ so ccst skills install /
-    install-everything provision them on every machine, not just the one they were authored
-    on. No registry to update - _discover_skills is a directory scan (any subdir with a
-    SKILL.md), so this test is really asserting the directories/files exist and are named
-    correctly."""
+    """pm-pdata-do-audit-and-prepare-to-migrate and pm-pdata-do-migrate (renamed from
+    pm-pdata-audit/pm-pdata-migrate in 3.1.0 for clarity) were built directly under
+    ~/.claude/skills/ in an earlier session - moved into this repo's bundled skills/ so
+    ccst skills install / install-everything provision them on every machine, not just the
+    one they were authored on. No registry to update - _discover_skills is a directory scan
+    (any subdir with a SKILL.md), so this test is really asserting the directories/files
+    exist and are named correctly."""
     discovered = {p.name for p in ccst._discover_skills(ccst._discover_source_dir())}
-    assert "pm-pdata-audit" in discovered
-    assert "pm-pdata-migrate" in discovered
+    assert "pm-pdata-do-audit-and-prepare-to-migrate" in discovered
+    assert "pm-pdata-do-migrate" in discovered
+
+
+def test_compact_smart_is_a_bundled_skill():
+    """compact-smart drafts a /compact preservation paragraph and hands back the exact
+    command to run - see openspec/changes/add-compact-smart-skill (archived) for the design.
+    Pure instruction skill, no backing script - this discovery assertion plus a frontmatter
+    sanity check is the extent of what's mechanically testable (design.md Decision 1)."""
+    skills = {p.name: p for p in ccst._discover_skills(ccst._discover_source_dir())}
+    assert "compact-smart" in skills
+    text = (skills["compact-smart"] / "SKILL.md").read_text()
+    assert text.startswith("---\nname: compact-smart\n")
+    assert "/compact-smart" in text