GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — chore: remove the stray .agiloft-spec working notes by waleedlatif1 · Pull Request #6605 · simstudioai/sim

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • .agiloft-spec/SPEC.md (233 lines of transcribed Agiloft REST docs) was committed by accident in fix(agiloft): repoint the block at the alrest surface and fix EWLogin #6562 (be5db68644), alongside the alrest repointing work
  • Nothing imports, links, or references it — git grep agiloft-spec outside the directory itself returns nothing
  • It sits in a dot-directory at the repo root rather than anywhere docs live, and the integration it informed has shipped

Not a disclosure

The repo is public, so I scanned it before removing. Every credential and host in it is the vendor's own documentation placeholder — $login=user&$password=passwd, admin/qwerty, https://server, localhost. No real tenant hostnames, tokens, or keys. Nothing sensitive was exposed while it was there.

Type of Change

  • Chore

Testing

Deletion only — no code references it, so nothing to exercise. If the notes are still wanted as reference, the right home is apps/docs, not a root dot-directory; happy to move rather than delete.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

greptile-apps[bot] reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@waleedlatif1
chore: remove the stray .agiloft-spec working notes
11ebd9e
Transcribed Agiloft REST docs committed by accident in #6562 alongside the
alrest repointing. Nothing imports or links it, it sits in a dot-directory at
the repo root rather than anywhere docs live, and the integration it informed
has shipped. Contents are the vendor's own public examples — placeholder
credentials and localhost hosts only, so nothing sensitive was exposed while
it was public.
@vercel

vercel Bot commented Aug 12, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview Aug 12, 2026 5:17am

Request Review

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@cursor

cursor Bot commented Aug 12, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only deletion of an unreferenced file; no runtime, security, or behavioral impact.

Overview
Removes the accidentally committed .agiloft-spec/SPEC.md working notes (transcribed Agiloft REST docs) that were checked in with earlier alrest work.

Nothing in the repo imports or references this file, and it lived in a root dot-directory rather than docs. No sensitive credentials were present—only vendor documentation placeholders.

Reviewed by Cursor Bugbot for commit 11ebd9e. Configure here.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@waleedlatif1
waleedlatif1 merged commit a40e379 into staging Aug 12, 2026
5 of 6 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@waleedlatif1
waleedlatif1 deleted the chore/remove-agiloft-spec branch August 12, 2026 05:11
@greptile-apps

greptile-apps Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR removes an accidentally committed, unreferenced set of Agiloft REST API working notes.

  • Deletes .agiloft-spec/SPEC.md.
  • Leaves the implementation and published Agiloft documentation unchanged.

Confidence Score: 5/5

The PR appears safe to merge because the deleted notes have no identified repository consumer.

The change only removes an isolated working-notes file; tracked code, documentation, tests, and build configuration do not reference or implicitly discover it.

Important Files Changed

Filename Overview
.agiloft-spec/SPEC.md Deletes an unreferenced working-notes document with no identified build, runtime, documentation, or integration consumer.

Reviews (1): Last reviewed commit: "chore: remove the stray .agiloft-spec wo..." | Re-trigger Greptile

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@waleedlatif1 waleedlatif1 mentioned this pull request Aug 12, 2026
v0.8.0: desktop app, workflow UI, v2 endpoints #6606
Merged
@vercel
vercel Bot deployed to Preview August 12, 2026 05:17
View deployment

This branch was successfully deployed

1 active deployment
Preview — 11ebd9e7 Deployed Aug 12, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@waleedlatif1
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.