AI Editor: add example config files

[miltondp]

No description provided.

[AppVeyorBot]

AppVeyor build 1.0.339 for commit 33e2bdf is now complete.

Found 51 potential spelling error(s). Preview:

content/02.delete-me.md:44:adipiscing
content/02.delete-me.md:44:aliqua
content/02.delete-me.md:44:amet
content/02.delete-me.md:44:consectetur
content/02.delete-me.md:44:dolore
content/02.delete-me.md:44:eiusmod
content/02.delete-me.md:44:elit
content/02.delete-me.md:44:incididunt
content/02.delete-me.md:44:ipsum
content/02.delete-me.md:44:labore
content/02.delete-me.md:44:Lorem
content/02.delete-me.md:44:magna
content/02...

The rendered manuscript from this build is temporarily available for download at:

• manuscript-1.0.339-33e2bdf.html
• manuscript-1.0.339-33e2bdf.pdf
• spelling-errors-1.0.339-33e2bdf.txt
• spelling-error-locations-1.0.339-33e2bdf.txt

[dhimmel]

I don't think ai_revision-config.yaml and ai_revision-prompts.yaml belong under content, which should remain primarily content that composes the manuscript.

I think ci or less likely build would be a more appropriate directory.

[miltondp]

Thanks, Daniel. I'll talk with @vincerubinetti and Faisal about this.

[falquaddoomi]

Hey @dhimmel, agreed; per your suggestion we've moved the config files to ci rather than content.

[miltondp]

@dhimmel this PR is ready to be merged. @vincerubinetti maybe you can start testing this now.

[dhimmel]

missing final newline.

[miltondp]

Fixed!

[vincerubinetti]

@dhimmel note that doing a fresh fork of rootstock failed (for the ai editor) because the manubot package is specified as a specific commit rather than a semver or github@latest version. That will be need to be updated as well. It also seems like a new PIPY version should be pushed, and that rootstock should be based off of PYPI, but I'll leave that to you.

[miltondp]

@dhimmel note that doing a fresh fork of rootstock failed (for the ai editor) because the manubot package is specified as a specific commit rather than a semver or github@latest version. That will be need to be updated as well. It also seems like a new PIPY version should be pushed, and that rootstock should be based off of PYPI, but I'll leave that to you.

From this, I understand that following the instructions to create a new Manubot-based manuscript (fork of this repo) and run the AI Editor would fail, right?

[dhimmel]

note that doing a fresh fork of rootstock failed (for the ai editor) because the manubot package is specified as a specific commit rather than a semver or github@latest version.

This pull request should have incremented the manubot version for manubot ai-revision --config-directory support. My bad for not noting that during the review.

#513 upgrades the manubot version used in rootstock and should resolve the problem.

I see the following as separate points as separate from the cause of this issue (and separate from eachother):

• whether rootstock installs the latest manubot version or a pinned version (I strongly prefer pinned here)
• whether the manubot package is installed from GitHub or PyPI