@karthikrajkumar.kannan/get-things-done 1.0.3 → 1.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +58 -0
  2. package/package.json +6 -2
package/README.md CHANGED
@@ -24,6 +24,9 @@ npx @karthikrajkumar.kannan/get-things-done@latest
24
24
 
25
25
  **Also available as an MCP server** -- use GTD tools from Python, TypeScript, Go, Rust, or any language.
26
26
 
27
+ **Home page:** [https://github.com/karthikrajkumar/gtd](https://github.com/karthikrajkumar/gtd)
28
+ **Repository:** [https://github.com/karthikrajkumar/gtd](https://github.com/karthikrajkumar/gtd)
29
+
27
30
  </div>
28
31
 
29
32
  ---
@@ -36,6 +39,7 @@ npx @karthikrajkumar.kannan/get-things-done@latest
36
39
  - [What Makes GTD Different](#what-makes-gtd-different)
37
40
  - [Installation](#installation)
38
41
  - [MCP Server -- Use GTD as Tools from Any Language](#mcp-server----use-gtd-as-tools-from-any-language)
42
+ - [Cloud-hosted code and local access](#cloud-hosted-code-and-local-access)
39
43
  - [SDK for CI/CD](#sdk-for-cicd)
40
44
  - [Architecture](#architecture)
41
45
  - [Document Formats](#document-formats)
@@ -582,6 +586,60 @@ You should see two JSON responses: server info + list of 19 tools.
582
586
 
583
587
  ---
584
588
 
589
+ ## Cloud-hosted code and local access
590
+
591
+ GTD runs against a **project directory on the machine** where you use slash commands, the MCP server (`--project`), or the SDK. If the source of truth lives in the cloud, use one of these patterns to get (and keep) that tree locally.
592
+
593
+ ### 1. Git
594
+
595
+ Code lives in **GitHub, GitLab, Azure DevOps, Bitbucket**, or another Git host. Locally: `git clone`, then `git pull` / `git fetch` for updates; use branches and remotes as usual.
596
+
597
+ **When to use:** Default for ongoing development when the repo is the artifact.
598
+
599
+ ### 2. Remote development
600
+
601
+ **VS Code Remote-SSH**, **JetBrains Gateway**, **GitHub Codespaces** (browser or VS Code), **cloud workstations**, etc. The canonical tree may stay in the cloud while your editor connects over SSH or a vendor tunnel; some setups also mirror files to disk.
602
+
603
+ **When to use:** You want a powerful or standardized environment without maintaining it on the laptop.
604
+
605
+ ### 3. Download / export
606
+
607
+ **Release zips**, **CI artifacts**, **container images** with source, or **object storage** (S3, Azure Blob) with folder download.
608
+
609
+ **When to use:** One-off copies, releases, or generated drops rather than daily edit loops.
610
+
611
+ ### 4. Sync clients
612
+
613
+ Cloud folders synced to a local directory (Dropbox-style). Possible for files; **risky for active Git repos** (conflicts, corrupted `.git`) unless the team standardizes carefully.
614
+
615
+ **When to use:** Non-Git assets or small teams with clear rules; usually prefer Git instead.
616
+
617
+ ### 5. Private network access
618
+
619
+ Source on a **VM or file share** in a VPC: **VPN**, **ExpressRoute** / private link, **bastion + scp/rsync**, or **SMB/NFS mounts** so your machine sees the path.
620
+
621
+ **When to use:** Enterprise code that never leaves a private boundary except over approved network paths.
622
+
623
+ ### 6. API or internal portal
624
+
625
+ Internal “download project” APIs, **package registries** (npm, PyPI, NuGet, Artifactory), or portals that ship **libraries / SDKs** rather than a full app repo.
626
+
627
+ **When to use:** Consuming versioned packages; partial source compared to a full monorepo clone.
628
+
629
+ ### Summary
630
+
631
+ | Need | Typical approach |
632
+ |------|------------------|
633
+ | Full project, day-to-day | **Git** clone + pull/push |
634
+ | Edit on a managed remote machine | **Remote dev** / cloud IDE |
635
+ | Snapshot or release | **Download** / artifact / image |
636
+ | Code only inside corporate cloud | **VPN** + Git or **rsync/SSH** |
637
+ | Consume binaries or APIs | **Registry** / internal **API** |
638
+
639
+ For embedding GTD in your own app (SDK, MCP, prompts), see **[docs/CUSTOM-INTEGRATION-GUIDE.md](docs/CUSTOM-INTEGRATION-GUIDE.md)**.
640
+
641
+ ---
642
+
585
643
  ## SDK for CI/CD
586
644
 
587
645
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@karthikrajkumar.kannan/get-things-done",
3
- "version": "1.0.3",
3
+ "version": "1.0.5",
4
4
  "description": "Bidirectional spec-driven agentic framework — Forward (idea to code to deploy), Backward (code to docs), Sync (drift detection and reconciliation). The first framework that goes both ways.",
5
5
  "keywords": [
6
6
  "ai",
@@ -23,9 +23,13 @@
23
23
  ],
24
24
  "author": "GTD Contributors",
25
25
  "license": "MIT",
26
+ "homepage": "https://github.com/karthikrajkumar/gtd",
26
27
  "repository": {
27
28
  "type": "git",
28
- "url": "https://github.com/get-things-done/get-things-done"
29
+ "url": "https://github.com/karthikrajkumar/gtd.git"
30
+ },
31
+ "bugs": {
32
+ "url": "https://github.com/karthikrajkumar/gtd/issues"
29
33
  },
30
34
  "bin": {
31
35
  "get-things-done": "./bin/install.js",