@garyr/pt-cli 1.1.0 → 1.3.0

package/CHANGELOG.md

@@ -7,6 +7,53 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [1.3.0] - 2026-09-08
+
+### Added
+
+- **Multi-template task deduplication**: `pt init` now deduplicates post-config tasks across templates by command+description, executing each unique task only once
+- **ID-based task selection**: Internal `_id` fields prevent key collisions when identical commands exist in multiple templates
+
+### Changed
+
+- **Aggregated security warnings**: Single security prompt for all templates (was per-template), preventing early abort when one template has dangerous commands
+- **Template attribution in UI**: Deduplicated tasks show all contributing templates (e.g., `[base-template, addon-template]`)
+
+### Fixed
+
+- Duplicate `git init` execution when multiple templates include the same post-config task
+- Security warning loop that cancelled all templates when user declined one template's post-config
+
+---
+
+## [1.2.0] - 2026-09-04
+
+### Added
+
+- **Modular multi-template initialization**: `pt init <template1> <template2> <target>` combines folders, files, variables, and post-config from multiple templates
+- **Collision handling**: Detects and reports conflicting folder names, file destinations, and variable definitions across templates
+- **Readme renaming**: Auto-renames `README.md` from each template to `README_<template>.md` to prevent overwrites
+
+### Changed
+
+- **Init command accepts multiple templates**: Space-separated template names before target directory
+- **Variable merging**: Template variables merged with collision detection and clear error messages
+
+---
+
+## [1.1.0] - 2026-09-03
+
+### Added
+
+- **Shell completions**: `pt completion <bash|zsh|fish>` generates shell completion scripts
+- **Completion install guidance**: Printed instructions for adding to shell rc files
+
+### Fixed
+
+- **Shell completions interfere with PT-GUI**: Removed auto-install behavior that broke GUI integration; completions now opt-in only
+
+---
+
 ## [1.0.0] - 2026-07-31
 
 ### 🎉 First Stable Release

package/README.md

@@ -26,7 +26,6 @@ graph LR
     RSA -. Update .-> Engine
     
     style Engine fill:#f9f,stroke:#333,stroke-width:2px,color:#000
-
 ```
 
 <!-- TOC -->
@@ -47,6 +46,12 @@ graph LR
     - [Documentation](#documentation)
     - [Development](#development)
     - [Where are the Templates?](#where-are-the-templates)
+    - [Release & API Stability](#release--api-stability)
+        - [🔒 Stability Guarantee 1.x series](#-stability-guarantee-1x-series)
+        - [📦 Versioning Policy](#-versioning-policy)
+        - [📋 What's Locked in 1.0](#-whats-locked-in-10)
+        - [📖 Migration from 0.x to 1.0](#-migration-from-0x-to-10)
+    - [Documentation](#documentation)
 
 <!-- /TOC -->
 
@@ -54,7 +59,7 @@ graph LR
 
 Traditional project templating often tightly couples logic and configuration, meaning every new template requires code changes. `pt-cli` breaks that ceiling by separating project definitions from the underlying logic.
 
-Instead of writing complex, hard-coded configuration files to scaffold new work, `pt-cli` allows you to **"learn"** from your existing project directories and turn them into  templates. It doesn't enforce a specific folder structure; it supports *your* existing patterns.
+Instead of writing complex, hard-coded configuration files to scaffold new work, `pt-cli` allows you to **learn** from your existing project directories and turn them into  templates. It doesn't enforce a specific folder structure; it supports *your* existing patterns.
 
 ## Core Benefits & Uses
 
@@ -108,8 +113,8 @@ pt learn /path/to/PROJECT
 # Learn a template from a remote repository (e.g. GitHub, Gitea, or path to tarball)
 pt learn https://github.com/garyritchie/pt_godot
 
-# Scaffold a new project from a learned template
-pt init <template_name> /path/to/NEW_PROJECT
+# Scaffold a new project from one or more learned templates
+pt init <template_name> [template_name2...] /path/to/NEW_PROJECT
 
 # List available templates and configurations
 pt config
@@ -122,7 +127,6 @@ pt add my-new-template --file my-new-template.json
 
 # Scaffold directly from a JSON file (no config registration required)
 pt init ./new-project --file my-template.json --yes
-
 ```
 
 ### Shell Completions
