Skip to content

Clean launch rough edges: artifacts, optional imports, docs extras, smoke script #29

@bordeauxred

Description

@bordeauxred

Why

Small repository rough edges become support burden when more users arrive.

What

  • Decide whether tracked generated analysis artifacts are intentional. If not, remove them and add ignore rules.
  • Add a docs extra so docs builds are reproducible.
  • Add release tooling dependencies or document how to build/check artifacts.
  • Add a public smoke script that runs the no-key demo, tests, package build, wheel install, and package audit.
  • Avoid eager imports of heavy optional benchmark adapters from the package namespace.
  • Make README snippets complete or explicitly label them pseudo-code.

Acceptance

  • Public repo has no accidental generated artifacts.
  • Docs/release checks are reproducible from documented commands.
  • import clawloop remains cheap and does not require optional benchmark dependencies.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ai_tinker_launchAI Tinkerers newsletter launch readinessenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions