packet-tracer-skill 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this project should be recorded in this file.
+
+The format is intentionally simple and release-oriented.
+
+## [0.2.1]
+
+### Added
+
+- npm tarball hardening for the public package surface
+- launch announcement draft aligned with the current public release wording
+
+### Changed
+
+- package version advanced to `0.2.1` because `0.2.0` is already published on npm
+- npm package contents now exclude caches, generated previews, and non-essential screenshot payloads
+- public release references now consistently point to the `0.2.1` patch release artifacts
+
+### Notes
+
+- `0.2.1` is the publishable patch release for the conservative public preview surface
+- runtime messaging remains Windows-first and explicit about the external bridge-assisted validation path
+
+## [0.2.0]
+
+### Added
+
+- release engineering surface for CI, contributing, issue templates, citation metadata, and release checklist
+- keyword/discovery-oriented README rewrite aligned with current CLI and decision contracts
+- known working scenario set positioning for public examples
+- runtime truth, discovery keyword, GitHub metadata, publish-preview roadmap, and curated donor registry docs
+- seeded curated donor registry entries derived from known working public example artifacts
+- checked-in Packet Tracer template fallback assets for hermetic builder coverage
+- hero demo plan and `0.2.0` release notes draft artifacts for conservative launch prep
+
+### Changed
+
+- package metadata expanded for publish-readiness and host/discovery coverage
+- examples gallery language aligned with the scenario fixture corpus and acceptance excerpts
+- CI now includes parity-report and runtime doctor smoke steps
+- selected donor summaries now distinguish registry-backed versus inferred evidence
+- CI now cancels superseded in-progress runs on the same ref
+- placeholder-backed template devices are synthesized into Packet Tracer-native fallback nodes
+- README, GitHub metadata, release checklist, and roadmap now align around the `0.2.0` public preview message
+
+### Notes
+
+- runtime doctor and scenario decision surfaces remain Windows-first for real `.pkt` runtime
+- repo-local bridge is still intentionally not bundled by default
+- `0.2.0` is a conservative launch-prep release surface; npm publish and GitHub release remain a short follow-up batch

package/CITATION.cff

@@ -0,0 +1,15 @@
+cff-version: 1.2.0
+title: packet-tracer-skill
+message: "If you use this project in research, coursework, or tooling references, please cite it."
+type: software
+authors:
+  - family-names: Hajiyev
+    given-names: Sanan
+repository-code: "https://github.com/20hajiyev/packet-tracer-skill"
+url: "https://github.com/20hajiyev/packet-tracer-skill"
+license: MIT
+version: 0.1.0
+abstract: >-
+  Donor-backed Cisco Packet Tracer 9.x skill for natural-language planning,
+  scenario comparison, safe-open generation, editing, parity reporting, and
+  runtime diagnostics across skill-based coding hosts.

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,26 @@
+# Code of Conduct
+
+## Our Standard
+
+Use direct, respectful, technical communication.
+
+Expected behavior:
+
+- discuss facts and tradeoffs clearly
+- challenge assumptions without dismissiveness
+- prefer reproducible evidence over vague claims
+- keep contributions aligned with the repo's explicit safety and compatibility rules
+
+Unacceptable behavior:
+
+- harassment or personal attacks
+- intentionally misleading technical claims
+- repeated attempts to bypass donor/runtime safety rules in tracked docs or code
+
+## Scope
+
+This applies to issues, discussions, pull requests, and other project spaces.
+
+## Enforcement
+
+Maintainers may remove or close content that breaks this standard.

package/CONTRIBUTING.md

@@ -0,0 +1,120 @@
+# Contributing
+
+## What This Repo Optimizes For
+
+This project is not a generic Packet Tracer exporter. It is a strict, donor-backed, open-first workflow for Cisco Packet Tracer 9.0.0.0810.
+
+When contributing, preserve these rules:
+
+- final `.pkt` apply stays `single-donor`
+- unsupported and acceptance-gated mutate must refuse cleanly
+- `reference_only` donors must not become final donors
+- release/readme/docs claims must match actual runtime and acceptance state
+
+## Recommended Contribution Order
+
+Contributions are preferred in this order:
+
+1. contract consistency
+2. tests and regression coverage
+3. donor evidence and fixture corpus quality
+4. docs and release surface
+5. new capability expansion
+
+Do not lead with new mutation behavior if parity, donor evidence, or acceptance truth is still unclear.
+
+## Local Setup
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\scripts\setup.ps1 -Dev
+```
+
+Recommended validation:
+
+```powershell
+python .\scripts\build_examples_index.py
+python -m pytest tests -q
+node --check .\bin\packet-tracer-skill.js
+python .\scripts\generate_pkt.py --parity-report "campus with VLAN DHCP ACL"
+python .\scripts\runtime_doctor.py
+```
+
+## Change Types
+
+### Product Contract Changes
+
+If you change:
+
+- `scenario_generate_decision`
+- `scenario_acceptance_summary`
+- `scenario_matrix_row`
+- `capability_parity`
+- runtime doctor payload
+
+then update:
+
+- tests
+- README
+- example/gallery derivation if affected
+
+### Curated Donor Changes
+
+If you add or promote a curated donor:
+
+- update `references/curated-donor-registry.json`
+- keep provenance explicit
+- include promotion status and evidence
+- do not mark a donor as acceptance-verified without explicit fixture evidence
+
+### Scenario Fixture Changes
+
+If you add or modify a scenario fixture:
+
+- update `references/scenario-fixture-corpus.json`
+- keep canonical prompt text and expectations aligned
+- update docs/examples language if the fixture is public-facing
+
+### Example Artifact Changes
+
+Public examples are text-first:
+
+- commit inventory JSON
+- commit screenshots if intended for public docs
+- do not commit raw `.pkt` binaries
+- rebuild `examples/index.json` and `examples/gallery.md`
+
+## Pull Request Expectations
+
+A good change should answer:
+
+- what contract changed
+- why it changed
+- what tests prove it
+- what docs or examples were updated
+
+If the change affects runtime behavior, explicitly say whether it changes:
+
+- repo-local readiness
+- external bridge fallback
+- donor eligibility
+- acceptance gating
+
+## Release Surface Rules
+
+Do not make public README or npm claims that exceed actual tested behavior.
+
+Current high-sensitivity claims:
+
+- Windows-first runtime
+- Packet Tracer `9.0.0.0810`
+- donor-backed safe-open generate behavior
+- curated donor and fixture corpus semantics
+
+## Security and Privacy
+
+Never commit:
+
+- personal donor paths
+- generated labs unless intentionally public
+- private or unsigned bridge binaries
+- local Packet Tracer install paths baked into tracked files