1.x-1.0.0-beta3

Beta3 work. No schema change - schema_version stays 1001.

Fixed

• Unticking Appear in forum list promoted a forum's sub-forums to the top
  of the forums index instead of hiding them. The index uses the Forum
  hierarchy style, which treats a forum whose parent is absent from the result
  set as top-level, so hiding a container pushed its children up to root. An
  unlisted forum now takes its whole branch out of the index, at any depth.
  Each forum still lists its own sub-forums on its own page, so an unlisted
  section browses normally from inside - which is what lets it be presented
  under its own menu link or view. The rule is flat for everyone including
  administrators (the index is a members' menu, not an admin screen); the
  forum admin overview carries no Listed filter and is unaffected. Any forum
  view gets the rule if it filters on Listed; dropping that filter opts out.

Added

• Forum icon as a Views field. Placeable in any view on the forum base
  table, and reachable from a topic or reply view through the forum
  relationship. Renders at each forum's own icon style by default, or at one
  style chosen for the view. Previously the icon was only reachable inside the
  forums-index identity cell.
• Hierarchy in the forum pickers. The Parent forum and Discussion forum
  selects list forums in tree order, indented one dash per level, siblings by
  weight then title - the same order as the forums index.
• Classes on the forum page's Post new topic link
  (entity-forum-new-topic-link button), matching what the Views area handler
  already emitted, so one theme rule styles it wherever it appears.

Internal

• entity_forum_forum_path() is now the single definition of a forum's page
  address, which EntityForumForum::uri() and every breadcrumb, forum link
  and post-submit redirect resolve through, replacing six copies of the same
  composed path. It takes an ID rather than an entity because the bulk callers
  work from light rows and would otherwise cost one entity load per listed
  forum.

Docs / config

• Shipped classified image/file fields no longer carry filefield_paths*
  keys, and README gains a Limitations warning: modules that rewrite a managed
  file's path or name fight the private-forum re-scheme (a leak) and can
  collide on the unique names the importer relies on. Existing installs are
  unaffected - the keys only ever took effect where filefield_paths was also
  installed.