*  <tt>[/finfo?name=f-apps/f-resolve.c|f-resolve]</tt> resolves symbolic checkin names (like "trunk", "current", and "prev") and partial UUIDs to their full UUIDs and RIDs.
   *  <tt>[/finfo?name=f-apps/f-rm.c|f-rm]</tt> queues files for removal at the next commit or cancels uncommitted "add" commands.
   *  <tt>[/finfo?name=f-apps/f-sanity.c|f-sanity]</tt> runs a number of sanity checks on the library. Library developers should run/amend this occasionally.
   *  <tt>[/finfo?name=f-apps/f-status.c|f-status]</tt> behaves mostly like fossil's <tt>status</tt> command.
   *  <tt>[/finfo?name=f-apps/f-tag.c|f-tag]</tt> adds tags to artifacts.
   *  <tt>[/finfo?name=f-apps/f-timeline.c|f-timeline]</tt> provides a timeline of recent repository activity. 
   *  <tt>[/finfo?name=f-apps/f-wiki.c|f-wiki]</tt> is a generic wiki manipulation tool, capable of listing, exporting, and importing wiki pages.
   *  <tt>[/finfo?name=f-apps/f-zip.c|f-zip]</tt> creates ZIP files from a given version of repository content.


All of these applications accept <tt>-?</tt>, <tt>--help</tt>, or a first non-flag argument of <tt>help</tt> to show their help text.

These applications provide demonstrations of using the library and give devs a place to test new features. <tt>[FossilApp|fcli]</tt> provides a mini-framework which takes care of bootstrapping fossil for these applications, making it pretty simple to create new ones. fcli handles the CLI parsing, global flags, opening of a repo/checkout, and other "getting started" bits. If you've ever hacked on fossil(1), adding a new f-* app is very similar to adding a new command to fossil, with only a few more lines of bootstrap code (because each "command" is in its own app).

<h2>Demos</h2>