faf-taf-git 2.4.1 → 2.4.3

package/CONTRIBUTING.md

@@ -1,289 +0,0 @@
-<!-- faf: faf-taf-git | TypeScript | cli | A Test Receipt Printer for git -->
-<!-- faf: doc=contributing | canonical=project.faf | family=TAF -->
-
-# Contributing to FAF TAF Action
-
-Thank you for considering contributing to the FAF TAF Action!
-
-## Philosophy
-
-We follow the **WJTTC (WolfeJam Technical & Testing Center)** philosophy:
-
-> "We break things so others never know they were broken."
-
-This means:
-- Test everything
-- Find bugs early
-- Fix them immediately
-- Maintain championship standards
-
-## Code of Conduct
-
-- Be professional
-- Be respectful
-- Focus on facts
-- Trust is everything
-- No BS - only verified claims
-
-## Development Setup
-
-### Prerequisites
-
-- Node.js 20+
-- npm or yarn
-- Git
-- TypeScript knowledge
-
-### Getting Started
-
-```bash
-# Clone the repository
-git clone https://github.com/Wolfe-Jam/faf-taf-action.git
-cd faf-taf-action
-
-# Install dependencies
-npm install
-
-# Build the project
-npm run build
-
-# Run tests
-npm test
-
-# Run integration tests
-npx tsx test-standalone.ts
-npx tsx test-mcp.ts
-```
-
-## Project Structure
-
-```
-faf-taf-action/
-├── src/
-│   ├── index.ts          # Main action entry point
-│   ├── taf-core.ts       # MCP-portable TAF operations
-│   └── parsers/
-│       └── jest.ts       # Jest output parser
-├── tests/
-│   └── jest-parser.test.ts  # Unit tests
-├── docs/
-│   ├── USER-GUIDE.md     # User documentation
-│   └── RELEASE-NOTES.md  # Release history
-├── action.yml            # Action definition
-└── package.json          # Dependencies
-```
-
-## How to Contribute
-
-### 1. Report Bugs
-
-Open an issue with:
-- Clear description
-- Steps to reproduce
-- Expected vs actual behavior
-- Environment details
-- Minimal reproduction case
-
-### 2. Suggest Features
-
-Open an issue with:
-- Use case description
-- Why it's valuable
-- Proposed implementation (optional)
-- Alternatives considered
-
-### 3. Submit Code
-
-1. Fork the repository
-2. Create a feature branch
-3. Make your changes
-4. Add tests
-5. Update documentation
-6. Submit a pull request
-
-## Coding Standards
-
-### TypeScript
-
-- Use strict mode (already configured)
-- Explicit types everywhere
-- No `any` unless absolutely necessary
-- Descriptive variable names
-- Functions should be pure when possible
-
-### Testing
-
-- All new code must have tests
-- Maintain 100% coverage for critical paths
-- Use descriptive test names
-- Test both success and failure cases
-
-### Documentation
-
-- Update README.md for user-facing changes
-- Update USER-GUIDE.md for new features
-- Add inline comments for complex logic
-- Keep CLAUDE.md synchronized
-
-### Commits
-
-Follow our git protocol:
-
-```
-<type>: <what changed>
-
-- <specific change 1>
-- <specific change 2>
-```
-
-**Types:** `fix:` `feat:` `docs:` `refactor:` `chore:` `test:`
-
-**Examples:**
-```
-fix: Handle Jest output with skipped tests
-
-- Add skipped count parsing
-- Update test result interface
-- Add unit tests for skipped tests
-```
-
-```
-feat: Add Mocha parser support
-
-- Create mocha.ts parser
-- Add Mocha output format detection
-- Update documentation
-- Add integration tests
-```
-
-**Never:**
-- No exclamation marks
-- No emotion or hype
-- No "finally" or "at last"
-- Keep it boring and professional
-
-## Adding Test Framework Support
-
-To add support for a new test framework:
-
-### 1. Create Parser
-
-Create `src/parsers/[framework].ts`:
-
-```typescript
-export interface TestResults {
-  total: number;
-  passed: number;
-  failed: number;
-  skipped?: number;
-  result: 'PASSED' | 'FAILED' | 'IMPROVED' | 'DEGRADED';
-}
-
-export function parseFrameworkOutput(output: string): TestResults | null {
-  // Parse framework-specific output
-  // Return null if output doesn't match format
-}
-```
-
-### 2. Add Tests
-
-Create `tests/[framework]-parser.test.ts`:
-
-```typescript
-import { parseFrameworkOutput } from '../src/parsers/framework';
-
-describe('Framework Parser', () => {
-  it('should parse all passing tests', () => {
-    const output = `...`;
-    const result = parseFrameworkOutput(output);
-    expect(result?.total).toBe(10);
-    // ... more assertions
-  });
-
-  // Test all output variations
-});
-```
-
-### 3. Update Main Entry
-
-Modify `src/index.ts` to detect and use the new parser.
-
-### 4. Update Documentation
-
-- Add to README.md supported frameworks list
-- Add examples to USER-GUIDE.md
-- Update RELEASE-NOTES.md
-
-## Testing Requirements
-
-Before submitting a PR:
-
-```bash
-# All unit tests must pass
-npm test
-
-# Build must succeed with no errors
-npm run build
-
-# Integration tests must pass
-npx tsx test-standalone.ts
-npx tsx test-mcp.ts
-
-# TypeScript must compile with no errors
-npx tsc --noEmit
-```
-
-## Review Process
-
-1. **Automated Checks**
-   - TypeScript compilation
-   - Test suite (must be 100%)
-   - Linting
-
-2. **Code Review**
-   - Architecture fit
-   - Code quality
-   - Test coverage
-   - Documentation
-
-3. **Testing**
-   - Manual testing if needed
-   - Integration verification
-
-4. **Approval & Merge**
-   - Squash and merge
-   - Clean commit history
-
-## Release Process
-
-Releases follow semantic versioning:
-
-- **Major** (v2.0.0): Breaking changes
-- **Minor** (v1.1.0): New features, backward compatible
-- **Patch** (v1.0.1): Bug fixes
-
-Release checklist:
-1. Update version in package.json
-2. Update RELEASE-NOTES.md
-3. Run full test suite
-4. Build and verify dist/
-5. Create git tag
-6. Push to GitHub
-7. Create GitHub release
-8. Announce in discussions
-
-## Championship Standards
-
-We maintain F1-inspired engineering standards:
-
-- **Methodical**: Not a race, do it right
-- **Tested**: WJTTC certified
-- **Professional**: Boring is good
-- **Trusted**: Facts only, no hype
-
-## Questions?
-
-- GitHub Discussions: https://github.com/Wolfe-Jam/faf/discussions
-- Email: team@faf.one
-
-Thank you for contributing to the Golden Triangle!

