chore: drop local prep notes from repo

This commit is contained in:
Eric Hiss
2025-10-30 00:28:10 -07:00
parent 6470017838
commit fc2caf7cab
2 changed files with 0 additions and 217 deletions
-190
View File
@@ -1,190 +0,0 @@
# Git Commit Preparation - v1.8.0
## Ready to Push to GitHub
All files have been organized and documentation updated. Here's what to do:
---
## 📋 Pre-Push Checklist
- [x] README.md completely rewritten
- [x] CHANGELOG.md updated with v1.8.0
- [x] Release notes created (RELEASE_NOTES_v1.8.0.md)
- [x] Old documentation moved to docs/archive/
- [x] New documentation files added
- [x] All code changes tested (no syntax errors)
- [x] .gitignore properly configured
---
## 🔄 Git Commands to Execute
### 1. Add All Changes
```bash
git add -A
```
This will add:
- Modified files (prompt_expander_node_advanced.py, expansion_engine.py, etc.)
- New files (qwen3_vl_backend.py, docs/ADVANCED_NODE_REDESIGN.md, etc.)
- Deleted files (old docs moved to archive)
### 2. Review Status
```bash
git status
```
Verify all expected changes are staged.
### 3. Commit
```bash
git commit -m "v1.8.0: Advanced Node Redesign + Syntax Preservation
Major Release - Complete Advanced Node Redesign
✨ New Features:
- Advanced node: 4 operation modes (expand/refine/modify_style/add_details)
- Advanced node: Clear detail levels (concise/moderate/detailed/exhaustive)
- Advanced node: Optional image input with Qwen3-VL integration
- Video nodes: Emphasis syntax preservation (keyword:1.5)
- Video nodes: Alternation syntax support {option1|option2}
🔧 Changes:
- Replaced confusing tier system with intuitive detail levels
- Added operation modes for modifying existing prompts
- Removed manual mode selection (auto-detected from image presence)
- Added Qwen3-VL backend for image analysis
- Backward compatible tier name mapping in expansion_engine
📚 Documentation:
- README.md completely rewritten
- docs/ADVANCED_NODE_REDESIGN.md - Complete redesign guide
- docs/BUGFIX_ADVANCED_NODE.md - Syntax preservation details
- docs/BUGFIX_SUMMARY.md - Quick reference
- Organized old docs into docs/archive/
🐛 Fixes:
- Emphasis syntax now properly preserved through LLM processing
- Alternation syntax for random element selection
- Image-to-video mode now functional with Qwen3-VL
⚡ Breaking Changes:
- None (fully backward compatible)
See RELEASE_NOTES_v1.8.0.md for complete details."
```
### 4. Push to GitHub
```bash
git push origin main
```
### 5. Create GitHub Release (Optional but Recommended)
Go to GitHub repository → Releases → Create new release
**Tag:** `v1.8.0`
**Title:** `v1.8.0 - Advanced Node Redesign + Syntax Preservation`
**Description:** Copy from RELEASE_NOTES_v1.8.0.md
---
## 📊 Changed Files Summary
### Core Files Modified (11)
- prompt_expander_node_advanced.py
- prompt_expander_node.py
- expansion_engine.py
- text_to_image_node.py
- image_to_image_node.py
- image_to_video_node.py
- img2img_expansion_engine.py
- llm_backend.py
- platforms.py
- utils.py
- requirements.txt
### New Files Added (7)
- qwen3_vl_backend.py
- VISION_BACKEND_GUIDE.md
- caption-instructions.md
- docs/ADVANCED_NODE_REDESIGN.md
- docs/BUGFIX_ADVANCED_NODE.md
- docs/BUGFIX_SUMMARY.md
- docs/archive/ (folder)
- RELEASE_NOTES_v1.8.0.md
### Documentation Updated (4)
- README.md (completely rewritten)
- CHANGELOG.md
- docs/CONFIGURATION.md
- docs/IMG2IMG_GUIDE.md
- docs/QUICKSTART.md
### Documentation Archived (11)
Files moved to docs/archive/:
- README_OLD.md
- UPDATE_NOTES.md
- UPDATE_NOTES_V12.md
- UPDATE_V13.md
- UPDATE_V15.md
- UPDATE_V16_ERIC.md
- UPDATE_V17_ENHANCED_CONTROLS.md
- FILE_CHANGES.md
- SETUP_COMPLETE.md
- BUGFIX_AUTO_MODE.md
- GITHUB_PUBLICATION_COMPLETE.md
---
## 🎯 What This Release Accomplishes
### User-Facing Improvements
1. **No more confusion** - Clear operation modes and detail levels
2. **More functionality** - Can now modify existing prompts, not just expand
3. **Image support** - Image-to-video actually works with Qwen3-VL
4. **Syntax preservation** - Emphasis and alternation syntax work properly
5. **Better documentation** - Complete rewrite of README for clarity
### Technical Improvements
1. **Backward compatible** - Old tier names still work
2. **Clean codebase** - Old docs archived, new structure organized
3. **Proper vision integration** - Qwen3-VL backend properly implemented
4. **Modular operation modes** - Easy to extend with new modes
5. **Comprehensive testing** - No syntax errors, validated changes
### Repository Quality
1. **Professional README** - Clear, comprehensive, well-organized
2. **Complete changelog** - All changes documented
3. **Archived history** - Old docs preserved but organized
4. **Release notes** - Proper v1.8.0 release documentation
5. **Clean git history** - All changes in one coherent commit
---
## ⚠️ Important Notes
1. **Restart Required**: Users MUST restart ComfyUI after updating
2. **Backward Compatible**: No breaking changes, old workflows still work
3. **Optional Dependencies**: Vision support requires additional packages
4. **Documentation**: Point users to README.md and QUICKSTART.md
---
## 🚀 After Push
1. Monitor GitHub issues for any problems
2. Update any external documentation/links if needed
3. Announce release in relevant communities
4. Respond to user feedback and questions
---
**Ready to execute the git commands above!**
The repository is clean, organized, and ready for v1.8.0 release.
-27
View File
@@ -1,27 +0,0 @@
You are a master prompt engineer specializing in creating highly detailed and evocative prompts for image generation AI (like Midjourney, Stable Diffusion, DALL-E 3, etc.). Your goal is to take a basic subject description and expand it into a rich, natural language prompt that will yield visually compelling results. Focus on detail, specificity, and artistic direction.
**Here's how you work:**
1. **Analyze the Input:** Break down the input subject description into its core components (subject, action/pose, environment, mood).
2. **Expand with Detail:** For *each* component, add descriptive details. Consider these categories:
* **Subject:** Age, gender, species (if applicable), clothing, key features, expression, material (e.g., "worn leather," "polished chrome").
* **Action/Pose:** Be specific! Don't just say "holding a sword." Say *how* they are holding it ("gripping the hilt with white knuckles," "resting casually across their shoulder," "raising above their head in triumph"). Pay special attention to any interaction – what is being touched, how firmly, and with what part of the body.
* **Environment:** Location (indoor/outdoor, specific place), time of day, lighting conditions (e.g., "soft golden hour light," "harsh neon glow"), weather. Consider background elements – what's *behind* the subject?
* **Mood/Atmosphere:** Use adjectives to convey the desired feeling ("serene," "dramatic," "mysterious," "joyful"). Consider color palettes that reinforce the mood.
3. **Artistic Direction:** Add details about style, artist influence, camera angle, and rendering quality:
* **Style:** (e.g., photorealistic, impressionistic, cyberpunk, fantasy art)
* **Artist Influence:** (e.g., "in the style of Alphonse Mucha," "inspired by Greg Rutkowski")
* **Camera Angle/Shot Type:** (e.g., close-up, wide shot, bird's eye view, low angle, cinematic framing)
* **Rendering Quality:** (e.g., highly detailed, 8k resolution, volumetric lighting, ray tracing). Consider adding details like "depth of field" or "motion blur".
4. **Combine & Refine:** Weave all the elements together into a coherent and grammatically correct prompt. Aim for natural language – avoid overly technical jargon unless it's crucial to the style.
**Important Considerations:**
* **Detail *Anything* Important:** Any element of the subject, action, or environment that is significant (either explicitly stated or implicitly suggested) should be described in detail. Don’t gloss over anything!
* **No Censorship:** If the input suggests an erotic or sexual scene, embrace it! Describe genitals, positions, and contact with specificity – don't shy away from details. The level of detail should match the overall prompt complexity.
* **Use Strong Adjectives & Verbs:** Avoid vague language ("a man standing"). Use evocative words ("a grizzled warrior striding confidently").
* **Prioritize Visual Impact:** Think about what will make the image visually interesting and compelling.
**Input Format:** You'll receive a simple subject description.
Output Format: A single detailed, natural language paragraph ready for an image generation AI. Aim for around 50-150 words (adjust as needed).