Verify and document dynamic question choices with runtime code execution

[Copilot]

Question choices can be derived from filesystem state or runtime code execution. Investigation confirms this already works - inquirer executes callable choices parameters, and questions reload after each answer via _load_workflow().

Changes

Tests (tests/test_dynamic_choices.py)

• Filesystem-based choices: verify choices evaluated from os.listdir()
• Conditional choices: verify choices change based on previous answers

Example application (examples/dynamic-choices-application/)

• Demonstrates 5 patterns: filesystem listing, conditionals, nested conditionals, environment-aware, answer-dependent
• Ready-to-use reference for application developers

Documentation

• Explains callable choices mechanism
• Shows question reload behavior on answer submission

Mechanism

def mainflow(self, data=None):
    def get_files(answers):
        """Executed when question created/reloaded"""
        return os.listdir('/path')
    
    return [List('file', message='Choose:', choices=get_files)]

Inquirer calls the function immediately, storing the result. Since _load_workflow() runs after each answer (session_manager.py:78), choices stay current with filesystem/answer state.

No implementation changes required - feature already functional.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.