remove ltis

Author: AnjanJ

README.md

@@ -78,7 +78,6 @@ $ zs
 zs automatically detects:
 
 - **Rails/Ruby**: Presence of `Gemfile`
-- **LTI Tools**: Rails projects with `lti` gem
 - **React**: `package.json` with react dependency
 - **Node.js**: Generic `package.json`
 - **Python**: `requirements.txt` or `pyproject.toml`

src/zs

@@ -24,7 +24,7 @@ LAST_RUN_FILE="$ZS_CONFIG_DIR/.last-run"
 # Smart detection functions
 detect_project_type() {
   if [[ -f "Gemfile" ]]; then
-    grep -q "lti" Gemfile 2>/dev/null && echo "lti" || echo "rails"
+    echo "rails"
   elif [[ -f "mix.exs" ]]; then
     echo "elixir"
   elif [[ -f "package.json" ]]; then
@@ -67,7 +67,7 @@ ensure_dependencies() {
   local project_type="$1"
 
   case "$project_type" in
-    *rails*|*lti*)
+    rails)
       if ! gem list debug -i &>/dev/null; then
         info "Installing Ruby debug support..."
         gem install debug --no-document &>/dev/null && info "Ruby debug ready"
@@ -112,7 +112,7 @@ create_debug() {
   else
     # Generate appropriate debug config
     case "$project_type" in
-      *rails*|*lti*)
+      rails)
         cat > .zed/debug.json << 'EOF'
 [
   {
@@ -213,7 +213,7 @@ task_count=$(grep -c '"label"' .zed/tasks.json 2>/dev/null || echo 0)
 
 # Single line output
 case "$project_type" in
-  rails|lti) success "Rails project ready ($task_count tasks, debugging enabled)" ;;
+  rails) success "Rails project ready ($task_count tasks, debugging enabled)" ;;
   react) success "React project ready ($task_count tasks, debugging enabled)" ;;
   elixir) success "Elixir project ready ($task_count tasks, debugging enabled)" ;;
   python) success "Python project ready ($task_count tasks, debugging enabled)" ;;

templates/commit-templates/work.txt

@@ -6,22 +6,22 @@
 
 # Work Project Commit Guidelines:
 # - Reference JIRA ticket numbers when applicable
-# - Include security considerations for LTI changes
-# - Mention Canvas compatibility testing
+# - Include security considerations when relevant
 # - Use professional, clear language
+# - Include testing details
 
 # Types for work projects:
-# feat: New LTI feature or Canvas integration
-# fix: Bug fix affecting LTI functionality
+# feat: New features or capabilities
+# fix: Bug fixes
 # security: Security improvements or fixes
-# canvas: Canvas-specific changes or compatibility updates
 # api: API changes or improvements
-# test: Adding or updating LTI integration tests
+# test: Adding or updating tests
 # docs: Documentation updates for team/stakeholders
 # chore: Maintenance, dependencies, or build changes
+# refactor: Code refactoring without changing functionality
 
 # Examples:
-# feat(lti): add grade passback functionality for assignments
-# fix(auth): resolve OAuth token refresh issue in Canvas
-# security(lti): implement additional CSRF protection
-# canvas(api): update to Canvas API v1.3 for better compatibility
+# feat(auth): add multi-factor authentication support
+# fix(api): resolve timeout issues in data processing
+# security(auth): implement rate limiting for login attempts
+# refactor(db): optimize query performance for user listings