Skip to content

Bring repo up to the filigree standard#16

Merged
tachyon-beep merged 6 commits into
mainfrom
docs/repo-standardization
Jun 1, 2026
Merged

Bring repo up to the filigree standard#16
tachyon-beep merged 6 commits into
mainfrom
docs/repo-standardization

Conversation

@tachyon-beep

Copy link
Copy Markdown
Collaborator

Implements docs/superpowers/specs/2026-06-01-wardline-repo-standardization-design.md.

Toolchain & CI

  • uv parity with filigree: dev → PEP 735 [dependency-groups], uv.lock, .python-version (build stays hatchling).
  • CI split into lint / typecheck / test, a 3.12 + 3.13 matrix, ruff format --check, and a 90% coverage floor (current ~93%). Dogfood SARIF scan, weekly judge e2e, and docs deploy preserved, rewired onto uv.
  • release.yml builds with uv build; the PyPI Trusted-Publishing job is unchanged — packages still publish.
  • Makefile (make ci/lint/format/test-cov/scan-self/...) and a ruff pre-commit config.

Docs

  • filigree-class README (badges, hero finding, features, quick start, agent setup, where-it-fits, docs table).
  • Expanded CONTRIBUTING (uv, conventional commits, make ci PR gate); new ROADMAP; Contributor Covenant v2.1.

Use ⇄ develop split

  • CLAUDE.md / AGENTS.md are now tracked (matching filigree; only .mcp.json stays ignored) and carry curated developer guidance + an Audience banner pointing end-user "how to use" guidance to the install block, the wardline-gate skill, and the docs site. Dev commands updated to uv.
  • Coverage artifacts (.coverage, coverage.json) gitignored and untracked.

No engine/source behaviour changes (formatting-only churn from ruff format). Local make ci, uv build + twine check, mkdocs build --strict, and the dogfood scan all pass.

Note: this branch also carries 5abf5ba docs(spec): design config-backed trust declarations (your own commit, made on this branch) — included as-is.

🤖 Generated with Claude Code

John Morrissey and others added 6 commits June 1, 2026 17:11
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a new design spec for extending Wardline's trust-declaration
capability so agentic coding agents can mark code as
external_boundary, trust_boundary, or trusted via wardline.yaml
instead of editing source.

Design decisions captured:
- trust semantics only in v1
- inline wardline.yaml trust block (not sidecar/store)
- path-glob defaults + exact-qualname entity overrides
- precedence: entity config > decorator > path default > fallback
- strict schema + typed parse + required reasons
- explicit composite provider chain
- provider fingerprint includes trust config hash for cache invalidation
- unmatched exact qualnames surface as a NONE-severity config fact

Also records testing strategy, non-goals, and the forward extension
path for future behavior-affecting property families.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…plit)

Match filigree: stop gitignoring CLAUDE.md and AGENTS.md (keep .mcp.json
ignored). Both now carry curated Wardline developer guidance above the
auto-managed Filigree block, with an Audience banner pointing end-user
'how to use' guidance to the install block, wardline-gate skill, and docs
site. Dev commands updated to the uv toolchain.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…IF fix)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 1, 2026 07:22
@tachyon-beep
tachyon-beep merged commit 87c434f into main Jun 1, 2026
8 of 9 checks passed
@tachyon-beep
tachyon-beep deleted the docs/repo-standardization branch June 1, 2026 07:23

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants