Release v1.1.0: Function block member completion feature

- Added function block instance member completion (myTimer.Q, upCounter.CV)
- Enhanced README.md with professional marketplace format
- Updated CHANGELOG.md for v1.1.0
- Added syntax highlighting screenshot
- Optimized package.json description and keywords
- Comprehensive test coverage (44 tests passing)
- Updated documentation and release planning

Author: michaeldistel

.vscodeignore

@@ -18,7 +18,12 @@ examples/**
 # Exclude development files
 .husky/**
 TESTING.md
+MANUAL_QA_PLAN.md
+RELEASE_PLAN.md
+images/README.md
 # Keep these in the package
 # CHANGELOG.md
 # README.md
 # LICENSE
+# icon.png
+# images/ (for screenshots)

CHANGELOG.md

@@ -1,5 +1,25 @@
 # Change Log
 
+## [1.1.0] - 2025-06-16
+
+### Added
+- **Function Block Instance Member Completion**: Auto-complete for function block output members
+  - Dot notation support (e.g., `myTimer.Q`, `upCounter.CV`)
+  - Support for all IEC 61131-3 standard function blocks (TON, TOF, TP, CTU, CTD, CTUD, R_TRIG, F_TRIG, RS, SR)
+  - Type-aware suggestions with detailed descriptions
+- Enhanced parser with function block instance extraction
+- Enhanced code snippets and examples
+
+### Improved
+- Syntax highlighting with additional keywords (END_CONFIGURATION, END_RESOURCE)
+- Better variable and function block detection
+- Enhanced error handling and performance
+- Updated documentation and testing infrastructure
+
+### Fixed
+- Missing syntax highlighting for configuration keywords
+- Parser edge cases for variable declarations
+
 ## [1.0.1] - 2024-01-09 15:30:00
 
 ### Changed

README.md

@@ -1,42 +1,114 @@
-# ControlForge Structured Text - VS Code Extension
+# ControlForge Structured Text
 
-Professional development environment for IEC 61131-3 Structured Text PLC programming in Visual Studio Code.
+[![Visual Studio Marketplace Version](https://img.shields.io/visual-studio-marketplace/v/ControlForgeSystems.controlforge-structured-text)](https://marketplace.visualstudio.com/items?itemName=ControlForgeSystems.controlforge-structured-text)
+[![Visual Studio Marketplace Installs](https://img.shields.io/visual-studio-marketplace/i/ControlForgeSystems.controlforge-structured-text)](https://marketplace.visualstudio.com/items?itemName=ControlForgeSystems.controlforge-structured-text)
 
-## Features
+Professional **Structured Text (IEC 61131-3)** development environment for **PLC programming** in Visual Studio Code.
 
-- **Syntax Highlighting**: Full support for Structured Text programming language
-- **Language Support**: Complete IEC 61131-3 standard compliance
-- **Code Validation**: Built-in syntax validation to catch errors early
+## ✨ Key Features
 
-## Language Features
+- 🎯 **Function Block IntelliSense**: Auto-complete for FB outputs (`myTimer.Q`, `upCounter.CV`)
+- 🌈 **Rich Syntax Highlighting**: Complete IEC 61131-3 language support
+- 💡 **Smart Code Completion**: Context-aware suggestions for keywords, types, and variables
+- 🔧 **Code Validation**: Built-in syntax validation and error detection
+- 📝 **Code Snippets**: Pre-built templates for common PLC patterns
 
-- Comprehensive syntax highlighting for:
-  - Keywords (IF, THEN, ELSE, FOR, WHILE, etc.)
-  - Data types (BOOL, INT, REAL, STRING, etc.)
-  - Operators (AND, OR, NOT, arithmetic operators)
-  - Comments (// and (* *))
-  - String literals
-  - Numeric literals (decimal, hex, binary, octal)
+## 📸 Screenshots
 
-- Smart editor features:
-  - Auto-closing brackets and quotes
-  - Comment toggling support
-  - Intelligent word pattern matching
+### Syntax Highlighting & IntelliSense
+![Syntax Highlighting](images/syntax-highlighting.png)
+*Rich syntax highlighting for all IEC 61131-3 constructs*
 
-## Usage
+## 🚀 Getting Started
 
-1. Open any `.st` or `.iecst` file in VS Code
-2. Syntax highlighting is automatically enabled
-3. Use `Ctrl+Shift+P` and type "Validate Syntax" to check your code
+### Installation
+1. Open **Visual Studio Code**
+2. Go to **Extensions** (`Ctrl+Shift+X`)
+3. Search for **"ControlForge Structured Text"**
+4. Click **Install**
 
-## Requirements
+### Quick Start
+1. Create a new file with `.st` or `.iecst` extension
+2. Start typing - syntax highlighting activates automatically
+3. Use `Ctrl+Space` for IntelliSense completion
+4. Type function block instances followed by `.` for member completion
 
-- Visual Studio Code 1.74.0 or higher
+### Function Block Completion Example
+```st
+PROGRAM MyProgram
+VAR
+    startTimer : TON;          // Timer On-Delay
+    partCounter : CTU;         // Counter Up
+    emergencyStop : R_TRIG;    // Rising Edge Trigger
+END_VAR
 
-## Support
+// IntelliSense in action:
+startTimer.     // Shows: Q (BOOL), ET (TIME)
+partCounter.    // Shows: Q (BOOL), CV (INT)
+emergencyStop.  // Shows: Q (BOOL)
+END_PROGRAM
+```
 
-Visit [controlforge.dev](https://controlforge.dev/) for documentation and support.
+## 📋 Language Features
 
-## License
+### 🧠 Smart IntelliSense
+- **Function Block Members**: Auto-complete for all standard IEC 61131-3 function blocks
+  - Timers: `TON`, `TOF`, `TP` → `Q`, `ET`
+  - Counters: `CTU`, `CTD`, `CTUD` → `Q`, `CV`, `QU`, `QD`
+  - Edge Detectors: `R_TRIG`, `F_TRIG` → `Q`
+  - Bistables: `RS`, `SR` → `Q1`
+- **Keyword Completion**: All IEC 61131-3 keywords and constructs
+- **Data Type Suggestions**: `BOOL`, `INT`, `REAL`, `TIME`, `STRING`, etc.
+- **Variable Detection**: Automatically detects declared variables
+- **Code Snippets**: Templates for common patterns (IF-THEN, FOR loops, etc.)
 
-Licensed under the Business Source License 1.1 (BUSL-1.1). For details, see [License Terms](https://controlforge.dev/license).
+### 🎨 Syntax Highlighting
+### 🎨 Syntax Highlighting
+- **Keywords**: `IF`, `THEN`, `ELSE`, `FOR`, `WHILE`, `CASE`, `VAR`, `END_VAR`
+- **Data Types**: `BOOL`, `INT`, `REAL`, `TIME`, `STRING`, `ARRAY`, `STRUCT`
+- **Operators**: `AND`, `OR`, `NOT`, `XOR`, `:=`, `+`, `-`, `*`, `/`
+- **Comments**: `//` single-line and `(* *)` multi-line
+- **Literals**: String, numeric (decimal, hex, binary), time literals
+- **Function Blocks**: Standard IEC 61131-3 function blocks
+
+### 🔧 Editor Features
+- **Auto-closing**: Brackets, quotes, and parentheses
+- **Comment Toggle**: `Ctrl+/` for quick commenting
+- **Word Matching**: Intelligent word selection and highlighting
+- **File Association**: Automatic recognition of `.st` and `.iecst` files
+
+## 💻 Supported File Extensions
+- `.st` - Standard Structured Text files
+- `.iecst` - IEC 61131-3 Structured Text files
+
+## ⚙️ Requirements
+- **Visual Studio Code** 1.100.0 or higher
+- **Operating System**: Windows, macOS, or Linux
+
+## 🛠️ Commands
+Access these commands via the Command Palette (`Ctrl+Shift+P`):
+- **"Structured Text: Validate Syntax"** - Check code for syntax errors
+
+## 📊 What's New in v1.1.0
+- ✨ **Function Block Member Completion** - The headline feature!
+- 🔍 **Enhanced Parser** - Better variable and FB instance detection
+- 🧪 **Comprehensive Testing** - Automated tests ensure reliability
+- 📚 **Improved Documentation** - Better examples and guides
+
+## 🤝 Support & Feedback
+
+## 🤝 Support & Feedback
+
+- 🌐 **Website**: [controlforge.dev](https://controlforge.dev/)
+- 📧 **Issues**: [GitHub Issues](https://github.com/ControlForge-Systems/controlforge-structured-text/issues)
+- 💬 **Discussions**: [GitHub Discussions](https://github.com/ControlForge-Systems/controlforge-structured-text/discussions)
+- ⭐ **Rate & Review**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=ControlForgeSystems.controlforge-structured-text)
+
+## 📄 License
+
+Licensed under the **Business Source License 1.1 (BUSL-1.1)**.  
+For details, see [License Terms](https://controlforge.dev/license).
+
+---
+
+**Made with ❤️ for the PLC programming community**

RELEASE_PLAN.md

@@ -0,0 +1,175 @@
+# Release Plan Checklist - ControlForge Structured Text Extension
+
+## Overview
+This checklist ensures a smooth and successful release of version with the new function block instance member completion feature.
+
+## Pre-Release Checklist
+
+### 🔧 Code Quality & Testing
+- [ ] All unit tests passing (26/26)
+- [ ] All E2E tests passing (18/18)
+- [ ] Manual QA completed successfully
+- [ ] No console errors or warnings
+- [ ] Code coverage acceptable
+- [ ] TypeScript compilation clean
+- [ ] ESLint/Prettier formatting applied
+
+###  Documentation
+- [ ] README.md updated with new features
+- [ ] CHANGELOG.md updated for v1.1.0
+- [ ] Package.json version bumped
+- [ ] Feature documentation complete
+- [ ] API documentation updated
+- [ ] Manual QA plan simplified and clean
+
+### 🔄 Version Management
+- [ ] Version number updated in package.json
+- [ ] Git tags aligned with version
+- [ ] Release branch (Release-1.1.0) ready
+- [ ] All feature branches merged
+- [ ] Issue1 branch merged and closed
+- [ ] Clean git history
+
+## Release Execution
+
+### 📦 Extension Packaging
+- [ ] Build extension package (`vsce package`)
+- [ ] Test .vsix file installation
+- [ ] Verify package size reasonable
+- [ ] Check included/excluded files correct
+- [ ] Extension metadata complete
+
+### 🚀 Marketplace Deployment
+- [ ] VS Code Marketplace publisher account ready
+- [ ] Extension published (`vsce publish`)
+- [ ] Marketplace listing updated
+- [ ] Screenshots/GIFs current
+- [ ] Extension description accurate
+- [ ] Keywords and categories appropriate
+
+### 🏷️ GitHub Release
+- [ ] Create GitHub release tag (v1.1.0)
+- [ ] Upload .vsix file to release
+- [ ] Release notes written
+- [ ] Breaking changes documented
+- [ ] Installation instructions provided
+
+## Post-Release Checklist
+
+### 📊 Monitoring & Validation
+- [ ] Extension appears in marketplace
+- [ ] Download/install metrics tracking
+- [ ] User feedback monitoring setup
+- [ ] Issue tracker ready for reports
+- [ ] Performance monitoring active
+
+### 🔍 Quality Assurance
+- [ ] Fresh installation test
+- [ ] Multiple VS Code versions tested
+- [ ] Different operating systems validated
+- [ ] User acceptance testing
+- [ ] Community feedback positive
+
+### 📢 Communication
+- [ ] Release announcement prepared
+- [ ] Documentation website updated
+- [ ] Social media posts ready
+- [ ] Developer community notified
+- [ ] User guides available
+
+## Version 1.1.0 Feature Summary
+
+### 🆕 New Features
+- **Function Block Instance Member Completion**: Auto-complete for FB outputs
+  - Dot notation support (`instanceName.`)
+  - All IEC 61131-3 standard function blocks
+  - Type-aware suggestions with descriptions
+- **Enhanced Syntax Highlighting**: Fixed missing keywords
+- **Improved Parser**: Better variable and FB instance extraction
+
+### 🔧 Technical Improvements
+- Comprehensive test coverage (44 automated tests)
+- Enhanced code snippets
+- Better error handling
+- Performance optimizations
+
+### 📖 Documentation Enhancements
+- Simplified manual QA plan
+- Enhanced example files
+- Comprehensive testing documentation
+
+## Rollback Plan
+
+### 🚨 If Issues Arise
+- [ ] Unpublish from marketplace if critical bugs
+- [ ] Revert to previous stable version
+- [ ] Document known issues
+- [ ] Prepare hotfix release plan
+- [ ] Communicate with users
+
+### 🔄 Hotfix Process
+- [ ] Create hotfix branch from Release-1.1.0
+- [ ] Apply minimal fix
+- [ ] Emergency testing protocol
+- [ ] Expedited release process
+- [ ] Version bump (1.1.1)
+
+## Success Criteria
+
+### ✅ Release is successful if:
+- [ ] Extension installs without errors
+- [ ] Function block completion works as expected
+- [ ] No critical bugs reported in first 48 hours
+- [ ] User feedback generally positive
+- [ ] Performance metrics acceptable
+- [ ] Download numbers growing
+
+### 📈 Key Metrics to Track
+- Download count (target: >100 in first week)
+- User ratings (target: >4.0 stars)
+- Issue reports (target: <5 critical issues)
+- Performance benchmarks maintained
+- Community engagement positive
+
+## Team Responsibilities
+
+### 🧑‍💻 Development Team
+- [ ] Code quality assurance
+- [ ] Test execution
+- [ ] Bug fixes pre-release
+- [ ] Technical documentation
+
+### 📋 QA Team
+- [ ] Manual testing execution
+- [ ] Cross-platform validation
+- [ ] Performance testing
+- [ ] User acceptance testing
+
+### 📢 Release Manager
+- [ ] Checklist coordination
+- [ ] Marketplace deployment
+- [ ] GitHub release creation
+- [ ] Communication planning
+
+## Timeline
+
+### 📅 Release Schedule
+- **T-3 days**: Final testing and QA
+- **T-2 days**: Package creation and validation
+- **T-1 day**: Final documentation review
+- **T-0**: Release execution
+- **T+1 day**: Post-release monitoring
+- **T+7 days**: Release retrospective
+
+---
+
+## Notes
+- All checkboxes must be completed before release
+- Any blockers should be documented and resolved
+- Emergency contacts available during release window
+- Rollback plan ready if needed
+
+**Release Manager**: _[Name]_  
+**Release Date**: _[Date]_  
+**Version**: v1.1.0  
+**Build**: _[Build Number]_

images/README.md

@@ -0,0 +1,37 @@
+# Screenshot Placeholders
+
+This directory contains screenshots for the README.md file.
+
+## Required Screenshots:
+
+1. **function-block-completion.gif** - Animated GIF showing:
+   - Typing `myTimer.` and seeing completion for `Q` and `ET`
+   - Typing `upCounter.` and seeing completion for `Q` and `CV`
+   - Show the type information and descriptions
+
+2. **syntax-highlighting.png** - Static image showing:
+   - A sample .st file with rich syntax highlighting
+   - Different colors for keywords, types, operators, comments
+   - Function block declarations and usage
+
+## How to Create Screenshots:
+
+### For function-block-completion.gif:
+1. Open VS Code with the extension
+2. Create a new .st file with function block instances
+3. Use a screen recorder (like OBS, LICEcap, or VS Code's built-in recorder)
+4. Record typing the dot notation and showing completions
+5. Export as GIF, keep under 3MB for GitHub
+
+### For syntax-highlighting.png:
+1. Open `examples/test_instance_members.st` or similar
+2. Make sure all syntax highlighting is visible
+3. Take a screenshot showing the full file
+4. Crop to show relevant code with good highlighting
+5. Save as PNG
+
+## Guidelines:
+- Keep file sizes reasonable (< 3MB for GIFs, < 1MB for PNGs)
+- Use high contrast themes for better visibility
+- Show real, meaningful code examples
+- Ensure text is readable at GitHub's display sizes