1. No, you do not need to manually add a list into mailman. The Savane cronjobs (if set up), will create the mailing list on the backend. If you use the example crontab file that comes with the savane tarball, it is set to run sv_mailman every 30 minutes. This backend script, sv_mailman, takes mailing list data from the database, and if it doesn't exist in the system, it creates it. You can, at your discretion, run sv_mailman yourself, and it will create the lists. You can run sv_mailman with the --debug command line argument, and it will dump a lot of data about what it would do. The script changes the value of a field in the database once it attempts to create a list, so while you're testing your setup, you might need to manually remove mailman lists (using rmlist), and/or remove records from the Savane database.
2. Your group type setup looks normal to me. Can you browse to, subscribe and post to mailman lists outside of Savane? Try creating a list yourself and test the mailman setup without involving mailman. Check the logs too. They often contain very useful information. Make sure you're following the guidelines for setting up a mailman setup in Apache too. You need to configure CGI script handling on the cgi-bin directory too.
Hope this helps.

On a Debian system, I have the following 3 Alias lines in my apache.conf:

Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/

This will allow you browse to http://localhost/mailman/listinfo/, and get your mail listings.

It looks like sv_cleaner sets the mailing list as deleted, and lets sv_mailman finish up the job (by running rmlist I'd presume). All the sv_* scripts are backend tasks that are run by cron. Take a look at savane/etc/crontab.

If you set up the sample savane cron file, there is a sv_mailman cronjob that runs every 30 minutes to create mailing lists. You can run that script manually for the mailman jobs to run.