Thanks for opening this discussion; I have suggested to OP to do it several times. The OP insisted on asking directly to me as if they hadn't understood the standard workings of the public question and answer platform and, more specifically, how the closing questions work.
As mentioned in a previous answer, the post-close notice shows multiple users voted to close the question. Considering this, the argument that the question was closed because a single user misunderstood the question doesn't look to sustain.
The original revision of the question was about general problems related to using open-source code. The later revisions have not made significant progress clarifying that the question is a good fit for GenAI tools.
Questions about general problems with using open-source code are off-topic on GenAI Stack Exchange; in other words, questions on this community should be about using GenAI Tool features, i.e., questions about using Stable Diffusion on a web browser might be on-topic, but troubleshooting like questions that require to:
- validate the user's computer meets the system requirements,
- that computer has the required components and they working correctly
- that have installed an open-source code project
- and debugging programming errors
are off-topic in this community.
Questions on this community should meet the standard public question and answer platform norms depicted in the GenAI Stack Exchange tour, help center and meta posts tagged faq.
The OP and others interested in the question should focus on understanding the GenAI Stack Exchange's:
- Topic and scope
- Workings
Some comments focused on reopening the question as if the site were a service desk that should accept any support request question, keeping the question with minimal changes.
Considering the GenAI Stack Exchange's stage, I think that one of the branches of this conversation should be focused on improving the question independently if, in the end, the question stays closed.
Another branch might be how to handle posts that might require back and forth beyond the standard use of comments.