@@ -137,6 +141,7 @@ pt completion bash > /etc/bash_completion.d/pt
 # Zsh
 pt completion zsh > ~/.zsh/completions/_pt
 # Add to ~/.zshrc: fpath=(~/.zsh/completions $fpath)
+# autoload -U compinit && compinit
 
 # Fish
 pt completion fish > ~/.config/fish/completions/pt.fish
@@ -275,4 +280,4 @@ If you skipped intermediate 0.x versions, the auto-migration handles everything.
 * **[Security Guide](doc/security.md)** - Command validation, trusted sources, audit logging.
 * **[Testing Guide](doc/testing.md)** - Test suite structure and running tests.
 * **[Exclusions Reference](doc/exclusions.md)** - Default ignored files and custom patterns.
-* **[Variable Substitution Example](doc/variable_substitution_example.md)** - Practical examples.
+* **[Variable Substitution Example](doc/variable_substitution_example.md)** - Practical examples.

package/dist/commands/completionCommand.js

@@ -1,6 +1,4 @@
 import fs from 'fs';
-import path from 'path';
-import { fileURLToPath } from 'url';
 import YAML from 'yaml';
 import { getConfigPath } from '../config.js';
 export function getTemplatesForCompletion() {
@@ -67,8 +65,8 @@ _pt_completions() {
       ;;
     init)
       if [[ "$cur" == -* ]]; then
-        COMPREPLY=( $(compgen -W "-f --file --skip-post-config --dry-run -y --yes --vars -h --help" -- "$cur") )
-      elif [[ $cword -eq 2 ]]; then
+        COMPREPLY=( $(compgen -W "-f --file --skip-post-config --dry-run -y --yes --vars --collision --json -h --help" -- "$cur") )
+      elif [[ $cword -ge 2 ]]; then
         local templates
         templates=$(pt completion --templates 2>/dev/null)
         COMPREPLY=( $(compgen -W "$templates" -- "$cur") )
@@ -200,9 +198,10 @@ _pt() {
             '--dry-run[Show what would be created without making changes]' \\
             '(-y --yes)'{-y,--yes}'[Automatically answer yes to prompts]' \\
             '--vars=[Comma-separated key=value variables]:variables:' \\
+            '--collision=[File collision resolution strategy]:mode:(overwrite newest)' \\
+            '--json[Output result as JSON]' \\
             '(-h --help)'{-h,--help}'[display help for command]' \\
-            '1:template:_pt_templates' \\
-            '2:destPath:_files -/'
+            '*:templates:_pt_templates'
           ;;
         config)
           _arguments \\
@@ -328,6 +327,8 @@ complete -c pt -n '__fish_pt_using_command init' -l skip-post-config -d 'Skip ru
 complete -c pt -n '__fish_pt_using_command init' -l dry-run -d 'Show what would be created without making changes'
 complete -c pt -n '__fish_pt_using_command init' -s y -l yes -d 'Automatically answer yes to prompts'
 complete -c pt -n '__fish_pt_using_command init' -l vars -d 'Comma-separated key=value variables'
+complete -c pt -n '__fish_pt_using_command init' -l collision -a 'overwrite newest' -d 'File collision resolution strategy'
+complete -c pt -n '__fish_pt_using_command init' -l json -d 'Output result as JSON'
 
 # config
 complete -c pt -n '__fish_pt_using_command config' -a '(__fish_pt_templates)' -d 'Template name'
@@ -396,13 +397,3 @@ export async function completionCommand(shellArg, options) {
         process.exit(1);
     }
 }
-// Allow direct execution via tsx src/commands/completionCommand.ts <shell>
-if (process.argv[1] && fileURLToPath(import.meta.url) === path.resolve(process.argv[1])) {
-    const shell = process.argv[2];
-    if (shell === '--templates' || shell === '_templates') {
-        completionCommand(shell, { templates: true });
-    }
-    else {
-        completionCommand(shell);
-    }
-}