Clarify the license scope for repository and dataset assets

## Problem

The repository does not identify which license applies to each distributed surface.

At current `main@2de83cb43b759c7b3d07c749c6a3efccd4528007`, the README says only:

> This project is licensed under the Apache-2.0 License.

The linked Hugging Face dataset currently declares `CC-BY-4.0`. The repository and Pages source also include paper figures, screenshots, generated gallery images, videos, JSON lists, and website code, but neither README nor the project page distinguishes the license for those categories.

## Reproduction

1. Read the repository README and LICENSE.
2. Follow the Data link to https://huggingface.co/datasets/ByteDance/TableVerse.
3. Try to determine the license for each of: repository documentation/site code, checked-in figures and demo media, and downloaded dataset archives.

## Expected behavior

The documentation should state the license boundary clearly—for example, which files are covered by Apache-2.0 and which dataset/media content is covered by CC-BY-4.0 or another policy.

## Actual behavior

The repository-level Apache statement and dataset-level CC-BY-4.0 declaration are both present, but their scopes are not explained.

## Impact

Downstream users cannot determine the applicable reuse and attribution requirements for the repository's different asset classes.

## Why this report has no PR

Choosing and documenting the boundary is a licensing decision for the copyright holders. A contributor cannot safely infer whether the checked-in media belongs with the project license, the dataset license, or a separate policy. Once maintainers confirm that boundary, the README, project-page footer, and any dataset references can be updated consistently.

## Evidence

- Default branch: `main@2de83cb43b759c7b3d07c749c6a3efccd4528007`
- Pages source: `web@66efcf4f1f8a4aaf5cc937e5b6d5bd9724f3ea04`
- Hugging Face card checked 2026-08-22: `license: cc-by-4.0`

Start by reading the repository README and LICENSE, then compare the Pages source and the linked Hugging Face dataset card. Identify the asset categories and their current license statements, including the project-page footer and dataset references. Done means maintainers have confirmed the license boundary and the affected documentation locations are updated consistently.

Written by the indexing model from the issue text.