package/SECURITY.md

@@ -1,19 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-We provide security updates for the latest released version. For older versions, please upgrade to the current release.
-
-## Reporting a Vulnerability
-
-If you discover a security vulnerability, please email **security@faf.one** directly.
-
-**Please do not open a public GitHub issue for security reports.** Responsible disclosure gives us time to fix the issue before it's widely known.
-
-When reporting, please include:
-- A description of the vulnerability
-- Steps to reproduce
-- Affected versions (if known)
-- Any suggested fix (optional)
-
-We aim to respond within 7 days.

package/action.yml

@@ -1,50 +0,0 @@
-name: 'TAF — Testing AI Format'
-description: 'A Test Receipt Printer for git. Every CI run prints a receipt to .taf — append-only, timestamped, kept in git. Proof over time.'
-author: 'wolfejam'
-
-branding:
-  icon: 'check-circle'
-  color: 'green'
-
-inputs:
-  test-output-file:
-    description: 'Path to file containing test output (created by previous step)'
-    required: true
-
-  auto-commit:
-    description: 'Automatically commit .taf updates (default: true)'
-    required: false
-    default: 'true'
-
-  commit-message:
-    description: 'Custom commit message for .taf updates'
-    required: false
-    default: 'chore(taf): update .taf receipt [skip ci]'
-
-  target-branch:
-    description: 'Push receipts to a dedicated branch (e.g. taf-receipts) instead of the current branch. Branch is created automatically on first run and seeded with existing .taf data.'
-    required: false
-    default: ''
-
-outputs:
-  result:
-    description: 'Test result (PASSED, FAILED, IMPROVED, DEGRADED)'
-
-  passed:
-    description: 'Number of tests passed'
-
-  failed:
-    description: 'Number of tests failed'
-
-  total:
-    description: 'Total number of tests'
-
-  skipped:
-    description: 'Number of tests skipped'
-
-  taf-updated:
-    description: 'Whether .taf file was updated (true/false)'
-
-runs:
-  using: 'node24'
-  main: 'dist/index.js'

package/agent.fafa

@@ -1,53 +0,0 @@
-version: "1.0"
-agent:
-  name: faf-taf-git
-  displayName: faf-taf-git
-  id: urn:air:faf.one:agent:faf-taf-git
-  version: 2.4.1
-  description: "A Test Receipt Printer for git: each CI run appends a receipt with the test counts and result to a .taf file kept in git."
-  homepage: https://faf.one
-capabilities:
-  - name: Print a receipt
-    type: tool
-    description: Append one Test Receipt (timestamp, counts, result, trigger) to .taf on each CI run
-    tags:
-      - print a receipt
-  - name: Read test output
-    type: tool
-    description: Parse Jest, Vitest, Bun and WJTTC test output into passed, failed and total
-    tags:
-      - read test output
-  - name: Receipts branch
-    type: tool
-    description: Push receipts to a dedicated branch such as taf-receipts, created on the first run
-    tags:
-      - receipts branch
-  - name: Auto-commit
-    type: tool
-    description: Commit the .taf update from CI, with an optional custom message
-    tags:
-      - auto-commit
-  - name: Badge
-    type: tool
-    description: Generate an SVG badge from the latest receipt in .taf
-    tags:
-      - badge
-  - name: Action outputs
-    type: tool
-    description: Expose result, passed, failed, total and taf-updated to later workflow steps
-    tags:
-      - action outputs
-endpoints:
-  - protocol: github-action
-    transport: http
-    location: Wolfe-Jam/faf-taf-git
-metadata:
-  cards:
-    domain: faf.one
-    examples:
-      - How do I keep a record of my test results on every CI run?
-      - How do I add Test Receipts to a GitHub Actions workflow?
-      - How do I make a test badge from my .taf history?
-    packages:
-      - registryType: npm
-        identifier: faf-taf-git

package/badge.svg

@@ -1,21 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="145" height="20" role="img" aria-label="TAF: 55/55 passing">
-  <title>TAF: 55/55 passing</title>
-  <linearGradient id="s" x2="0" y2="100%">
-    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset="1" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r">
-    <rect width="145" height="20" rx="3" fill="#fff"/>
-  </clipPath>
-  <g clip-path="url(#r)">
-    <rect width="40" height="20" fill="#555"/>
-    <rect x="40" width="105" height="20" fill="#003366"/>
-    <rect width="145" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="11">
-    <text x="20" y="14" fill="#010101" fill-opacity=".3">TAF</text>
-    <text x="20" y="13" fill="#fff">TAF</text>
-    <text x="92.5" y="14" fill="#010101" fill-opacity=".3">55/55 passing</text>
-    <text x="92.5" y="13" fill="#fff">55/55 passing</text>
-  </g>
-</svg>