[Extension]: Add DUBSAR Memory

[kotnisofiane-bit]

Extension ID

dubsar

Extension Name

DUBSAR Memory

Version

0.1.4

Description

Local project memory for Spec Kit with explicit checkpoints, cross-session resume, and SHA-256 freshness for recorded specification, plan, and task references.

Author

DUBSAR

Repository URL

https://github.com/kotnisofiane-bit/dubsar-memory

Download URL

https://github.com/kotnisofiane-bit/dubsar-memory/releases/download/speckit-dubsar-v0.1.4/dubsar-memory-extension.zip

License

MIT

Homepage

https://github.com/kotnisofiane-bit/dubsar-memory

Documentation URL

https://github.com/kotnisofiane-bit/dubsar-memory/blob/main/integrations/spec-kit/dubsar-memory/README.md

Changelog URL

https://github.com/kotnisofiane-bit/dubsar-memory/blob/main/CHANGELOG.md

Required Spec Kit Version

>=0.16.4

Required Tools

• node (>=20) - required

Number of Commands

2

Number of Hooks

0

Tags

memory, continuity, checkpoints, resume, offline

Key Features

• Create the first local project memory, selected Work, and checkpoint through one atomic preview and confirmation.
• Record explicit progress, decisions, blockers, references, and the next action without running in the background.
• Resume the same bounded Work context in later Cursor, Claude Code, or Codex sessions.
• Report recorded Spec Kit references as fresh, stale, missing, or unknown using SHA-256 observation.
• Keep .specify/ and specs/ read-only; no hooks, MCP server, daemon, model call, or hidden write.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Release tested

• DUBSAR Memory 0.1.4
• Spec Kit 0.16.4
• Node.js 20 and 22 in CI on Windows and Ubuntu
• Real interactive acceptance on Windows with the cursor-agent integration
• Packaged integration coverage for claude, codex, and cursor-agent

Real project

A disposable clone of the public DUBSAR Memory repository was initialized as a real Spec Kit project. The feature 001-validate-dubsar-014-catalog-readiness was specified, recorded, and resumed from a fresh Cursor session using only the packaged release asset.

Scenarios exercised

1. Installed the official release asset with no source-tree copy and confirmed the packaged runtime was used instead of a global command.
2. Ran resume before initialization and received WORKSPACE_NOT_FOUND with no parent-memory leak and no write.
3. Created one project memory, selected Work, and first checkpoint through one digest-bound atomic bootstrap.
4. Opened a new Cursor session and recovered the exact project, Work, objective, checkpoint, next action, blockers, and reference freshness.
5. Confirmed the recorded spec.md reference was fresh; separate deterministic tests cover fresh, stale, missing, unknown, and read-only observation.
6. Ran the complete DUBSAR suite: 373 passed, 0 failed, with one documented Windows symlink skip. Boundary, runtime, and conformance gates passed.

The release archive is deterministic and published with SHA-256 55282acfd5df4f000ee75395b4eb6db68562b3fd80fe39330b67a9296435f556.

Example Usage

# Install the release asset directly
specify extension add dubsar --from https://github.com/kotnisofiane-bit/dubsar-memory/releases/download/speckit-dubsar-v0.1.4/dubsar-memory-extension.zip

# In Cursor, Claude Code, or Codex
/speckit.dubsar.resume
/speckit.dubsar.checkpoint

resume is read-only. checkpoint shows a preview and requires confirmation of the exact change_sha256 before writing .dubsar/.

Proposed Catalog Entry

{
  "dubsar": {
    "name": "DUBSAR Memory",
    "id": "dubsar",
    "description": "Local project memory for Spec Kit with explicit checkpoints, cross-session resume, and SHA-256 freshness for recorded specification, plan, and task references.",
    "author": "DUBSAR",
    "version": "0.1.4",
    "download_url": "https://github.com/kotnisofiane-bit/dubsar-memory/releases/download/speckit-dubsar-v0.1.4/dubsar-memory-extension.zip",
    "sha256": "55282acfd5df4f000ee75395b4eb6db68562b3fd80fe39330b67a9296435f556",
    "repository": "https://github.com/kotnisofiane-bit/dubsar-memory",
    "homepage": "https://github.com/kotnisofiane-bit/dubsar-memory",
    "documentation": "https://github.com/kotnisofiane-bit/dubsar-memory/blob/main/integrations/spec-kit/dubsar-memory/README.md",
    "changelog": "https://github.com/kotnisofiane-bit/dubsar-memory/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "visibility",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.16.4",
      "tools": [
        {
          "name": "node",
          "version": ">=20",
          "required": true
        }
      ]
    },
    "provides": {
      "commands": 2,
      "hooks": 0
    },
    "tags": [
      "memory",
      "continuity",
      "checkpoints",
      "resume",
      "offline"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-08-15T00:00:00Z",
    "updated_at": "2026-08-15T00:00:00Z"
  }
}

Additional Context

DUBSAR Memory deliberately complements Spec Kit rather than replacing its workflow. Spec Kit owns .specify/ and specs/; DUBSAR owns .dubsar/. The extension never edits Spec Kit documents, never ticks tasks, and never runs on a lifecycle hook.

The extension is categorized as visibility because it records and restores project state without orchestrating Spec Kit phases. Its catalog effect is read-write because the explicit checkpoint command writes local .dubsar/ memory; resume remains read-only.

The extension is packaged from a monorepo, so the download URL targets the deterministic release asset rather than the full source archive. The asset digest is included above and is also published by GitHub.

• Visual walkthrough: https://github.com/kotnisofiane-bit/dubsar-memory#spec-kit--dubsar-memory
• Release: https://github.com/kotnisofiane-bit/dubsar-memory/releases/tag/speckit-dubsar-v0.1.4
• Known limits: https://github.com/kotnisofiane-bit/dubsar-memory/blob/main/integrations/spec-kit/dubsar-memory/README.md#known-limit

No pull request to extensions/catalog.community.json has been opened. This issue is the requested submission path.