For this PR i'm going to wait until we're good with the whole stuff, meaning that until we have a clue about how we're going to handle the api.gintingest.com subdomain.

@cyclotruc if you got time, please review the current state of the PR, the swagger UI can be improved as you wish.

@cyclotruc regarding comments from #24
i think i should expose a simple optional argument to make the output plain text OR json.

This is way better for LLMs and we keep the possibility to use json for API integrations.

Maybe we can do something like this : default -> plaintext, and "format=json" returns the json format. Still, everything will be easy to understand for LLMs since we have llms.txt with some examples and important note for LLMs, and provide the openapi.json file.

@ix-56h about exposing an argument format, I agree, but let's keep it for another pr and start with plain text for now

we still need to decide the structure of the json, would it be "summary, tree, content" or keys for each files in the digest? things like that

@ix-56h I think you can remove the additional tasks from the list for now and instead create an issue toward making the API public and documented

For now, let's just get this PR tested in order to bring back main into a stable state and move forward from there

thanks!

Here's the list of features to add on another PR once main is back to a working state:

• Serve /api/ingest | /api/{user}/{repo} | /api/ | /api to api.gitingest.com
• add hint about api doc location in llm.txt
• Add navbar link for API docs