refactor: clear package-lint warnings for MELPA prep

I worked through the package-lint backlog and got it to zero. Five changes:

1. Renamed six interactive debug commands from the private `chime--debug-*'
   prefix to the public `chime-debug-*' form. They were always M-x targets,
   so the private prefix was just wrong. The autoload cookies stay because
   public commands SHOULD be autoloaded. README, docstring references in
   chime.el, and the matching tests follow the rename.

2. Dropped `Version', `Package-Requires', and `Keywords' headers from
   chime-org-contacts.el. Auxiliary files in a multi-file package shouldn't
   carry their own metadata — package-lint flags it as an error because the
   headers have no effect outside the main file. The main file (chime.el)
   already declares the chime package's metadata.

3. Dropped `Keywords' from chime-debug.el for the same reason.

4. Dropped the auto-loader for the optional chime-org-contacts integration
   from chime.el. The old code used `with-eval-after-load 'org-capture' to
   pull the file in, which package-lint flags as a configuration pattern
   that doesn't belong in a package. Users who want the integration now
   require it themselves; the README shows both the plain `with-eval-after-load'
   pattern and the `use-package :after' form. chime-org-contacts.el's
   internal `with-eval-after-load' went away too — by the time the user has
   required the file, they've already gated it on org-capture being loaded,
   so the inner check is redundant.

5. Dropped the redundant `with-eval-after-load' from chime-org-contacts.el's
   activation block. The setup function still guards on
   `(boundp 'org-capture-templates)' so it's safe to require either order.

Behavioral note: this is a small breaking change for anyone whose config
relied on the auto-load. The README change spells out the migration path.

0 files changed, 0 insertions, 0 deletions