Yes; an interface will need to be made available for accessing the archives. (how it was tested without one I'm not sure, but?)
This can be web-based (please not php) or-- well, you could just do it inside the mush. This would be another set of commands to run queries to retrieve archived job info-- and likely do various types of searches.
I very strongly recommend using the @query interface for async db queries-- that way you can run them without hanging the game, which is handy for very large/complex queries. It also has the nice result of returning a row at a time with a @trigger-like interface.
So, I tried all that and it didn't do the trick. I ended up just putting up a @readcache cron job every 30 minutes. All you who follow in my footsteps: skip the troubleshooting and just use the cron. @Sponge is wise.