Files
roadmap/content/sc/status-l2/2025q4-maintaining-status-l2-contracts.md
fbarbu15 845d6b8dcd Chore/roadmap validator (#318)
## Summary

- Introduce a standalone Python roadmap validator with a CLI entry
point, modular validation pipeline, and GitHub Actions wiring so roadmap
content can be linted locally and in CI.
- Provide reusable validation primitives for path resolution,
front-matter parsing, identity checks, task parsing, catalog
enforcement, and template adherence.
- Document usage, configuration, and workflow behaviour to make the
validator approachable for contributors.

## Validator Details

- **Core tooling**
- Added the `tools/roadmap_validator/` package with `validate.py` (CLI),
`validator.py` (orchestration), and helper modules (`tasks.py`,
`identity.py`, `paths.py`, `constants.py`, `issues.py`).
- CLI supports directory/file targets, skips default filenames, emits
GitHub annotations, and integrates optional substring filtering
- README explains features, environment variables, and development
guidance.
- **Catalog and template enforcement**
- `catalog.py` verifies each allowed content unit has `index.md` and
`preview.md`, confirms roadmap entries appear under the proper
quarter/area, and flags stale or missing links.
- `templates.py` enforces template basics: front matter completeness,
`## Description` ordering/content, template placeholder cleanup, and
task section detection.
- **Task validation**
- `tasks.py` checks required metadata (`owner`, `status`, `start-date`,
`end-date`), date formats, populated descriptions/deliverables, TODO
markers, tangible deliverable heuristics, and `fully-qualified-name`
prefixes.
- **Workflow integration**
- `.github/workflows/roadmap-validator.yml` runs the validator on pushes
and manual dispatch, installs dependencies, scopes validation to changed
Markdown, and surfaces findings via GitHub annotations.

## Existing Roadmap Updates

- Normalised 2025q4 commitments across Web, DST, QA, SC, and other units
by filling in missing descriptions, deliverables, schedule notes,
recurring task statuses, and maintenance tasks.
- Added tasks where absent, removed remaining template placeholders,
aligned fully qualified names, and ensured roadmap files conform to the
new validator checks.

## Testing

```bash
python tools/roadmap_validator/validate.py *2025q4*
```

CI: `Roadmap Validator` workflow runs automatically on pushes/dispatch.

---------

Co-authored-by: kaiserd <1684595+kaiserd@users.noreply.github.com>
2025-10-28 15:41:11 +02:00

1.4 KiB

title, tags, draft, description
title tags draft description
Maintaining existing Status Network L2 smart contracts
2025q4
sc
status-l2
false Maintain and improve existing Status Network L2 smart contracts as requested.

vac:sc:status-l2:2025q4-maintaining-status-l2-contracts

Maintain and improve existing Status Network L2 smart contracts as requested.

Description

Smart contracts for Status Network L2 that have already been implemented and deployed might still need maintenance. This includes upgrading systems, fixing bugs that might be discovered after the contracts have been deployed, and implementing minor enhancements that don't fall under specific commitments.

The Smart Contracts team commits to providing maintenance service for existing Status Network L2 smart contracts, such as:

  • Karma Token
  • Karma Airdrop
  • Staking and reward distribution contracts

Task List

There are no concrete tasks associated to this commitment. As requests come in, they will be addressed by our team.

Contract maintenance (recurring)

  • fully qualified name: vac:sc:status-l2:2025q4-maintaining-status-l2-contracts:maintenance
  • owner: sc-team
  • status: not started
  • start-date: 2025/10/01
  • end-date: 2025/12/31

Description

Handle inbound maintenance requests for deployed Status L2 contracts, including bug fixes and minor enhancements.

Deliverables

  • PRs/Issues/Docs/Reports